You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Michael Lipp (JIRA)" <je...@portals.apache.org> on 2005/06/13 10:27:48 UTC
[jira] Created: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
*.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
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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Assigned: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "David Le Strat (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=all ]
David Le Strat reassigned JS2-281:
----------------------------------
Assign To: David Le Strat
> *.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
>
> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "David Le Strat (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=all ]
David Le Strat resolved JS2-281:
--------------------------------
Fix Version: 2.0-M4
Resolution: Fixed
All *.xml have been move from META-INF to META-INF/xxx/ for all components. This should fix this issue.
> *.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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [jira] Reopened: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by David Jencks <dj...@gluecode.com>.
On Aug 2, 2005, at 12:06 AM, Dr. Michael Lipp wrote:
> Hi,
>
>> 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?
>
> I support moving the configuration files out of META-INF. Though
> writing
> a deployer is of course possible, it introduces a strong dependency of
> Jetspeed on JBoss (I haven't looked into this closely, but it may even
> be possible that you need the JBoss libraries to compile the custom
> deployer, so you won't be able to compile Jetspeed without a JBoss
> installation). Besides, such like APIs are never 100% stable, so maybe
> we will need a different deployer for JBoss 3.x, 4.x etc.
It's conceivable that jboss would be interested in such a deployer.
You could make it generic so it would ignore a configurable list of
.xml files in META-INF, thus helping JBoss work with other projects
facing the same problem.
>
> I think that using META-INF for these files is wrong anyway. Despite
> its
> generic name, META-INF is a directory with a layout governed by the
> Java/J2EE specifications and adding your own files there implies always
> the risk of a conflict.
If JBoss followed your logic, this situation would not have arisen, as
JBoss would look in META-INF only for Java/J2ee required files and
would ignore the jetspeed ones. In addition, no one would put vendor
plans in META-INF for pre-j2ee 1.4 applications. As IIRC the original
author of the JBoss code in question, I can assure you that the problem
there is not some altruistic desire to preserve the purity of the
contents of META-INF but rather the lack of a way to explicitly specify
the classpath for a server and over-reliance on guessing based
directory scanning deployment.
thanks
david jencks
>
> - Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [jira] Reopened: (JS2-281) *.xml in jetspeed-security-*.jar cause
problems
Posted by "Dr. Michael Lipp" <Mi...@danet.de>.
Hi,
> 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?
I support moving the configuration files out of META-INF. Though writing
a deployer is of course possible, it introduces a strong dependency of
Jetspeed on JBoss (I haven't looked into this closely, but it may even
be possible that you need the JBoss libraries to compile the custom
deployer, so you won't be able to compile Jetspeed without a JBoss
installation). Besides, such like APIs are never 100% stable, so maybe
we will need a different deployer for JBoss 3.x, 4.x etc.
I think that using META-INF for these files is wrong anyway. Despite its
generic name, META-INF is a directory with a layout governed by the
Java/J2EE specifications and adding your own files there implies always
the risk of a conflict.
- Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [J2] Added PDF to Documentation - Deployed Site
Posted by David Le Strat <dl...@yahoo.com>.
All,
I refreshed the site on people.apache.org. It should
propagate within 24 hours.
Regards,
David Le Strat.
--- David Le Strat <dl...@yahoo.com> wrote:
> All,
>
> I have added PDFs to the site generation process. I
> have regenerated the entire site locally (a good 60
> minutes process with the coverage reports). I am
> trying to get it uploaded to people.apache.org, but
> it
> now seems to require an SSH public key. I will try
> to
> get this uploaded as soon as I can resolve this
> issue.
>
> Regards,
>
> David Le Strat
>
> --- David Le Strat <dl...@yahoo.com> wrote:
>
> > 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 <da...@yahoo.com> 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:
> > > jetspeed-dev-unsubscribe@portals.apache.org
> > > > For additional commands, e-mail:
> > > jetspeed-dev-help@portals.apache.org
> > > >
> > >
> > >
> > >
> >
>
---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> > > jetspeed-dev-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> > > jetspeed-dev-help@portals.apache.org
> > >
> > >
> >
> >
> > ________________________
> > 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:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
>
=== message truncated ===
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[J2] Added PDF to Documentation
Posted by David Le Strat <dl...@yahoo.com>.
All,
I have added PDFs to the site generation process. I
have regenerated the entire site locally (a good 60
minutes process with the coverage reports). I am
trying to get it uploaded to people.apache.org, but it
now seems to require an SSH public key. I will try to
get this uploaded as soon as I can resolve this issue.
Regards,
David Le Strat
--- David Le Strat <dl...@yahoo.com> wrote:
> 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 <da...@yahoo.com> 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:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > > For additional commands, e-mail:
> > jetspeed-dev-help@portals.apache.org
> > >
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> > jetspeed-dev-help@portals.apache.org
> >
> >
>
>
> ________________________
> 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:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
David Le Strat
Blogging @ http://dlsthoughts.blogspot.com
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [jira] Reopened: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by David Le Strat <dl...@yahoo.com>.
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 <da...@yahoo.com> 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:
> jetspeed-dev-unsubscribe@portals.apache.org
> > For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@portals.apache.org
>
>
________________________
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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
Re: [jira] Reopened: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by David Jencks <da...@yahoo.com>.
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: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Reopened: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "David Le Strat (JIRA)" <je...@portals.apache.org>.
[ 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "Michael Lipp (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=comments#action_12313433 ]
Michael Lipp commented on JS2-281:
----------------------------------
I just noticed that security_repository.xml *is* used at run-time. I propose moving it to META-INF/ojb/
> *.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
>
> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Resolved: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "David Le Strat (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=all ]
David Le Strat resolved JS2-281:
--------------------------------
Resolution: Fixed
Change committed. This should finally resolve this issue.
> *.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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "Michael Lipp (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=comments#action_12317296 ]
Michael Lipp commented on JS2-281:
----------------------------------
Regrettably, it does not fix the issue as JBoss searches for *.xml files in META-INF recursively!
I think the proper view of things is that META-INF should be considered a directory under control of the Java/J2EE specs and should therefore not be used by any other frameworks (though it has this tempting generic name). Something like OBJ-INF or SPRING-INF should be used instead.
> *.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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "David Le Strat (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=comments#action_12317093 ]
David Le Strat commented on JS2-281:
------------------------------------
I started to roll this change out. OJB mapping will go under META-INF/ojb/ and OJB mapping files will have an _repository suffix.
> *.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
>
> 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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
[jira] Commented: (JS2-281) *.xml in jetspeed-security-*.jar cause problems
Posted by "David Le Strat (JIRA)" <je...@portals.apache.org>.
[ http://issues.apache.org/jira/browse/JS2-281?page=comments#action_12317461 ]
David Le Strat commented on JS2-281:
------------------------------------
Will use JETSPEED-INF instead as requested by Scott.
> *.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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org