[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
11:58 a.m.
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR (for
EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
John Eckhart updated JBSEAM-4022:
---------------------------------
Attachment: classdescriptor.patch
Here is the workaround I used, in the form of a patch against Seam 2.1.1 GA.
I chose to patch ClassDescriptor because that is where the symptoms were manifest and
therefore easiest to remedy; however, another logical place for this patch may be in the
scanner that originally grabs the "filename" of the annotated class.
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:53 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
Pete Muir commented on JBSEAM-4022:
-----------------------------------
Place it in WEB-INF/components.xml or WEB-INF/classes/META-INF/components.xml
Though we should probably not fail if it is in META-INF
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:11 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
John Eckhart commented on JBSEAM-4022:
--------------------------------------
Thanks Pete, I've tried that location and I am still able to reproduce this if the
components.xml is in my myApp.war/WEB-INF/ folder.
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:24 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
Denis Forveille commented on JBSEAM-4022:
-----------------------------------------
We are using WebSphere v7.0.0.1 + RSA v7.5.1 with split modules (1 web + 1 JPA +1 EJB) and
we don't have problems like this one
For the web module we put an empty seam.properties in the "src" directory (root
of our java sourecs in RAD) and components.xml in WEB_INF
The seam.properties is copied to the classes dir with the other".class" files
and as the scanner seems to base the "root" path of its search on the location
of the seam.properties file, it works
no need to patch anything for us...
You can also search in the forum for some of my posts where I describe the way we
structure our projects to run with WAS v7.0
Hope this helps.
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
John Eckhart commented on JBSEAM-4022:
--------------------------------------
Denis, your guides were instrumental in helping me get seam running on WebSphere 7.0 in
the first place, thank you!! I've tuned the structure in a few parts as I was testing
various options and plan to feed those observations back into your forum posts.
Do you have Seam components (Seam annotated POJO's) in your web component? I
didn't encounter this error until I started annotating a few classes in my war to use
as backing beans for JSF (Facelets). If so, I will have to look closer as to why I was
encountering the mentioned behavior as well as why my patch was necessary.
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:18 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
Denis Forveille commented on JBSEAM-4022:
-----------------------------------------
I'm not sure this is the place to discuss this, we should use the forum for this I
think, however, yes, we have various scope seam components in the web side, many factories
(to build list for s:convertEnum, tags for exemple), converters, filters and
"presentation related" components
Do you have a seam.properties file at the top root of your classes directory with the
seam-jndi.properties file (ie at the root of your src directory in RAD/RSA)? did you
remove all other seam.properties files in your web modules? did you put components.xml,
pages.xml ... in WEB-INF? did you remove all the components.xml files you could have
elsewhere in your
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:21 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4022) ComponentScanner fails with classes in WEB-INF/classes on websphere
[
https://jira.jboss.org/jira/browse/JBSEAM-4022?page=com.atlassian.jira.pl...
]
Norman Richards commented on JBSEAM-4022:
-----------------------------------------
I'm sorry, but I'm terribly confused. Is there an actual bug here or is this the
same as JBSEAM-2347? If you are just asking a usage question, please use the forums. If
you are reporting an actual bug (as opposed to putting the descriptors in the wrong place
as with the prior issue) can you be very clear about what your structure is and how it
differs from the examples which have been successfully run in websphere.
ComponentScanner fails with classes in WEB-INF/classes on websphere
-------------------------------------------------------------------
Key: JBSEAM-4022
URL: https://jira.jboss.org/jira/browse/JBSEAM-4022
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.1.1.GA
Environment: Websphere 7.0 (also reported on Websphere 6.1)
Reporter: John Eckhart
Attachments: classdescriptor.patch
This bug is a follow-on to 2347 which was rejected. Since it doesn't appear possible
to request a bug be "reopened", I've created a new bug to track the
problem.
The problem: When a Seam annotated class is included in a WAR file, the filename of the
class will be "WEB-INF/classes/com/mycompany/MyClass.class". Theoretically, this
IS the filename as the classes are packaged under WEB-INF/classes, however, the
classloader does not recognize/ignore "WEB-INF/classes/" as part of the name
(which is logical, since the classpath includes everything under this directory). This
causes ComponentScanner to throw the following exception: java.lang.NoClassDefFoundError:
WEB-INF.classes.com.mycompany.Myclass
The previous issue was rejected with the following rationale: "This turned out to be
a user error, not a websphere issues. The classpath was correct, but the user put a
META-INF/components.xml in the WAR which causes the scanning error."
However:
Where would the components.xml go if a project is broken into WAR, JAR (for JPA), JAR
(for EJB), and finally EAR (containing the mentioned components)?
Based on the examples I've read for WebSphere , the recommended place for
components.xml is in the WAR file. Moreover, it would stand to reason that including seam
components in the WAR would be beneficial (ie POJO components as backing beans for jsf
pages).
I ran into this issue recently in Websphere 7.0 where I had a Seam managed POJO as a
backing bean to a JSF page. The bean wouldn't load because of the
NoClassDefFoundError. I patched seam to work-around this issue as I didn't see any
other solution (JSF backing beans don't belong in my JPA or EJB layers).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5588
days inactive
5590
days old
7 comments
4 participants
participants (4)
-
Denis Forveille (JIRA) -
John Eckhart (JIRA)
-
Norman Richards (JIRA)
-
Pete Muir (JIRA)