[JBoss JIRA] Created: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
2 p.m.
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with
weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss Tools
seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:09 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Ales Justin commented on JBAS-8754:
-----------------------------------
> (but it will work on all previous AS versions)
All previous such as what?
I doubt this ever worked in AS5/6, due to JBAS-6843 bug.
(could be some early AS5 versions, which had diff scanning mechanism)
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:55 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Max Andersen commented on JBAS-8754:
------------------------------------
from JBIDE-7932": "Shelly, this EAR works in JBoss AS 5.1.0.GA and 5.0.1."
(which includes EAP 5 and EAP 5.1)
Thus this is a regression from all definitions I know.
Anything we can do to fix it ?
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Carlo de Wolf edited comment on JBAS-8754 at 12/23/10 3:27 AM:
---------------------------------------------------------------
Abusing a bug is not regression.
I think the app expects one EjbSynchronizations to be present. The ear must be packaged to
reflect that.
JavaEE 6 EE.8.5.2 Bullet 4:
Note that the presence of component-declaring annotations in shared artifacts, such as
libraries in the library directory and libraries referenced by more than one module
through Class-Path references, can have unintended and undesirable consequences and is not
recommended.
was (Author: wolfc):
Abusing a bug is not regression.
I think the app expects one EjbSynchronizations to be present. The ear must be packaged to
reflect that.
JavaEE 6 EE.8.5.2 Bullet 4:
Note that the presence of component-declaring annotations in shared artifacts, such as
libraries in the library directory and libraries referenced by more than one module
through Class-Path references, can have unintended and undesirable
consequences and is not recommended.
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:28 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Carlo de Wolf commented on JBAS-8754:
-------------------------------------
Abusing a bug is not regression.
I think the app expects one EjbSynchronizations to be present. The ear must be packaged to
reflect that.
JavaEE 6 EE.8.5.2 Bullet 4:
Note that the presence of component-declaring annotations in shared artifacts, such as
libraries in the library directory and libraries referenced by more than one module
through Class-Path references, can have unintended and undesirable
consequences and is not recommended.
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:59 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Max Andersen commented on JBAS-8754:
------------------------------------
Carlo,
You need to be a bit more informative please since your comment is as confusing as the
exception being thrown ;)
Which part of the EAR is causing the problem ?
Is that we put a jar in the manifest classpath the problem ? Why is that a problem - its
just a jar.
How is that ever related to what synchronization annotations that are expected on classes
? Causing failure at this point is rather uninformative nor very userfriendly.
Again, if this is what AS 6 will be released with it will not be able to deploy EAR's
that have been working fine on AS 5, AS 5.1 (I think even back to AS 4) and if we
"fix" this
by removing the classpath entry in the manifest.mf Eclipse "looses" its ability
to see what classes to compile against.
I would love to fix that problem too but that is unfortunately not our codebase nor
something we could fix within the AS 6 release time.
Thus I would like to understand why we have "regressed" or "become more
strict" (depending on your POV) and what we can do about it for AS 6 release time ?
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:20 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8754:
------------------------------------
> You need to be a bit more informative please since your comment
is as confusing as the exception being thrown ;)
Max, Ales recently fixed an issue in processing MANIFEST.MF file. If you now deploy the
application attached to https://issues.jboss.org/browse/JBIDE-7932 against the latest AS
nightly build, you will see a _relatively_ better error message about duplicate binding
exception for the EJBs.
The problem is that the jboss-seam.jar (which has EJBs within it) gets listed twice, once
in the application.xml and then again as a ClassPath element in the MANIFEST.MF of another
EJB deployment. This leads to the EJBs in the jboss-seam.jar being deployed/processed
twice. This has always been a problem (although it kept manifesting itself in different
ways).
As Carlo points out from the spec:
JavaEE 6 EE.8.5.2 Bullet 4:
Note that the presence of component-declaring annotations in shared artifacts, such as
libraries in the library directory and libraries referenced by more than one module
through Class-Path references, can have unintended and undesirable consequences and is not
recommended.
The effect of having a jar (in this case jboss-seam.jar) containing component-declaring
annotations (for example, EJB bean annotation like @Stateful ) referenced through
Class-Path element of MANIFEST.MF can have undesired and unintended consequences and is
not recommended.
> if we "fix" this by removing the classpath entry in the
manifest.mf Eclipse "looses" its ability to see what classes to compile against.
I'm not an IDE guy, so I don't know much, but I thought Eclipse uses the
.classpath file to setup classpaths and not the MANIFEST.MF of the jar. Isn't that the
case?
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Max Andersen commented on JBAS-8754:
------------------------------------
1) Having duplicate jars on the classpath is not an uncommon thing; its used for
overloading in many places but also its a challenge for many IDE's / build tools to
keep clean because of inconsistent metadata - and there is a simple rule to handle this:
Only look at the first class you find; and in this case it is literally the same file.
We had the same problem in Seam 2.x where they suddenly exploded because a class was found
twice because of how Seam's hot deployment works + Eclipse packaging it causes double
listng of classes - again solution was to ignore those found later in the
classpath/classloader.
I completely understand it is not recommended but why is the app server not obeying
ancient old classpath resolution mechanisms ?
2) Yes, the .classpath file defines this but these contains references to a classpath
container that reads the manifest.mf files of the related project to avoid users to
specify things twice.
And unfortunately Eclipse has a problem too with lib directories and manifest.mf in the
sense that it uses the manifest.mf to find the classpath for ejb jars inside an EAR
requiring us to list
it in manifest.mf to not have problems there (which is fine since it literally is the
*same* jar)
If this is really how AS 6 wants to behave then thats gonna be tough/impossible to support
:(
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:12 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Max Andersen commented on JBAS-8754:
------------------------------------
my point is - yes, this is not a good system but it (classpath ordering) is the only
"exhaust-valve" we have to make things works across IDE's/AS versions/build
systems. Thus it should be allowed IMO; feel free to push out a warning.
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:27 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
[
https://issues.jboss.org/browse/JBAS-8754?page=com.atlassian.jira.plugin....
]
Jason Greene reopened JBAS-8754:
--------------------------------
Due to feedback from the community, I have split the AS7 and AS6 projects and reopened all
unscheduled AS6 issues that are a year or less old. This will make it easier community
members to find and work on them.
Future releases beyond 6.1 can be done provided a community member steps up to coordinate
them.
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS
6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Rydahl Andersen
Assignee: Shelly McGowan
Priority: Blocker
Fix For: No Release
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss
Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects)
created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5031
days inactive
5155
days old
9 comments
5 participants
participants (5)
-
Ales Justin (JIRA) -
Carlo de Wolf (JIRA)
-
jaikiran pai (JIRA)
-
Jason Greene (JIRA)
-
Max Andersen (JIRA)