[JBoss JIRA] Commented: (JBIDE-6464) Running a SeamTest when multiple projects are open in the Eclipse workspace fails
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin... ]
Alexey Kazakov commented on JBIDE-6464:
---------------------------------------
The reason of that failure is that Project1.ejb has Project1.ear/EarContent/jboss-seam.jar in its classpath.
It's not correct if you use Project1.ejb as a module of Project2.ear.
So you have to configure your project correctly:
1. Go to Properties for Project1.ejb -> Java Build Path -> Libraries ->
2. Remove Project1.ear/EarContent/jboss-seam.jar
3. Add Project2.ear/EarContent/jboss-seam.jar
So now your module Project1.ejb is configured correctly and you can run the tests.
> Running a SeamTest when multiple projects are open in the Eclipse workspace fails
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-6464
> URL: https://issues.jboss.org/browse/JBIDE-6464
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Seam2
> Environment: XP, JBoss 5.1.0 GA, Seam 2.2.0 GA, JBoss Tools 3.1.0 GA
> Reporter: Shu-Wei Tan
> Assignee: Alexey Kazakov
> Fix For: 3.3.x
>
>
> My eclipse workspace contains 2 JBoss Tools generated Seam projects:
> - Project1.war
> - Project1.ear
> - Project1.ejb
> - Project1.test
> - Project2.war
> - Project2.ear
> - Project2.ejb
> - Project2.test
> Project2.ear depends on both Project1.ejb and Project2.ejb.
> Project2.test contains a SeamTest test case. When running that test case, I get an exception saying TimerServiceDispatcher already deployed. This is because jboss-seam.jar seems to be picked up twice by the bootstrap process, once from Project1.ear and once from Project2.ear.
> If I close the Project1.ear project in Eclipse then rerun the test, it works.
> Here's the exception (the actual project name is different from my simplified example above):
> ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Real: name=vfsjar:file:/E:/gbahn/SeamProjects/General/General-ear/EarContent/jboss-seam.jar!/ state=PostClassLoader mode=Manual requiredState=Real
> org.jboss.deployers.spi.DeploymentException: Error deploying jboss-seam.jar: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:158)
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:88)
> at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalDeploy(AbstractVFSRealDeployer.java:45)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
> at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127)
> at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289)
> at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:19)
> at org.jboss.seam.mock.AbstractSeamTest.startJbossEmbeddedIfNecessary(AbstractSeamTest.java:1024)
> at org.jboss.seam.mock.AbstractSeamTest.startSeam(AbstractSeamTest.java:915)
> at org.jboss.seam.mock.SeamTest.startSeam(SeamTest.java:58)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:607)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:417)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:154)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:88)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:284)
> at org.testng.SuiteRunner.run(SuiteRunner.java:204)
> at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:877)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:842)
> at org.testng.TestNG.run(TestNG.java:751)
> at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73)
> at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124)
> Caused by: org.jboss.deployers.spi.DeploymentException: Error creating ejb container TimerServiceDispatcher: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:540)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:486)
> at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:468)
> at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:434)
> at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:376)
> at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:145)
> ... 36 more
> Caused by: java.lang.IllegalStateException: Container jboss.j2ee:jar=jboss-seam.jar,name=TimerServiceDispatcher,service=EJB3,VMID=5822310e5111fa1a:7ef46a7d:128f1d23da7:-8000 + is already registered
> at org.jboss.ejb3.Ejb3Registry.register(Ejb3Registry.java:128)
> at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:536)
> ... 41 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBDS-1682) Add Atlassian Mylyn-JIRA features to update site (if possible)
by Nick Boldt (JIRA)
Add Atlassian Mylyn-JIRA features to update site (if possible)
--------------------------------------------------------------
Key: JBDS-1682
URL: https://issues.jboss.org/browse/JBDS-1682
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: updatesite
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.M3
Ran into some compatibility issues w/ the Atlassian JIRA plugins for Mylyn, so they've all been removed from the 5.0 Extras site pending further investigation into compatibility. Might have to respin those features ourselves and fix their requirement ranges so they're not so strictly tied to old Orbit bundles like:
* org.apache.commons.httpclient [3.1.0.v201005080502]
* javax.wsdl [1.6.2.v201005080631]
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBDS-1798) Hide 3rd party features from JBDS Extras site - only com.jboss.jbds.* features should be exposed
by Nick Boldt (JIRA)
Hide 3rd party features from JBDS Extras site - only com.jboss.jbds.* features should be exposed
------------------------------------------------------------------------------------------------
Key: JBDS-1798
URL: https://issues.jboss.org/browse/JBDS-1798
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Reporter: Nick Boldt
1. instead of including 3rd party features in com.jboss.jbds.* features, include contained plugins.
2. rewrite com.jboss.jbds.* features to list out contents so it's clear what versions of 3rd party stuff are included.
Benefits:
* anything installable from JBDS Extras site is a feature we build and maintain (and test and support).
* to install any non-com.jboss 3rd party feature, must go to 3rd party site (or jboss.org community mirror). Because this is "off the reservation", it's not supported, and users' mileage may vary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBDS-1800) jbds updatesites are too "big", need to split/divide
by Max Rydahl Andersen (JIRA)
jbds updatesites are too "big", need to split/divide
----------------------------------------------------
Key: JBDS-1800
URL: https://issues.jboss.org/browse/JBDS-1800
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Fix For: 4.1.0.GA
Suggestion from chat discussion is that we where possible will include org.* features in a certified jbds feature and put the org.* features in uncategorized as a "safety valve" in case users want to go on their own and install piecemal.
For features were we can't just include org.* features because of some tycho or versionng limitation we should at least avoid bulking unrelated features together - i.e. subclipse and subversive shouldn't be bundled together.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months