All, I have been looking a bit into what David Jencks suggests here. We could indeed write a custom deployer for Jetspeed.
1. Custom JBoss deployer that would ignore jetspeed configuration files (OJB and Castor for data binding). 2. Move OJB and Castor files into JETSPEED-INF. This change could be quickly implemented as the location of the configuration files location is injected through spring assembly. I believe that 2. is an acceptable solution. What do others think? Regards, David Le Strat. --- David Jencks <[EMAIL PROTECTED]> wrote: > Are you sure there isn't a way to convince JBoss to > behave better by > including a "deployer" that recognizes the jetspeed > configurations and > basically ignores them? i don't know what is in any > of these jars, but > would it be appropriate to write a jboss mbean that > starts spring and > sets up j2? I'd be reluctant to move stuff out of > META-INF for this > reason. IIRC there were quite a few other jars that > had this problem, > I wonder what they did about them. > > thanks > david jencks > > On Aug 1, 2005, at 6:48 AM, David Le Strat (JIRA) > wrote: > > > [ > http://issues.apache.org/jira/browse/JS2-281?page=all > ] > > > > David Le Strat reopened JS2-281: > > -------------------------------- > > > > > > The previous fix did not completely fix the issue. > I propose to put > > Jetspeed configuration file into J2-INF instead of > META-INF. This > > will avoid any issue of that sort. Please let me > know what you think. > > > >> *.xml in jetspeed-security-*.jar cause problems > >> ----------------------------------------------- > >> > >> Key: JS2-281 > >> URL: > http://issues.apache.org/jira/browse/JS2-281 > >> Project: Jetspeed 2 > >> Type: Bug > >> Components: Security > >> Versions: 2.0-M3 > >> Environment: JBoss > >> Reporter: Michael Lipp > >> Assignee: David Le Strat > >> Fix For: 2.0-M4 > > > >> > >> The component file jetspeed-security-*.jar > contains in its META-INF/ > >> directory two *.xml files. These files prevent > the deployment of this > >> Jar in JBoss in other contexts than a WAR. > >> The reason is that JBoss assumes that there is a > special deployer for > >> Jars that have *.xml files in META-INF. So the > default deployer for > >> Jars skips any such Jars. This problem does not > show if > >> jakarta-security-*.jar is put in the WEB-INF/lib > simply because you > >> cannot use the JBoss deployer for Jetspeed2 > anyway, you must use the > >> Tomcat deployer. but if you try to put > jetspeed-security-*.jar in > >> e.g. a sar, the problem shows. > >> As far as I have understood, the *.xml files are > only significant for > >> testing anyway. They should be put elsewhere. > >> I'm aware that this is, at its root, a JBoss > problem. But I won't be > >> able to make them change this behaviour. > > > > -- > > This message is automatically generated by JIRA. > > - > > If you think it was sent incorrectly contact one > of the administrators: > > > http://issues.apache.org/jira/secure/Administrators.jspa > > - > > For more information on JIRA, see: > > http://www.atlassian.com/software/jira > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > ________________________ David Le Strat Blogging @ http://dlsthoughts.blogspot.com ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
