[Tapestry 5] Issue with loading ApplicationResources when using jetty:run

7 messages Options
Embed this post
Permalink
mraible

[Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
Serge,

In the following method of AppModule.java, you refer to the i18n
bundle as being located in WEB-INF/classes. This works great with "mvn
jetty:run-war" or when the project is packaged and deployed as a WAR.
However, I'd like to move to allowing folks to run "mvn jetty:run". In
this case, the files stay in src/main/resources and don't get copied.
Do you know if it's possible to change this method to allow both? I
was hoping something like "classpath:ApplicationResources.properties"
worked, but it doesn't.

        public static void contributeApplicationDefaults(
                        MappedConfiguration<String, String> configuration) {
                configuration.add(SymbolConstants.SUPPORTED_LOCALES,
                                          "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");
               
                configuration.add(SymbolConstants.APPLICATION_CATALOG,
                                          "WEB-INF/classes/ApplicationResources.properties");

                // The factory default is true but during the early stages of an
                // application
                // overriding to false is a good idea. In addition, this is often
                // overridden
                // on the command line as -Dtapestry.production-mode=false
                configuration.add(SymbolConstants.PRODUCTION_MODE, "true");

               
                // Set filesize limit to 2 MB
                 configuration.add(UploadSymbols.REQUESTSIZE_MAX, "2048000");
             configuration.add(UploadSymbols.FILESIZE_MAX, "2048000");
        }

Thanks,

Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Serge Eby

Re: [Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
Hi Matt,

I don't think that's possible.
However, I would recommend using the default Tapestry settings if possible by:
1) renaming these file match the "standard" Tapestry filter name under WEB-INF i.e. WEB-INF/app*properties
2) Removing the config below in the AppModule class

Less configs is better :)

Serge

On Mon, Dec 15, 2008 at 6:26 AM, Matt Raible <[hidden email]> wrote:
Serge,

In the following method of AppModule.java, you refer to the i18n
bundle as being located in WEB-INF/classes. This works great with "mvn
jetty:run-war" or when the project is packaged and deployed as a WAR.
However, I'd like to move to allowing folks to run "mvn jetty:run". In
this case, the files stay in src/main/resources and don't get copied.
Do you know if it's possible to change this method to allow both? I
was hoping something like "classpath:ApplicationResources.properties"
worked, but it doesn't.

       public static void contributeApplicationDefaults(
                       MappedConfiguration<String, String> configuration) {
               configuration.add(SymbolConstants.SUPPORTED_LOCALES,
                                         "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");

               configuration.add(SymbolConstants.APPLICATION_CATALOG,
                                         "WEB-INF/classes/ApplicationResources.properties");

               // The factory default is true but during the early stages of an
               // application
               // overriding to false is a good idea. In addition, this is often
               // overridden
               // on the command line as -Dtapestry.production-mode=false
               configuration.add(SymbolConstants.PRODUCTION_MODE, "true");


               // Set filesize limit to 2 MB
                configuration.add(UploadSymbols.REQUESTSIZE_MAX, "2048000");
            configuration.add(UploadSymbols.FILESIZE_MAX, "2048000");
       }

Thanks,

Matt

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




--
Serge Eby
Matt Raible-3

Re: [Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
Can you please enter an issue for this in JIRA? In reality, I wish
Tapestry followed all the other framework's conventions (putting i18n
files at the root of the classpath). However, I've given up on that
battle and will be lifting any "AppFuse way" conventions in favor of
framework conventions for 2.1.

BTW, have you had a chance to look at implementing Page tests at all?
I have AMP mostly working, but still need to do the tests, as well as
solve the following issue:

http://tinyurl.com/58u7hs

The above issue happens when the tapestry-basic archetype is used in
its current form. I hope to change things for 2.1 so users have the
full-source of the web module by default - just haven't gotten there
yet.

Thanks,

Matt

On Mon, Dec 15, 2008 at 3:54 PM, Serge Eby <[hidden email]> wrote:

