from:"pico.dev"

Re: Getting Started with 5.7.2

2021-09-01 Thread pico.dev

Thanks Tim.

Updated to use Jetty 10 and Java 11.

El mié, 1 sept 2021 a las 4:07, D Tim Cummings ()
escribió:

> Thanks pico
>
> I had a quick look and see that you are targeting java 8 and jetty 9.4.
> I think we should be targeting java 11 and jetty 10 at least. The
> quickstart helps new users get familiar with tapestry and old users see
> what is required to run tapestry on the latest java and jetty. I
> remember when I first started with tapestry how frustrating it was for
> me to have to learn really old versions of jetty just to get sample code
> to run. Then my first task was to translate everything to new versions
> of jetty, not knowing if it was even possible. Now we should say that
> tapestry doesn't work with jetty 11 so we are providing an example with
> jetty 10.
>
> Thanks for all your work. I will keep testing.
>
> Tim
>
> On 31/8/21 20:36, pico.dev wrote:
> > Hello,
> >
> > I created this issue https://issues.apache.org/jira/browse/TAP5-2690
> Update
> > quickstart to make Spring Boot optional.
> >
> > I attached a patch in the issue and a summary with the main changes
> > performed to the quickstart.
> >
> > Give a look and a test, if something should be changed leave a comment
> and
> > I will do the change.
> >
> > Regards,
> >
> > El vie, 27 ago 2021 a las 7:52, pico.dev ()
> escribió:
> >
> >> Hello,
> >>
> >> Just to say that I will start to work on updating quickstat to make
> spring
> >> boot optional. Give me some days, I will come with a patch.
> >>
> >> Regards,
> >>
> >> El mar, 10 ago 2021 a las 23:36, Thiago H. de Paula Figueiredo (<
> >> thiag...@gmail.com>) escribió:
> >>
> >>> On Thu, Aug 5, 2021 at 10:02 PM D Tim Cummings
> >>> 
> >>> wrote:
> >>>
> >>>> Hi Thiago
> >>>>
> >>> Hello!
> >>>
> >>>
> >>>> I believe pico.dev is waiting for confirmation that you would like
> the
> >>>> quickstart app reverted to jetty.
> >>>
> >>> I'm sorry I overlooked this. I prefer Quickstart to be as simple as
> >>> possible, so I believe Jetty is the way to go. SpringBoot is better
> left
> >>> being optional.
> >>>
> >>>
> >>>> Personally I think it is great there
> >>>> is a quickstart using springboot, but it should be in addition to the
> >>>> quickstart using jetty, not replacing it. Also it should come with
> >>>> instructions how to use it.
> >>>>
> >>> I also agree with this.
> >>>
> >>>
> >>>> I have just tried quickstart again recently and the three issues
> listed
> >>>> in my first email below, still exist.
> >>>>
> >>>> *An additional problem facing new users on the getting started page*
> >>>>
> >>>> Getting started https://tapestry.apache.org/getting-started.html
> >>> suggests
> >>>> mvn archetype:generate -DarchetypeCatalog=http://tapestry.apache.org
> >>>>
> >>>> However this no longer works on version 3 or later of the
> >>>> maven-archetype-plugin. This has been flagged as issue
> >>>> https://issues.apache.org/jira/projects/TAP5/issues/TAP5-2579 . I
> >>>> suggest changing web page to use the command
> >>>>
> >>>> mvn archetype:generate -Dfilter=org.apache.tapestry:quickstart
> >>>>
> >>>> and then you could close that issue. If someone could give me edit
> >>>> privileges on the getting started page I would be happy to do that.
> >>>>
> >>> Thanks for spotting that and volunteering for fixing it! I just fixed
> it
> >>> myself, but it takes some time for the fix to be replicated to the
> site.
> >>>
> >>> Thank you!
> >>>
> >>>> Thanks
> >>>>
> >>>> Tim
> >>>>
> >>>> On 1/5/21 17:17, pico.dev wrote:
> >>>>> Hi!
> >>>>>
> >>>>> Sorry for the inconvenience.
> >>>>>
> >>>>> If Spring Boot is not desired in the app generated by quickstart, I
> >>> could
> >>>>> try to provide a new patch to remove it if you wish, I hope as soon
> >>> as I
> >>>>> can, just confirm me and I start doing the changes.
>

