[
https://issues.apache.org/jira/browse/TAPESTRY-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485931
]
Ben Sommerville commented on TAPESTRY-1333:
-------------------------------------------
Some further info.
"org.jboss.logging.util.OnlyOnceErrorHandler" is configured by the JBoss
log4j.xml found under server/default/conf. My guess is that war doesn't have a
log4j config file bundled & it is picking up the JBoss one. Then the web app
log4j tries to assign a class loaded by the root JBoss loader to a the web app
log4j error handler... thus giving the ClassCastException
And an observation.
The workaround is really good if you are using maven to build/deploy.
Unfortunately a lot of other tools don't have the option of packaging
WEB-INF/classes as a jar......
(which is what motivated me to try & fix the problem)
> 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]