> Hi Matt,
>
> I don't think that's possible.
> However, I would recommend using the default Tapestry settings if possible
> by:
> 1) renaming these file match the "standard" Tapestry filter name under
> WEB-INF i.e. WEB-INF/app*properties
> 2) Removing the config below in the AppModule class
>
> Less configs is better :)
>
> Serge
>
> On Mon, Dec 15, 2008 at 6:26 AM, Matt Raible <[hidden email]> wrote:
>>
>> Serge,
>>
>> In the following method of AppModule.java, you refer to the i18n
>> bundle as being located in WEB-INF/classes. This works great with "mvn
>> jetty:run-war" or when the project is packaged and deployed as a WAR.
>> However, I'd like to move to allowing folks to run "mvn jetty:run". In
>> this case, the files stay in src/main/resources and don't get copied.
>> Do you know if it's possible to change this method to allow both? I
>> was hoping something like "classpath:ApplicationResources.properties"
>> worked, but it doesn't.
>>
>>        public static void contributeApplicationDefaults(
>>                        MappedConfiguration<String, String> configuration)
>> {
>>                configuration.add(SymbolConstants.SUPPORTED_LOCALES,
>>
>>  "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");
>>
>>                configuration.add(SymbolConstants.APPLICATION_CATALOG,
>>
>>  "WEB-INF/classes/ApplicationResources.properties");
>>
>>                // The factory default is true but during the early stages
>> of an
>>                // application
>>                // overriding to false is a good idea. In addition, this is
>> often
>>                // overridden
>>                // on the command line as -Dtapestry.production-mode=false
>>                configuration.add(SymbolConstants.PRODUCTION_MODE, "true");
>>
>>
>>                // Set filesize limit to 2 MB
>>                 configuration.add(UploadSymbols.REQUESTSIZE_MAX,
>> "2048000");
>>             configuration.add(UploadSymbols.FILESIZE_MAX, "2048000");
>>        }
>>
>> Thanks,
>>
>> Matt
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> Serge Eby
>



--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Serge Eby

Re: [Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
Hi Matt,

I managed to get  mvn jetty:run working by overriding the default configuration. I will test this tonite against the latest code from the trunk and send a patch.
My only concern is that this adds more configuration rather than following the framework standards and use less code.
Let me know which option you prefer.

I started the tests by ran into some issues/limitations when using the PageTester class.
I think when the core classes are ready, we can move them into a module AppFuseModule and bundle this in a jar.

/Serge

On Mon, Dec 15, 2008 at 4:20 PM, Matt Raible <[hidden email]> wrote:
Can you please enter an issue for this in JIRA? In reality, I wish
Tapestry followed all the other framework's conventions (putting i18n
files at the root of the classpath). However, I've given up on that
battle and will be lifting any "AppFuse way" conventions in favor of
framework conventions for 2.1.

BTW, have you had a chance to look at implementing Page tests at all?
I have AMP mostly working, but still need to do the tests, as well as
solve the following issue:

http://tinyurl.com/58u7hs

The above issue happens when the tapestry-basic archetype is used in
its current form. I hope to change things for 2.1 so users have the
full-source of the web module by default - just haven't gotten there
yet.

Thanks,

Matt

