[opencms-dev] custom class for templateone.form

[Ian Kavanagh]

Carl Alex Friis Nielsen wrote:
>> -----Original Message-----
>> From: opencms-dev-bounces at opencms.org@KB On Behalf Of Ian Kavanagh
>> <ikavanagh at acm.org>
>>     
>
>   
>> Thanks very much for your prompt replies.  I did take a look at the 
>> .properties files in the classes directory, and it seemed like these 
>> strings are the actual text displayed on the edit form page, 
>> so I added 
>> an entry for my custom class in the "Input field types" 
>> section as follows:
>>
>> form.field.type.textLabel = Text label
>>
>> I hoped this would then show up as an option in the "Type:" drop-down 
>> menu, but it does not.
>> So basically, my problem is that I have my custom class, along with a 
>> .properties file for it, but I don't know how to integrate it 
>> into the 
>> larger templateone framework.  (My apologies if I'm missing something 
>> glaringly obvious).
>>     
>
> The available choices in a drop-down list is configured in the xsd
> describing the resource type being edited (or some nested part of it)
>
> look at the contents of the "schemas" folder in the module.
> inputfield.xsd might be of interest.
>
> However having the choice available in the list only allows you to set
> that value in the resource describing a form - you still have to add
> some code somewhere if you want the system to interpret it.
>
> Cheers,
>
> Carl
>
> _______________________________________________
> This mail is sent to you from the opencms-dev mailing list
> To change your list options, or to unsubscribe from the list, please visit
> http://lists.opencms.org/mailman/listinfo/opencms-dev
>
>   
One more question on this topic:

Now that I've created a custom form field and integrated it into the
larger templateone framework, what I'm not clear on is whether an
update/redeployment of OpenCMS would preserve this addition. Would these
files need to be added to the OpenCMS war as well, to ensure that
they're included in future deployments?

Thanks again,
Ian