On Sat, 12 Dec 2015 16:42:51 -0200, Luca Arzeni <[email protected]> wrote:
Hi Dimitris,
Hi, Luca!
Thanks for the insights about JBoss. I've never used it, so I've learned
some new stuff today and I thank you for that. :)
I agree with you when you say the problem is caused by JBoss separating
which classloader can access which classes (or classpaths). Is this
defined by the Java EE specs? If yes, so yes, Tapestry doesn't support the
spec fully.
Well, at least you seem to have found a way to avoid this problem, and
thanks for sharing it. ;)
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
