RE: Messages in modules (where to put the *.properties files)
Hi, Thanks for that. That worked. Cheers Russell -Original Message- From: SergeEby [mailto:[EMAIL PROTECTED] Sent: 06 June 2008 16:11 To: users@tapestry.apache.org Subject: Re: Messages in modules (where to put the *.properties files) Hi, If you are using Maven, you should put your properties files under src/main/resources/my/package/components See details here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/project-layout. html /Serge Russell Brown-6 wrote: > > Hi, > > I have created a couple of components and have jarred them up as a > library. I followed the Tapestry 5 book and the how to here > http://wiki.apache.org/tapestry/Tapestry5HowToCreateYourOwnComponentLibr > ary on the wiki. It is working ok for me so far except that one of my > components makes use of the and the validate regexp > pattern contained in related properties file for the component cannot be > found. This component started life as a page. When it was a Page (in the > *.*.*.pages package) it renedered correctly and the regexp for the > corresponding field was found. Now it is a component and packaged up > (and referred to as thanks to adding a > LibraryMapping to the ComponentClasResolver via > contributeComponentClassResolver ) I get the exception that follows > > > > ender queue error in BeginRender[core/PropertyEditBlocks:textfield]: > Failure reading parameter 'validate' of component > core/PropertyEditBlocks:textfield: Validator 'regexp' requires a > validation constraint (of type java.util.regex.Pattern) but none was > provided. > > > > Can anyone let me know what I need to do to make this work? The > component is called register and the properties file is in the > my.package.components package with the component. Is that correct or > should it be elsewhere? > > > > Cheers > > > > Russell > > > > Communications on or through ioko's computer systems may be monitored or > recorded to secure effective system operation and for other lawful > purposes. > > Unless otherwise agreed expressly in writing, this communication is to be > treated as confidential and the information in it may not be used or > disclosed except for the purpose for which it has been sent. If you have > reason to believe that you are not the intended recipient of this > communication, please contact the sender immediately. No employee is > authorised to conclude any binding agreement on behalf of ioko with > another party by e-mail without prior express written confirmation. > > ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved. > > -- View this message in context: http://www.nabble.com/Messages-in-modules-%28where-to-put-the-*.properti es-files%29-tp17694337p17694525.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Communications on or through ioko's computer systems may be monitored or recorded to secure effective system operation and for other lawful purposes. Unless otherwise agreed expressly in writing, this communication is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this communication, please contact the sender immediately. No employee is authorised to conclude any binding agreement on behalf of ioko with another party by e-mail without prior express written confirmation. ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Messages in modules (where to put the *.properties files)
Hi, If you are using Maven, you should put your properties files under src/main/resources/my/package/components See details here: http://tapestry.apache.org/tapestry5/tapestry-core/guide/project-layout.html /Serge Russell Brown-6 wrote: > > Hi, > > I have created a couple of components and have jarred them up as a > library. I followed the Tapestry 5 book and the how to here > http://wiki.apache.org/tapestry/Tapestry5HowToCreateYourOwnComponentLibr > ary on the wiki. It is working ok for me so far except that one of my > components makes use of the and the validate regexp > pattern contained in related properties file for the component cannot be > found. This component started life as a page. When it was a Page (in the > *.*.*.pages package) it renedered correctly and the regexp for the > corresponding field was found. Now it is a component and packaged up > (and referred to as thanks to adding a > LibraryMapping to the ComponentClasResolver via > contributeComponentClassResolver ) I get the exception that follows > > > > ender queue error in BeginRender[core/PropertyEditBlocks:textfield]: > Failure reading parameter 'validate' of component > core/PropertyEditBlocks:textfield: Validator 'regexp' requires a > validation constraint (of type java.util.regex.Pattern) but none was > provided. > > > > Can anyone let me know what I need to do to make this work? The > component is called register and the properties file is in the > my.package.components package with the component. Is that correct or > should it be elsewhere? > > > > Cheers > > > > Russell > > > > Communications on or through ioko's computer systems may be monitored or > recorded to secure effective system operation and for other lawful > purposes. > > Unless otherwise agreed expressly in writing, this communication is to be > treated as confidential and the information in it may not be used or > disclosed except for the purpose for which it has been sent. If you have > reason to believe that you are not the intended recipient of this > communication, please contact the sender immediately. No employee is > authorised to conclude any binding agreement on behalf of ioko with > another party by e-mail without prior express written confirmation. > > ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved. > > -- View this message in context: http://www.nabble.com/Messages-in-modules-%28where-to-put-the-*.properties-files%29-tp17694337p17694525.html Sent from the Tapestry - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Messages in modules (where to put the *.properties files)
Hi, I have created a couple of components and have jarred them up as a library. I followed the Tapestry 5 book and the how to here http://wiki.apache.org/tapestry/Tapestry5HowToCreateYourOwnComponentLibr ary on the wiki. It is working ok for me so far except that one of my components makes use of the and the validate regexp pattern contained in related properties file for the component cannot be found. This component started life as a page. When it was a Page (in the *.*.*.pages package) it renedered correctly and the regexp for the corresponding field was found. Now it is a component and packaged up (and referred to as thanks to adding a LibraryMapping to the ComponentClasResolver via contributeComponentClassResolver ) I get the exception that follows ender queue error in BeginRender[core/PropertyEditBlocks:textfield]: Failure reading parameter 'validate' of component core/PropertyEditBlocks:textfield: Validator 'regexp' requires a validation constraint (of type java.util.regex.Pattern) but none was provided. Can anyone let me know what I need to do to make this work? The component is called register and the properties file is in the my.package.components package with the component. Is that correct or should it be elsewhere? Cheers Russell Communications on or through ioko's computer systems may be monitored or recorded to secure effective system operation and for other lawful purposes. Unless otherwise agreed expressly in writing, this communication is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this communication, please contact the sender immediately. No employee is authorised to conclude any binding agreement on behalf of ioko with another party by e-mail without prior express written confirmation. ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved.