Re: Getting Started with 5.7.2

2021-08-31 Thread pico.dev

Hello,

I created this issue https://issues.apache.org/jira/browse/TAP5-2690 Update
quickstart to make Spring Boot optional.

I attached a patch in the issue and a summary with the main changes
performed to the quickstart.

Give a look and a test, if something should be changed leave a comment and
I will do the change.

Regards,

El vie, 27 ago 2021 a las 7:52, pico.dev () escribió:

> Hello,
>
> Just to say that I will start to work on updating quickstat to make spring
> boot optional. Give me some days, I will come with a patch.
>
> Regards,
>
> El mar, 10 ago 2021 a las 23:36, Thiago H. de Paula Figueiredo (<
> thiag...@gmail.com>) escribió:
>
>> On Thu, Aug 5, 2021 at 10:02 PM D Tim Cummings
>> 
>> wrote:
>>
>> > Hi Thiago
>> >
>>
>> Hello!
>>
>>
>> > I believe pico.dev is waiting for confirmation that you would like the
>> > quickstart app reverted to jetty.
>>
>>
>> I'm sorry I overlooked this. I prefer Quickstart to be as simple as
>> possible, so I believe Jetty is the way to go. SpringBoot is better left
>> being optional.
>>
>>
>> > Personally I think it is great there
>> > is a quickstart using springboot, but it should be in addition to the
>> > quickstart using jetty, not replacing it. Also it should come with
>> > instructions how to use it.
>> >
>>
>> I also agree with this.
>>
>>
>> > I have just tried quickstart again recently and the three issues listed
>> > in my first email below, still exist.
>> >
>> > *An additional problem facing new users on the getting started page*
>> >
>> > Getting started https://tapestry.apache.org/getting-started.html
>> suggests
>> >
>> > mvn archetype:generate -DarchetypeCatalog=http://tapestry.apache.org
>> >
>> > However this no longer works on version 3 or later of the
>> > maven-archetype-plugin. This has been flagged as issue
>> > https://issues.apache.org/jira/projects/TAP5/issues/TAP5-2579 . I
>> > suggest changing web page to use the command
>> >
>> > mvn archetype:generate -Dfilter=org.apache.tapestry:quickstart
>> >
>> > and then you could close that issue. If someone could give me edit
>> > privileges on the getting started page I would be happy to do that.
>> >
>>
>> Thanks for spotting that and volunteering for fixing it! I just fixed it
>> myself, but it takes some time for the fix to be replicated to the site.
>>
>> Thank you!
>>
>> >
>> > Thanks
>> >
>> > Tim
>> >
>> > On 1/5/21 17:17, pico.dev wrote:
>> > > Hi!
>> > >
>> > > Sorry for the inconvenience.
>> > >
>> > > If Spring Boot is not desired in the app generated by quickstart, I
>> could
>> > > try to provide a new patch to remove it if you wish, I hope as soon
>> as I
>> > > can, just confirm me and I start doing the changes.
>> > >
>> > > Regards,
>> > >
>> > > El vie, 30 abr 2021 a las 22:43, Thiago H. de Paula Figueiredo (<
>> > > thiag...@gmail.com>) escribió:
>> > >
>> > >> Hello!
>> > >>
>> > >> Thank you very much for spotting and warning us about these issues.
>> > >>
>> > >> You shouldn't need to use Spring Boot. The archetype needs to be
>> fixed.
>> > >>
>> > >> On Sat, Apr 24, 2021 at 9:00 PM D Tim Cummings
>> > > > >> wrote:
>> > >>
>> > >>> I have tried the instructions at
>> > >>> https://tapestry.apache.org/getting-started.html using Tapestry
>> 5.7.2
>> > >>> archetype.
>> > >>>
>> > >>> 1. The code produced by 5.7.2 archetype uses 5.6 packages
>> > >>> org.apache.tapestry5.services.Request, RequestFilter,
>> RequestHandler,
>> > >>> Response so it won't compile.
>> > >>>
>> > >>> As there were only four to be fixed I manually changed them in
>> > >>> com.example.newapp.services.AppModule.java to
>> > >>>
>> > >>> import org.apache.tapestry5.http.services.Request;
>> > >>> import org.apache.tapestry5.http.services.RequestFilter;
>> > >>> import org.apache.tapestry5.http.services.RequestHandler;
>> > >>> import org.apache.tapestry5.http.services.Response;
>> > >>>
>> > >>> 2. Instructions say use 'mvn jetty:run' but there is no jetty plugin
>> > >>> defined in the pom so this doesn't work despite the nice screen shot
>> > >>> showing it working with 5.7.2.
>> > >>>
>> > >>> 3. I ran 'mvn spring-boot:run' and this ran successfully. However,
>> one
>> > >>> of the reasons I was trying the archetype was because I was getting
>> a
>> > >>> lot of duplicate jar warnings in the project I was migrating to
>> 5.7.2.
>> > >>> Maybe spring-boot solves this problem by not copying duplicates into
>> > its
>> > >>> uber jar. Do I need to convert my existing project to include
>> > >>> spring-boot for building a war?
>> > >>>
>> > >>> Thanks
>> > >>>
>> > >>> Tim
>> > >>>
>> > >>>
>> > >>>
>> -
>> > >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> > >>> For additional commands, e-mail: users-h...@tapestry.apache.org
>> > >>>
>> > >>>
>> > >> --
>> > >> Thiago
>> > >>
>> >
>>
>>
>> --
>> Thiago
>>
>

Re: Getting Started with 5.7.2

2021-08-26 Thread pico.dev

Hello,

Just to say that I will start to work on updating quickstat to make spring
boot optional. Give me some days, I will come with a patch.

Regards,

El mar, 10 ago 2021 a las 23:36, Thiago H. de Paula Figueiredo (<
thiag...@gmail.com>) escribió:

> On Thu, Aug 5, 2021 at 10:02 PM D Tim Cummings  >
> wrote:
>
> > Hi Thiago
> >
>
> Hello!
>
>
> > I believe pico.dev is waiting for confirmation that you would like the
> > quickstart app reverted to jetty.
>
>
> I'm sorry I overlooked this. I prefer Quickstart to be as simple as
> possible, so I believe Jetty is the way to go. SpringBoot is better left
> being optional.
>
>
> > Personally I think it is great there
> > is a quickstart using springboot, but it should be in addition to the
> > quickstart using jetty, not replacing it. Also it should come with
> > instructions how to use it.
> >
>
> I also agree with this.
>
>
> > I have just tried quickstart again recently and the three issues listed
> > in my first email below, still exist.
> >
> > *An additional problem facing new users on the getting started page*
> >
> > Getting started https://tapestry.apache.org/getting-started.html
> suggests
> >
> > mvn archetype:generate -DarchetypeCatalog=http://tapestry.apache.org
> >
> > However this no longer works on version 3 or later of the
> > maven-archetype-plugin. This has been flagged as issue
> > https://issues.apache.org/jira/projects/TAP5/issues/TAP5-2579 . I
> > suggest changing web page to use the command
> >
> > mvn archetype:generate -Dfilter=org.apache.tapestry:quickstart
> >
> > and then you could close that issue. If someone could give me edit
> > privileges on the getting started page I would be happy to do that.
> >
>
> Thanks for spotting that and volunteering for fixing it! I just fixed it
> myself, but it takes some time for the fix to be replicated to the site.
>
> Thank you!
>
> >
> > Thanks
> >
> > Tim
> >
> > On 1/5/21 17:17, pico.dev wrote:
> > > Hi!
> > >
> > > Sorry for the inconvenience.
> > >
> > > If Spring Boot is not desired in the app generated by quickstart, I
> could
> > > try to provide a new patch to remove it if you wish, I hope as soon as
> I
> > > can, just confirm me and I start doing the changes.
> > >
> > > Regards,
> > >
> > > El vie, 30 abr 2021 a las 22:43, Thiago H. de Paula Figueiredo (<
> > > thiag...@gmail.com>) escribió:
> > >
> > >> Hello!
> > >>
> > >> Thank you very much for spotting and warning us about these issues.
> > >>
> > >> You shouldn't need to use Spring Boot. The archetype needs to be
> fixed.
> > >>
> > >> On Sat, Apr 24, 2021 at 9:00 PM D Tim Cummings
> >  > >> wrote:
> > >>
> > >>> I have tried the instructions at
> > >>> https://tapestry.apache.org/getting-started.html using Tapestry
> 5.7.2
> > >>> archetype.
> > >>>
> > >>> 1. The code produced by 5.7.2 archetype uses 5.6 packages
> > >>> org.apache.tapestry5.services.Request, RequestFilter, RequestHandler,
> > >>> Response so it won't compile.
> > >>>
> > >>> As there were only four to be fixed I manually changed them in
> > >>> com.example.newapp.services.AppModule.java to
> > >>>
> > >>> import org.apache.tapestry5.http.services.Request;
> > >>> import org.apache.tapestry5.http.services.RequestFilter;
> > >>> import org.apache.tapestry5.http.services.RequestHandler;
> > >>> import org.apache.tapestry5.http.services.Response;
> > >>>
> > >>> 2. Instructions say use 'mvn jetty:run' but there is no jetty plugin
> > >>> defined in the pom so this doesn't work despite the nice screen shot
> > >>> showing it working with 5.7.2.
> > >>>
> > >>> 3. I ran 'mvn spring-boot:run' and this ran successfully. However,
> one
> > >>> of the reasons I was trying the archetype was because I was getting a
> > >>> lot of duplicate jar warnings in the project I was migrating to
> 5.7.2.
> > >>> Maybe spring-boot solves this problem by not copying duplicates into
> > its
> > >>> uber jar. Do I need to convert my existing project to include
> > >>> spring-boot for building a war?
> > >>>
> > >>> Thanks
> > >>>
> > >>> Tim
> > >>>
> > >>>
> > >>> -
> > >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > >>> For additional commands, e-mail: users-h...@tapestry.apache.org
> > >>>
> > >>>
> > >> --
> > >> Thiago
> > >>
> >
>
>
> --
> Thiago
>

Re: Getting Started with 5.7.2

2021-05-01 Thread pico.dev

Hi!

Sorry for the inconvenience.

If Spring Boot is not desired in the app generated by quickstart, I could
try to provide a new patch to remove it if you wish, I hope as soon as I
can, just confirm me and I start doing the changes.

Regards,

El vie, 30 abr 2021 a las 22:43, Thiago H. de Paula Figueiredo (<
thiag...@gmail.com>) escribió:

> Hello!
>
> Thank you very much for spotting and warning us about these issues.
>
> You shouldn't need to use Spring Boot. The archetype needs to be fixed.
>
> On Sat, Apr 24, 2021 at 9:00 PM D Tim Cummings  >
> wrote:
>
> > I have tried the instructions at
> > https://tapestry.apache.org/getting-started.html using Tapestry 5.7.2
> > archetype.
> >
> > 1. The code produced by 5.7.2 archetype uses 5.6 packages
> > org.apache.tapestry5.services.Request, RequestFilter, RequestHandler,
> > Response so it won't compile.
> >
> > As there were only four to be fixed I manually changed them in
> > com.example.newapp.services.AppModule.java to
> >
> > import org.apache.tapestry5.http.services.Request;
> > import org.apache.tapestry5.http.services.RequestFilter;
> > import org.apache.tapestry5.http.services.RequestHandler;
> > import org.apache.tapestry5.http.services.Response;
> >
> > 2. Instructions say use 'mvn jetty:run' but there is no jetty plugin
> > defined in the pom so this doesn't work despite the nice screen shot
> > showing it working with 5.7.2.
> >
> > 3. I ran 'mvn spring-boot:run' and this ran successfully. However, one
> > of the reasons I was trying the archetype was because I was getting a
> > lot of duplicate jar warnings in the project I was migrating to 5.7.2.
> > Maybe spring-boot solves this problem by not copying duplicates into its
> > uber jar. Do I need to convert my existing project to include
> > spring-boot for building a war?
> >
> > Thanks
> >
> > Tim
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
> --
> Thiago
>

Re: Access request from tml / standard servlet api role support

2018-04-27 Thread pico.dev

Maybe other alternative is create a base page class that has this and
some/all application pages extends

@Inject
RequestGlobals m_requestGlobals;

public boolean isUserAdmin()

El sáb., 28 abr. 2018 a las 0:41, pico.dev () escribió:

> Hi,
>
> Maybe you can implement a new conditional component that checks the role
> and render or not its body. Something like this:
>
> 
> SAVE DATA
> 
>
> See https://tapestry.apache.org/component-rendering.html
>
> Regards,
>
> El sáb., 28 abr. 2018 a las 0:12, Luca Arzeni ()
> escribió:
>
>> Hi,
>> I'm using tapestry5.4 with java 8.
>>
>> I am using the standard servlet API to check if a user is in role or not,
>> to hide or show buttons, links, and so on.
>>
>> For example, I need to show a button to the user only if the user has
>> been granted a role.
>>
>> My usual way to to this is:
>>
>> 1) create a method in the page, for example:
>>
>> @Inject
>> RequestGlobals m_requestGlobals;
>>
>> public boolean isUserAdmin() {
>> if (m_requestGlobals == null) {
>> return false;
>> }
>> return m_requestGlobals.isUserInRole("ADMIN");
>> }
>>
>> 2) then, in the tml, check the method using a t:if component, for example:
>>
>> 
>> SAVE DATA
>> 
>>
>> This is not so good, since I must reimplement the same method in many
>> pages.
>>
>> Is there any way could I access the requestGlobals directly from tml?
>>
>> My goql would be to write, directly in the tml, something like:
>>
>>
>> 
>> SAVE DATA
>> 
>>
>>
>> Is it possible to do this with tapestry5?
>>
>> Thanks in advance,
>> larzeni
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
>> For additional commands, e-mail: users-h...@tapestry.apache.org
>>
>>

Re: Access request from tml / standard servlet api role support

2018-04-27 Thread pico.dev

Hi,

Maybe you can implement a new conditional component that checks the role
and render or not its body. Something like this:


SAVE DATA


See https://tapestry.apache.org/component-rendering.html

Regards,

El sáb., 28 abr. 2018 a las 0:12, Luca Arzeni ()
escribió:

> Hi,
> I'm using tapestry5.4 with java 8.
>
> I am using the standard servlet API to check if a user is in role or not,
> to hide or show buttons, links, and so on.
>
> For example, I need to show a button to the user only if the user has been
> granted a role.
>
> My usual way to to this is:
>
> 1) create a method in the page, for example:
>
> @Inject
> RequestGlobals m_requestGlobals;
>
> public boolean isUserAdmin() {
> if (m_requestGlobals == null) {
> return false;
> }
> return m_requestGlobals.isUserInRole("ADMIN");
> }
>
> 2) then, in the tml, check the method using a t:if component, for example:
>
> 
> SAVE DATA
> 
>
> This is not so good, since I must reimplement the same method in many
> pages.
>
> Is there any way could I access the requestGlobals directly from tml?
>
> My goql would be to write, directly in the tml, something like:
>
>
> 
> SAVE DATA
> 
>
>
> Is it possible to do this with tapestry5?
>
> Thanks in advance,
> larzeni
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Re: ApacheCon Europe

2014-12-05 Thread pico.dev

Hi,

Is there any video available of the presentations? I'd like to watch them

Best regards,

2014-11-27 10:33 GMT+01:00 Thilo Tanner :

> Hi folks,
>
> Uli and myself gave our best to promote Tapestry on ApacheCon Europe in
> Budapest last week. Unfortunately, most people were more interested in
> buzzword technologies, in particular in the Hadoop ecosystem. Don’t get me
> wrong, Hadoop is a good technology if you have a real use case for it, but
> my impression was, that if, only a handful of attendees really deal with
> big data. This is a bit sad, especially because the few people attended
> our talks were very impressed what Tapestry is capable of and praised the
> big potential of the framework. Therefore a big thank you from my side to
> the people that put their effort into Tapestry! I’m still convinced that
> Tapestry is one of the best (web) application frameworks out there.
>
> In case you’re interested, below the link to my slides:
>
> http://events.linuxfoundation.org/sites/events/files/slides/141109_Tapestry
> _Talk_0.pdf
> 
>
> Best,
> Thilo
>
>

Re: Tapetstry JPA - nested DAO and commits

2013-06-18 Thread pico.dev .

What about this?
http://tawus.wordpress.com/2011/04/23/tapestry-magic-5-advising-services/


2013/6/18 Thiago H. de Paula Figueiredo 

> Tapestry-Hibernate and Tapestry-JPA were created for simple scenarios, in
> which you don't need that much control on transactions. If you really need
> more than that, you'll be better served by EJB or Spring or something else
> that deals with transactions in a more specifc way.
>
>
> On Tue, Jun 18, 2013 at 11:35 AM, Lenny Primak  >wrote:
>
> > Full JEE (i.e. Stateless EJBs) support nested transactions.
> >
> > On Jun 18, 2013, at 4:13 AM, John wrote:
> >
> > > I have some updating DAOs that refer to other updating DAOs. Both the
> > top level and the lower level DAO update the same PU and use the
> following
> > on their interfaces:
> > >
> > > @CommitAfter
> > >
> > > @PersistenceContext(unitName = "DBUnit")
> > >
> > > Will the transactions be nested properly, i.e. will the lower levels
> DAO
> > commit actually occur on the exit of the top level DAOs method exit? I
> > don't want the lower level transaction to be a new and seperate one (it
> > should use the transaction that's already open) because obviosuly that
> > would not synchronize the updates with seperate transactions.
> > >
> > > John
> > >
> > >
> > >
> > >
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>
>
> --
> Thiago
>

Re: Pageable Loop-like Component

2011-11-20 Thread pico.dev


Josh Kamau wrote:
> 
> Hi there ;
> 
> Is there a way of hiding the header of the Grid component. What i want to
> have is a way of listing items (e.g the way the Loop does it) but also
> with
> the paging capabilities.
> 
> Regards.
> Josh.
> 

Maybe this is what you need.

http://elblogdepicodev.blogspot.com/2011/01/componente-lista-para-tapestry-5.html
https://docs.google.com/uc?id=0B4yquUFv3csrNWY1M2EzZmQtMjg0MC00ZGYwLThmNTMtNDZiMDJmODZmMzBh&export=download&authkey=CIvr76YB&hl=es

The com.blogspot.elblogdepicodev.tapestry.components.Lista component and
others are based on the tapestry grid component. Sorry, it is in spanish but
the code can be understanded. 

--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Pageable-Loop-like-Component-tp5008539p5008758.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Re: text/javascript not minimized and HTTP status 200

