[
https://issues.apache.org/jira/browse/TAPESTRY-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485778
]
Ben Sommerville commented on TAPESTRY-1333:
-------------------------------------------
Hmm, I've been working without problems under JBoss 4.0.5 with this patch for
the last few weeks.
I'm guessing from the stack trace that your test war is bundling log4j in its
lib. If you remove log4j from the war do you still get errors?
I've tended not to bundle log4j under JBoss as more often than not I get class
loader problems (or certain classes not logging at all).
Alternatively if you can point me at whatever app you were using to test I'll
try to chase down the problem myself. & report back :)
PS: were you using JBoss 4.0.2 or 4.0.5?
> Cannot bundle component classes & templates in WEB-INF/classes when deploying
> to Tomcat (& JBoss)
> -------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1333
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1333
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.3
> Environment: Tomcat 5, JBoss 4,
> Reporter: Ben Sommerville
> Attachments: TAP-1333.patch, TAP-1333_2.patch
>
>
> As described in TAPESTRY-1287 when deploying under Tomcat/JBoss, Tapestry
> currently does not pick up classes which are bundled under WEB-INF\classes
> (when the WAR is exploded).
> I have created a new issue for this because I think I've found a solution.
> Also, although I added a patch in the comments on 1287 as it turns out that
> patch was broken :(.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