On Mon, Dec 15, 2008 at 3:54 PM, Serge Eby <[hidden email]> wrote:
> Hi Matt,
>
> I don't think that's possible.
> However, I would recommend using the default Tapestry settings if possible
> by:
> 1) renaming these file match the "standard" Tapestry filter name under
> WEB-INF i.e. WEB-INF/app*properties
> 2) Removing the config below in the AppModule class
>
> Less configs is better :)
>
> Serge
>
> On Mon, Dec 15, 2008 at 6:26 AM, Matt Raible <[hidden email]> wrote:
>>
>> Serge,
>>
>> In the following method of AppModule.java, you refer to the i18n
>> bundle as being located in WEB-INF/classes. This works great with "mvn
>> jetty:run-war" or when the project is packaged and deployed as a WAR.
>> However, I'd like to move to allowing folks to run "mvn jetty:run". In
>> this case, the files stay in src/main/resources and don't get copied.
>> Do you know if it's possible to change this method to allow both? I
>> was hoping something like "classpath:ApplicationResources.properties"
>> worked, but it doesn't.
>>
>>        public static void contributeApplicationDefaults(
>>                        MappedConfiguration<String, String> configuration)
>> {
>>                configuration.add(SymbolConstants.SUPPORTED_LOCALES,
>>
>>  "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");
>>
>>                configuration.add(SymbolConstants.APPLICATION_CATALOG,
>>
>>  "WEB-INF/classes/ApplicationResources.properties");
>>
>>                // The factory default is true but during the early stages
>> of an
>>                // application
>>                // overriding to false is a good idea. In addition, this is
>> often
>>                // overridden
>>                // on the command line as -Dtapestry.production-mode=false
>>                configuration.add(SymbolConstants.PRODUCTION_MODE, "true");
>>
>>
>>                // Set filesize limit to 2 MB
>>                 configuration.add(UploadSymbols.REQUESTSIZE_MAX,
>> "2048000");
>>             configuration.add(UploadSymbols.FILESIZE_MAX, "2048000");
>>        }
>>
>> Thanks,
>>
>> Matt
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> Serge Eby
>



--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




--
Serge Eby
Matt Raible-3

Re: [Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
On Tue, Dec 16, 2008 at 8:51 AM, Serge Eby <[hidden email]> wrote:

> Hi Matt,
>
> I managed to get  mvn jetty:run working by overriding the default
> configuration. I will test this tonite against the latest code from the
> trunk and send a patch.
> My only concern is that this adds more configuration rather than following
> the framework standards and use less code.
> Let me know which option you prefer.
>
> I started the tests by ran into some issues/limitations when using the
> PageTester class.
> I think when the core classes are ready, we can move them into a module
> AppFuseModule and bundle this in a jar.

What do you mean by "when the core classes are ready"?

Matt

>
> /Serge
>
> On Mon, Dec 15, 2008 at 4:20 PM, Matt Raible <[hidden email]> wrote:
>>
>> Can you please enter an issue for this in JIRA? In reality, I wish
>> Tapestry followed all the other framework's conventions (putting i18n
>> files at the root of the classpath). However, I've given up on that
>> battle and will be lifting any "AppFuse way" conventions in favor of
>> framework conventions for 2.1.
>>
>> BTW, have you had a chance to look at implementing Page tests at all?
>> I have AMP mostly working, but still need to do the tests, as well as
>> solve the following issue:
>>
>> http://tinyurl.com/58u7hs
>>
>> The above issue happens when the tapestry-basic archetype is used in
>> its current form. I hope to change things for 2.1 so users have the
>> full-source of the web module by default - just haven't gotten there
>> yet.
>>
>> Thanks,
>>
>> Matt
>>
>> On Mon, Dec 15, 2008 at 3:54 PM, Serge Eby <[hidden email]> wrote:
>> > Hi Matt,
>> >
>> > I don't think that's possible.
>> > However, I would recommend using the default Tapestry settings if
>> > possible
>> > by:
>> > 1) renaming these file match the "standard" Tapestry filter name under
>> > WEB-INF i.e. WEB-INF/app*properties
>> > 2) Removing the config below in the AppModule class
>> >
>> > Less configs is better :)
>> >
>> > Serge
>> >
>> > On Mon, Dec 15, 2008 at 6:26 AM, Matt Raible <[hidden email]>
>> > wrote:
>> >>
>> >> Serge,
>> >>
>> >> In the following method of AppModule.java, you refer to the i18n
>> >> bundle as being located in WEB-INF/classes. This works great with "mvn
>> >> jetty:run-war" or when the project is packaged and deployed as a WAR.
>> >> However, I'd like to move to allowing folks to run "mvn jetty:run". In
>> >> this case, the files stay in src/main/resources and don't get copied.
>> >> Do you know if it's possible to change this method to allow both? I
>> >> was hoping something like "classpath:ApplicationResources.properties"
>> >> worked, but it doesn't.
>> >>
>> >>        public static void contributeApplicationDefaults(
>> >>                        MappedConfiguration<String, String>
>> >> configuration)
>> >> {
>> >>                configuration.add(SymbolConstants.SUPPORTED_LOCALES,
>> >>
>> >>  "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");
>> >>
>> >>                configuration.add(SymbolConstants.APPLICATION_CATALOG,
>> >>
>> >>  "WEB-INF/classes/ApplicationResources.properties");
>> >>
>> >>                // The factory default is true but during the early
>> >> stages
>> >> of an
>> >>                // application
>> >>                // overriding to false is a good idea. In addition, this
>> >> is
>> >> often
>> >>                // overridden
>> >>                // on the command line as
>> >> -Dtapestry.production-mode=false
>> >>                configuration.add(SymbolConstants.PRODUCTION_MODE,
>> >> "true");
>> >>
>> >>
>> >>                // Set filesize limit to 2 MB
>> >>                 configuration.add(UploadSymbols.REQUESTSIZE_MAX,
>> >> "2048000");
>> >>             configuration.add(UploadSymbols.FILESIZE_MAX, "2048000");
>> >>        }
>> >>
>> >> Thanks,
>> >>
>> >> Matt
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >>
>> >
>> >
>> >
>> > --
>> > Serge Eby
>> >
>>
>>
>>
>> --
>> http://raibledesigns.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> Serge Eby
>



--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Serge Eby

Re: [Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
I meant the default classes bundled in AppFuse (in org.appfuse.webpp.{pages,services,mixins}).
I assume you want multiple modules because users can decide to use different package. Is this accurate?


On Tue, Dec 16, 2008 at 9:03 AM, Matt Raible <[hidden email]> wrote:
On Tue, Dec 16, 2008 at 8:51 AM, Serge Eby <[hidden email]> wrote:
> Hi Matt,
>
> I managed to get  mvn jetty:run working by overriding the default
> configuration. I will test this tonite against the latest code from the
> trunk and send a patch.
> My only concern is that this adds more configuration rather than following
> the framework standards and use less code.
> Let me know which option you prefer.
>
> I started the tests by ran into some issues/limitations when using the
> PageTester class.
> I think when the core classes are ready, we can move them into a module
> AppFuseModule and bundle this in a jar.

What do you mean by "when the core classes are ready"?

Matt

>
> /Serge
>
> On Mon, Dec 15, 2008 at 4:20 PM, Matt Raible <[hidden email]> wrote:
>>
>> Can you please enter an issue for this in JIRA? In reality, I wish
>> Tapestry followed all the other framework's conventions (putting i18n
>> files at the root of the classpath). However, I've given up on that
>> battle and will be lifting any "AppFuse way" conventions in favor of
>> framework conventions for 2.1.
>>
>> BTW, have you had a chance to look at implementing Page tests at all?
>> I have AMP mostly working, but still need to do the tests, as well as
>> solve the following issue:
>>
>> http://tinyurl.com/58u7hs
>>
>> The above issue happens when the tapestry-basic archetype is used in
>> its current form. I hope to change things for 2.1 so users have the
>> full-source of the web module by default - just haven't gotten there
>> yet.
>>
>> Thanks,
>>
>> Matt
>>
>> On Mon, Dec 15, 2008 at 3:54 PM, Serge Eby <[hidden email]> wrote:
>> > Hi Matt,
>> >
>> > I don't think that's possible.
>> > However, I would recommend using the default Tapestry settings if
>> > possible
>> > by:
>> > 1) renaming these file match the "standard" Tapestry filter name under
>> > WEB-INF i.e. WEB-INF/app*properties
>> > 2) Removing the config below in the AppModule class
>> >
>> > Less configs is better :)
>> >
>> > Serge
>> >
>> > On Mon, Dec 15, 2008 at 6:26 AM, Matt Raible <[hidden email]>
>> > wrote:
>> >>
>> >> Serge,
>> >>
>> >> In the following method of AppModule.java, you refer to the i18n
>> >> bundle as being located in WEB-INF/classes. This works great with "mvn
>> >> jetty:run-war" or when the project is packaged and deployed as a WAR.
>> >> However, I'd like to move to allowing folks to run "mvn jetty:run". In
>> >> this case, the files stay in src/main/resources and don't get copied.
>> >> Do you know if it's possible to change this method to allow both? I
>> >> was hoping something like "classpath:ApplicationResources.properties"
>> >> worked, but it doesn't.
>> >>
>> >>        public static void contributeApplicationDefaults(
>> >>                        MappedConfiguration<String, String>
>> >> configuration)
>> >> {
>> >>                configuration.add(SymbolConstants.SUPPORTED_LOCALES,
>> >>
>> >>  "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");
>> >>
>> >>                configuration.add(SymbolConstants.APPLICATION_CATALOG,
>> >>
>> >>  "WEB-INF/classes/ApplicationResources.properties");
>> >>
>> >>                // The factory default is true but during the early
>> >> stages
>> >> of an
>> >>                // application
>> >>                // overriding to false is a good idea. In addition, this
>> >> is
>> >> often
>> >>                // overridden
>> >>                // on the command line as
>> >> -Dtapestry.production-mode=false
>> >>                configuration.add(SymbolConstants.PRODUCTION_MODE,
>> >> "true");
>> >>
>> >>
>> >>                // Set filesize limit to 2 MB
>> >>                 configuration.add(UploadSymbols.REQUESTSIZE_MAX,
>> >> "2048000");
>> >>             configuration.add(UploadSymbols.FILESIZE_MAX, "2048000");
>> >>        }
>> >>
>> >> Thanks,
>> >>
>> >> Matt
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >>
>> >
>> >
>> >
>> > --
>> > Serge Eby
>> >
>>
>>
>>
>> --
>> http://raibledesigns.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> Serge Eby
>



--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




--
Serge Eby
Matt Raible-3

Re: [Tapestry 5] Issue with loading ApplicationResources when using jetty:run

Reply Threaded More More options
Print post
Permalink
Yes, you are correct. How AppFuse currently works by default is the
core functionality is bundled in a WAR and the dependencies (and
classes) are read by the maven-warpath-plugin. So when a person first
creates a new project from an archetype, they will have their own
package names, but AppFuse classes will reside in
org.appfuse.webapp.*. If I can try the solution posted here
(http://tinyurl.com/58u7hs), I should be able to get it to work.
Regardless, it's a temporary solution as I hope to change 2.1 so the
archetypes give you all the source for the webapp instead of embedding
it in a dependency.

Matt

On Tue, Dec 16, 2008 at 10:04 AM, Serge Eby <[hidden email]> wrote:

> I meant the default classes bundled in AppFuse (in
> org.appfuse.webpp.{pages,services,mixins}).
> I assume you want multiple modules because users can decide to use different
> package. Is this accurate?
>
>
> On Tue, Dec 16, 2008 at 9:03 AM, Matt Raible <[hidden email]> wrote:
>>
>> On Tue, Dec 16, 2008 at 8:51 AM, Serge Eby <[hidden email]> wrote:
>> > Hi Matt,
>> >
>> > I managed to get  mvn jetty:run working by overriding the default
>> > configuration. I will test this tonite against the latest code from the
>> > trunk and send a patch.
>> > My only concern is that this adds more configuration rather than
>> > following
>> > the framework standards and use less code.
>> > Let me know which option you prefer.
>> >
>> > I started the tests by ran into some issues/limitations when using the
>> > PageTester class.
>> > I think when the core classes are ready, we can move them into a module
>> > AppFuseModule and bundle this in a jar.
>>
>> What do you mean by "when the core classes are ready"?
>>
>> Matt
>>
>> >
>> > /Serge
>> >
>> > On Mon, Dec 15, 2008 at 4:20 PM, Matt Raible <[hidden email]> wrote:
>> >>
>> >> Can you please enter an issue for this in JIRA? In reality, I wish
>> >> Tapestry followed all the other framework's conventions (putting i18n
>> >> files at the root of the classpath). However, I've given up on that
>> >> battle and will be lifting any "AppFuse way" conventions in favor of
>> >> framework conventions for 2.1.
>> >>
>> >> BTW, have you had a chance to look at implementing Page tests at all?
>> >> I have AMP mostly working, but still need to do the tests, as well as
>> >> solve the following issue:
>> >>
>> >> http://tinyurl.com/58u7hs
>> >>
>> >> The above issue happens when the tapestry-basic archetype is used in
>> >> its current form. I hope to change things for 2.1 so users have the
>> >> full-source of the web module by default - just haven't gotten there
>> >> yet.
>> >>
>> >> Thanks,
>> >>
>> >> Matt
>> >>
>> >> On Mon, Dec 15, 2008 at 3:54 PM, Serge Eby <[hidden email]> wrote:
>> >> > Hi Matt,
>> >> >
>> >> > I don't think that's possible.
>> >> > However, I would recommend using the default Tapestry settings if
>> >> > possible
>> >> > by:
>> >> > 1) renaming these file match the "standard" Tapestry filter name
>> >> > under
>> >> > WEB-INF i.e. WEB-INF/app*properties
>> >> > 2) Removing the config below in the AppModule class
>> >> >
>> >> > Less configs is better :)
>> >> >
>> >> > Serge
>> >> >
>> >> > On Mon, Dec 15, 2008 at 6:26 AM, Matt Raible <[hidden email]>
>> >> > wrote:
>> >> >>
>> >> >> Serge,
>> >> >>
>> >> >> In the following method of AppModule.java, you refer to the i18n
>> >> >> bundle as being located in WEB-INF/classes. This works great with
>> >> >> "mvn
>> >> >> jetty:run-war" or when the project is packaged and deployed as a
>> >> >> WAR.
>> >> >> However, I'd like to move to allowing folks to run "mvn jetty:run".
>> >> >> In
>> >> >> this case, the files stay in src/main/resources and don't get
>> >> >> copied.
>> >> >> Do you know if it's possible to change this method to allow both? I
>> >> >> was hoping something like
>> >> >> "classpath:ApplicationResources.properties"
>> >> >> worked, but it doesn't.
>> >> >>
>> >> >>        public static void contributeApplicationDefaults(
>> >> >>                        MappedConfiguration<String, String>
>> >> >> configuration)
>> >> >> {
>> >> >>                configuration.add(SymbolConstants.SUPPORTED_LOCALES,
>> >> >>
>> >> >>  "de,en,es,fr,it,ko,nl,no,pt_BR,pt,tr,zh_CN,zh_TW,en_US");
>> >> >>
>> >> >>
>> >> >>  configuration.add(SymbolConstants.APPLICATION_CATALOG,
>> >> >>
>> >> >>  "WEB-INF/classes/ApplicationResources.properties");
>> >> >>
>> >> >>                // The factory default is true but during the early
>> >> >> stages
>> >> >> of an
>> >> >>                // application
>> >> >>                // overriding to false is a good idea. In addition,
>> >> >> this
>> >> >> is
>> >> >> often
>> >> >>                // overridden
>> >> >>                // on the command line as
>> >> >> -Dtapestry.production-mode=false
>> >> >>                configuration.add(SymbolConstants.PRODUCTION_MODE,
>> >> >> "true");
>> >> >>
>> >> >>
>> >> >>                // Set filesize limit to 2 MB
>> >> >>                 configuration.add(UploadSymbols.REQUESTSIZE_MAX,
>> >> >> "2048000");
>> >> >>             configuration.add(UploadSymbols.FILESIZE_MAX,
>> >> >> "2048000");
>> >> >>        }
>> >> >>
>> >> >> Thanks,
>> >> >>
>> >> >> Matt
>> >> >>
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: [hidden email]
>> >> >> For additional commands, e-mail: [hidden email]
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Serge Eby
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://raibledesigns.com
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [hidden email]
>> >> For additional commands, e-mail: [hidden email]
>> >>
>> >
>> >
>> >
>> > --
>> > Serge Eby
>> >
>>
>>
>>
>> --
>> http://raibledesigns.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
>
> --
> Serge Eby
>



--
http://raibledesigns.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]