2011-11-01 Thread pico.dev

Yes, I'm using apache-tomcat-7.0.22, with the only additions of mysql
connector and java-mail libs.

If it is relevant my other enviroment is:
Arch Linux (64 bits).

java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.4)
(ArchLinux-6.b22_1.10.4-1-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode).

App is deployed into tomcat in expanded mode.

My list of libraries included in the WEB-INF/lib:
annotations-api-6.0.30.jar
antlr-2.7.7.jar
antlr-runtime-3.3.jar
aopalliance-1.0.jar
apache-mime4j-0.6.jar
bcprov-jdk15-135.jar
bsh-2.0b4.jar
c3p0-0.9.1.1.jar
cglib-nodep-2.2.jar
commons-codec-1.5.jar
commons-collections-3.2.1.jar
commons-fileupload-1.2.2.jar
commons-io-2.0.1.jar
commons-lang-2.4.jar
commons-lang3-3.0.jar
commons-logging-1.1.1.jar
cssparser-0.9.5.jar
dbcp-6.0.30.jar
dom4j-1.6.1.jar
easymock-3.0.jar
ehcache-core-2.4.3.jar
freemarker-2.3.18.jar
groovy-all-1.8.3.jar
gson-1.7.1.jar
guava-r09.jar
guice-2.0.jar
hibernate-commons-annotations-3.2.0.Final.jar
hibernate-core-3.6.8.Final.jar
hibernate-ehcache-3.6.8.Final.jar
hibernate-jpa-2.0-api-1.0.1.Final.jar
hibernate-validator-4.2.0.Final.jar
htmlunit-2.8.jar
htmlunit-core-js-2.8.jar
httpclient-4.0.2.jar
httpcore-4.0.1.jar
httpmime-4.0.1.jar
javassist-3.12.1.GA.jar
javax.inject-1.jar
jcommander-1.12.jar
jna-3.2.3.jar
js-1.6R7.jar
json-20080701.jar
jta-1.1.jar
juli-6.0.30.jar
junit-3.8.1.jar
log4j-1.2.16.jar
mockito-all-1.9.0-rc1.jar
mx4j-tools-3.0.1.jar
nekohtml-1.9.14.jar
objenesis-1.2.jar
plastic-5.3-rc-2.jar
quartz-2.1.0.jar
restfb-1.6.6.jar
sac-1.3.jar
serializer-2.7.1.jar
slf4j-api-1.6.1.jar
slf4j-log4j12-1.6.1.jar
snakeyaml-1.8.jar
stringtemplate-3.2.1.jar
tapestry5-annotations-5.3-rc-2.jar
tapestry-beanvalidator-5.3-rc-2.jar
tapestry-core-5.3-rc-2.jar
tapestry-facebook-0.0.1-SNAPSHOT.jar
tapestry-func-5.3-rc-2.jar
tapestry-hibernate-5.3-rc-2.jar
tapestry-hibernate-core-5.3-rc-2.jar
tapestry-ioc-5.3-rc-2.jar
tapestry-javadoc-5.3-rc-2.jar
tapestry-jmx-5.3-rc-2.jar
tapestry-json-5.3-rc-2.jar
tapestry-test-5.3-rc-2.jar
tapestry-upload-5.3-rc-2.jar
tapestry-yuicompressor-5.3-rc-2.jar
testng-5.14.9.jar
validation-api-1.0.0.GA.jar
xalan-2.7.1.jar
xercesImpl-2.9.1.jar
xml-apis-1.3.04.jar
yuicompressor-2.4.6.jar


