You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2011/06/02 02:16:47 UTC
[jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
CDI EAR deployment issue
------------------------
Key: GERONIMO-5989
URL: https://issues.apache.org/jira/browse/GERONIMO-5989
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment, javaee6
Reporter: David Blevins
Attached is one of many EAR files produced by the CDI TCK that do not deploy. Both the EJB and WAR modules are found and created, but only the WAR starts and has none of the required jars in the classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
Posted by Shawn Jiang <ge...@gmail.com>.
The spec EE 8.3.1 does not specify if the classes in EJB module should be
visible for WAR. But the spec does say app should not depend on such EJB
and WEB module classloading relationship. I think the case is breaking the
rule.
Anyway, in geronimo impl, the content of ejb is visible to war so that we
are fine with the case reqirement.
On Thu, Jun 2, 2011 at 11:38 AM, Kevan Miller <ke...@gmail.com>wrote:
>
> On Jun 1, 2011, at 11:14 PM, Shawn Jiang wrote:
>
> > It's quite tricky because the war and ejb module have the same name,
> Hence, they have the same hashcode because we are returning
> name.hashCode() in Module.hashCode().
> >
> > r1130391 Change to moduleURI.hashCode() will fix this because the URI
> can identify a module. It should be fixed, I will trigger a G JCDI tck to
> see.
>
> Interesting. So, is this the error you were getting?
>
> org.testng.TestNGException:
> Cannot find class in classpath:
> org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest
> org.testng.xml.XmlClass.getSupportClass(XmlClass.java:55)
> org.testng.internal.Utils.xmlClassesToClasses(Utils.java:79)
> org.testng.TestRunner.initMethods(TestRunner.java:289)
> org.testng.TestRunner.init(TestRunner.java:235)
> org.testng.TestRunner.init(TestRunner.java:197)
> org.testng.TestRunner.<init>(TestRunner.java:141)
>
> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:488)
> org.testng.SuiteRunner.privateRun(SuiteRunner.java:250)
> org.testng.SuiteRunner.run(SuiteRunner.java:204)
> org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:912)
> org.testng.TestNG.runSuitesLocally(TestNG.java:876)
> org.testng.TestNG.run(TestNG.java:784)
> org.jboss.testharness.impl.runner.TestRunner.run(TestRunner.java:61)
>
> org.jboss.testharness.impl.runner.servlet.ServletTestRunner.doGet(ServletTestRunner.java:77)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
>
> Can someone refresh my memory as to *why* a class in
> org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest.jar
> should be visible, in this app?
>
> --kevan
>
--
Shawn
Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
Posted by Kevan Miller <ke...@gmail.com>.
On Jun 1, 2011, at 11:14 PM, Shawn Jiang wrote:
> It's quite tricky because the war and ejb module have the same name, Hence, they have the same hashcode because we are returning name.hashCode() in Module.hashCode().
>
> r1130391 Change to moduleURI.hashCode() will fix this because the URI can identify a module. It should be fixed, I will trigger a G JCDI tck to see.
Interesting. So, is this the error you were getting?
org.testng.TestNGException:
Cannot find class in classpath: org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest
org.testng.xml.XmlClass.getSupportClass(XmlClass.java:55)
org.testng.internal.Utils.xmlClassesToClasses(Utils.java:79)
org.testng.TestRunner.initMethods(TestRunner.java:289)
org.testng.TestRunner.init(TestRunner.java:235)
org.testng.TestRunner.init(TestRunner.java:197)
org.testng.TestRunner.<init>(TestRunner.java:141)
org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:488)
org.testng.SuiteRunner.privateRun(SuiteRunner.java:250)
org.testng.SuiteRunner.run(SuiteRunner.java:204)
org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:912)
org.testng.TestNG.runSuitesLocally(TestNG.java:876)
org.testng.TestNG.run(TestNG.java:784)
org.jboss.testharness.impl.runner.TestRunner.run(TestRunner.java:61)
org.jboss.testharness.impl.runner.servlet.ServletTestRunner.doGet(ServletTestRunner.java:77)
javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
Can someone refresh my memory as to *why* a class in org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest.jar should be visible, in this app?
--kevan
Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
Posted by Shawn Jiang <ge...@gmail.com>.
It's quite tricky because the war and ejb module have the same name,
Hence, they have the same hashcode because we are returning
name.hashCode() in Module.hashCode().
r1130391 Change to moduleURI.hashCode() will fix this because the URI can
identify a module. It should be fixed, I will trigger a G JCDI tck to
see.
On Thu, Jun 2, 2011 at 10:02 AM, Shawn Jiang <ge...@gmail.com> wrote:
> I'll take a look.
>
>
> On Thu, Jun 2, 2011 at 8:27 AM, David Blevins <da...@gmail.com>wrote:
>
>> Made great progress in CDI/EJB integration, but seems we have a general
>> issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
>>
>> It looks like the deploy is successful but the EJB module doesn't start.
>> No errors in the log other than the webapp failing to start due to missing
>> EJB jar classes.
>>
>> If someone could take a quick look that would be wonderful. I've attached
>> an example EAR to the JIRA.
>>
>>
>> -David
>>
>> On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:
>>
>> > CDI EAR deployment issue
>> > ------------------------
>> >
>> > Key: GERONIMO-5989
>> > URL:
>> https://issues.apache.org/jira/browse/GERONIMO-5989
>> > Project: Geronimo
>> > Issue Type: Bug
>> > Security Level: public (Regular issues)
>> > Components: deployment, javaee6
>> > Reporter: David Blevins
>> >
>> >
>> > Attached is one of many EAR files produced by the CDI TCK that do not
>> deploy. Both the EJB and WAR modules are found and created, but only the
>> WAR starts and has none of the required jars in the classpath.
>> >
>> > --
>> > This message is automatically generated by JIRA.
>> > For more information on JIRA, see:
>> http://www.atlassian.com/software/jira
>>
>>
>
>
> --
> Shawn
>
--
Shawn
Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
Posted by David Blevins <da...@gmail.com>.
Thanks, Shawn!
On Jun 1, 2011, at 7:02 PM, Shawn Jiang wrote:
> I'll take a look.
>
> On Thu, Jun 2, 2011 at 8:27 AM, David Blevins <da...@gmail.com> wrote:
> Made great progress in CDI/EJB integration, but seems we have a general issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
>
> It looks like the deploy is successful but the EJB module doesn't start. No errors in the log other than the webapp failing to start due to missing EJB jar classes.
>
> If someone could take a quick look that would be wonderful. I've attached an example EAR to the JIRA.
>
>
> -David
>
> On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:
>
> > CDI EAR deployment issue
> > ------------------------
> >
> > Key: GERONIMO-5989
> > URL: https://issues.apache.org/jira/browse/GERONIMO-5989
> > Project: Geronimo
> > Issue Type: Bug
> > Security Level: public (Regular issues)
> > Components: deployment, javaee6
> > Reporter: David Blevins
> >
> >
> > Attached is one of many EAR files produced by the CDI TCK that do not deploy. Both the EJB and WAR modules are found and created, but only the WAR starts and has none of the required jars in the classpath.
> >
> > --
> > This message is automatically generated by JIRA.
> > For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
>
> --
> Shawn
Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
Posted by Shawn Jiang <ge...@gmail.com>.
I'll take a look.
On Thu, Jun 2, 2011 at 8:27 AM, David Blevins <da...@gmail.com>wrote:
> Made great progress in CDI/EJB integration, but seems we have a general
> issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
>
> It looks like the deploy is successful but the EJB module doesn't start.
> No errors in the log other than the webapp failing to start due to missing
> EJB jar classes.
>
> If someone could take a quick look that would be wonderful. I've attached
> an example EAR to the JIRA.
>
>
> -David
>
> On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:
>
> > CDI EAR deployment issue
> > ------------------------
> >
> > Key: GERONIMO-5989
> > URL: https://issues.apache.org/jira/browse/GERONIMO-5989
> > Project: Geronimo
> > Issue Type: Bug
> > Security Level: public (Regular issues)
> > Components: deployment, javaee6
> > Reporter: David Blevins
> >
> >
> > Attached is one of many EAR files produced by the CDI TCK that do not
> deploy. Both the EJB and WAR modules are found and created, but only the
> WAR starts and has none of the required jars in the classpath.
> >
> > --
> > This message is automatically generated by JIRA.
> > For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
>
--
Shawn
Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue
Posted by David Blevins <da...@gmail.com>.
Made great progress in CDI/EJB integration, but seems we have a general issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
It looks like the deploy is successful but the EJB module doesn't start. No errors in the log other than the webapp failing to start due to missing EJB jar classes.
If someone could take a quick look that would be wonderful. I've attached an example EAR to the JIRA.
-David
On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:
> CDI EAR deployment issue
> ------------------------
>
> Key: GERONIMO-5989
> URL: https://issues.apache.org/jira/browse/GERONIMO-5989
> Project: Geronimo
> Issue Type: Bug
> Security Level: public (Regular issues)
> Components: deployment, javaee6
> Reporter: David Blevins
>
>
> Attached is one of many EAR files produced by the CDI TCK that do not deploy. Both the EJB and WAR modules are found and created, but only the WAR starts and has none of the required jars in the classpath.
>
> --
> This message is automatically generated by JIRA.
> For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-5989) CDI EAR deployment issue
Posted by "David Blevins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins updated GERONIMO-5989:
------------------------------------
Attachment: EnterpriseQualifierDefinitionTest.ear
As of OpenEJB/OpenWebBeans/XBean r1130358, this test should pass.
> CDI EAR deployment issue
> ------------------------
>
> Key: GERONIMO-5989
> URL: https://issues.apache.org/jira/browse/GERONIMO-5989
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: deployment, javaee6
> Reporter: David Blevins
> Labels: cdi, deployment, ear, ejb, tck
> Attachments: EnterpriseQualifierDefinitionTest.ear
>
>
> Attached is one of many EAR files produced by the CDI TCK that do not deploy. Both the EJB and WAR modules are found and created, but only the WAR starts and has none of the required jars in the classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira