I am trying to share tapestry JARs between multiple web apps by
placing Tapestry JARs into common library directory on the container
(domain1/lib in GlassFish)
Clearly Tapestry does not support this configuration, as I get multiple IoC
instances and warnings of such.
Is this by-design or some
Never used GlassFish, but skinny wars work fine in Tomcat.
Kalle
On Tue, Feb 22, 2011 at 2:26 AM, Lenny Primak lpri...@hope.nyc.ny.us wrote:
I am trying to share tapestry JARs between multiple web apps by
placing Tapestry JARs into common library directory on the container
(domain1/lib in
Are you using maven?
___
Everton Agner Ramos
2011/2/22 Kalle Korhonen kalle.o.korho...@gmail.com
Never used GlassFish, but skinny wars work fine in Tomcat.
Kalle
On Tue, Feb 22, 2011 at 2:26 AM, Lenny Primak lpri...@hope.nyc.ny.us
wrote:
I am trying to share
Yes, I am using maven, but I don't think it's of any consequence in this case.
Kalle, I just tried this with Tomcat 6, and I get the same error, although just
like in Glassfish,
the application seems to work.
I am assuming that this error will cause something to break at some point :)
On Tue, Feb 22, 2011 at 8:01 AM, Everton Agner ton.ag...@gmail.com wrote:
Are you using maven?
Yes.
Kalle
2011/2/22 Kalle Korhonen kalle.o.korho...@gmail.com
Never used GlassFish, but skinny wars work fine in Tomcat.
Kalle
On Tue, Feb 22, 2011 at 2:26 AM, Lenny Primak
On Tue, 22 Feb 2011 13:48:05 -0300, Lenny Primak lpri...@hope.nyc.ny.us
wrote:
Yes, I am using maven, but I don't think it's of any consequence in this
case.
Maybe yes: by default, Maven puts all the dependency JARs in WEB-INF/lib
of the generated web app, so make sure the JARs you've
They are definitely not repeated. The only time I get this error is when there
more than
one web app running that depends on tapestry in the same container,
and there is only one copy of tapestry-* jars, in the common directory.
There are no tapestry jar files in the WEB-INF/lib in this case.
I
The warning you are getting are unavoidable. The background:
Tapestry makes service proxies serializable. This is important, as it
is not unusual to have a data object that persists in the HttpSession
that must have a reference to a IoC service.
The services are not serialized, just the
Thanks! This error is actually 'severe' not a warning.
Can this be made into a warning,
or can some kind of list of IoC be used or some such in the static variable?
On Feb 22, 2011, at 12:31 PM, Howard Lewis Ship wrote:
The warning you are getting are unavoidable. The background:
Tapestry