Howard Lewis Ship wrote:
> 
> We're finding that YUICompressor doesn't work inside Tomcat.  Could
> this be the issue?
> 
> On Tue, Nov 1, 2011 at 5:48 AM, pico.dev . <pico.dev@> wrote:
>> Hi!
>>
>> I've updated my app to Tapestry 5.3-rc-2 and I'm testing the
>> minification and production mode. I've included in my project the
>> tapestry-yuicompressor dependency and I've made contributions to the
>> ApplicationDefaults like this in my app module:
>>
>> public static void
>> contributeApplicationDefaults(MappedConfiguration<String, String>
>> configuration) {
>>        configuration.add(SymbolConstants.PRODUCTION_MODE, "true");
>>        configuration.add(SymbolConstants.COMPRESS_WHITESPACE, "true");
>>        configuration.add(SymbolConstants.COMBINE_SCRIPTS, "true");
>>        configuration.add(SymbolConstants.MINIFICATION_ENABLED, "true");
>>        configuration.add(SymbolConstants.COMPACT_JSON, "true");
>>        ...
>> }
>>
>> When I access to my application the text/css resources gets minimized
>> correctly but the text/javascript resources are returned like the
>> originals without any minimization.
>>
>> Also I noted that with PRODUCTION_MODE to "true" all text/css and
>> text/javascript assets are returned with HTTP status 200 code and the
>> transferred size of all resources of a request to my app is 290 KiB
>> according to Chrome Developer Tools. With PRODUCTION_MODE to "false"
>> the assets are returned with HTTP status 304 code and the transferred
>> size of all resources is 25 KiB.
>>
>> I'm missing something? Anyone with the same behavour?
>>
>> Cheers,
>>
>> -
>> To unsubscribe, e-mail: users-unsubscribe@.apache
>> For additional commands, e-mail: users-help@.apache
>>
>>
> 
> 
> 
> -- 
> Howard M. Lewis Ship
> 
> Creator of Apache Tapestry
> 
> The source for Tapestry training, mentoring and support. Contact me to
> learn how I can get you up and productive in Tapestry fast!
> 
> (971) 678-5210
> http://howardlewisship.com
> 
> -
> To unsubscribe, e-mail: users-unsubscribe@.apache
> For additional commands, e-mail: users-help@.apache
> 


--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/text-javascript-not-minimized-and-HTTP-status-200-tp4955260p4955399.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

text/javascript not minimized and HTTP status 200

2011-11-01 Thread pico.dev .

Hi!

I've updated my app to Tapestry 5.3-rc-2 and I'm testing the
minification and production mode. I've included in my project the
tapestry-yuicompressor dependency and I've made contributions to the
ApplicationDefaults like this in my app module:

public static void
contributeApplicationDefaults(MappedConfiguration
configuration) {
configuration.add(SymbolConstants.PRODUCTION_MODE, "true");
configuration.add(SymbolConstants.COMPRESS_WHITESPACE, "true");
configuration.add(SymbolConstants.COMBINE_SCRIPTS, "true");
configuration.add(SymbolConstants.MINIFICATION_ENABLED, "true");
configuration.add(SymbolConstants.COMPACT_JSON, "true");
...
}

When I access to my application the text/css resources gets minimized
correctly but the text/javascript resources are returned like the
originals without any minimization.

Also I noted that with PRODUCTION_MODE to "true" all text/css and
text/javascript assets are returned with HTTP status 200 code and the
transferred size of all resources of a request to my app is 290 KiB
according to Chrome Developer Tools. With PRODUCTION_MODE to "false"
the assets are returned with HTTP status 304 code and the transferred
size of all resources is 25 KiB.

I'm missing something? Anyone with the same behavour?

Cheers,

-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Re: Getting Started with 5.7.2

Re: Getting Started with 5.7.2

Re: Getting Started with 5.7.2

Re: Getting Started with 5.7.2

Re: Access request from tml / standard servlet api role support

Re: Access request from tml / standard servlet api role support

Re: ApacheCon Europe

Re: Tapetstry JPA - nested DAO and commits

Re: Pageable Loop-like Component

Re: text/javascript not minimized and HTTP status 200

text/javascript not minimized and HTTP status 200

11 matches

Site Navigation

Mail list logo

Footer information