[JBoss JIRA] Updated: (JBAS-1841) SAR/ServiceController should be a facade over the generic dependency controller
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1841?page=all ]
Dimitris Andreadis updated JBAS-1841:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
> SAR/ServiceController should be a facade over the generic dependency controller
> -------------------------------------------------------------------------------
>
> Key: JBAS-1841
> URL: http://jira.jboss.com/jira/browse/JBAS-1841
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: System service
> Reporter: Adrian Brock
> Assigned To: Adrian Brock
> Priority: Critical
> Fix For: JBossAS-5.0.0.Beta2
>
>
> Rework the ServiceCreator, ServiceConfigurator, ServiceController
> to use the generic deployment controller.
> This will allow MBeans to take part in the same dependency/injection protocol
> as the plain javabeans provided by the MicroContainer.
> It also adds the "Describe" stage to the lifecycle allowing classloading dependencies.
> This will first be prototyped in system2 rather than system.
> The initial work will not include reworking the XML to use JBossXB
> schema binding, but that is obviously desirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-2145) Testsuite JBossMQ destination deployment is broken
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2145?page=all ]
Dimitris Andreadis updated JBAS-2145:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
> Testsuite JBossMQ destination deployment is broken
> --------------------------------------------------
>
> Key: JBAS-2145
> URL: http://jira.jboss.com/jira/browse/JBAS-2145
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Affects Versions: JBossAS-5.0.0.Beta1
> Reporter: Adrian Brock
> Assigned To: Sacha Labourey
> Fix For: JBossAS-5.0.0.Beta2
>
>
> The change to only deploy destinations as part of the testsuite run
> is broken. e.g.
> 2005-08-19 15:03:28,885 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/scratch/cruisecontrol/checkout/jboss-head-testsuite/testsuite/outp
> ut/resources/messaging/test-destinations-full-service.xml
> org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq.destination:name=A,service=Queue
> at org.jboss.system.ServiceCreator.install(ServiceCreator.java:72)
> at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:429)
> at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:151)
> at org.jboss.system.ServiceController.install(ServiceController.java:216)
> at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
> Sacha, why did you change this?
> This needs fixing properly anyway such that the tests run against both JBossMQ and JBoss Messaging.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-2563) Cleanup the build for jboss5
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2563?page=all ]
Dimitris Andreadis updated JBAS-2563:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
> Cleanup the build for jboss5
> ----------------------------
>
> Key: JBAS-2563
> URL: http://jira.jboss.com/jira/browse/JBAS-2563
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Scott M Stark
> Priority: Critical
> Fix For: JBossAS-5.0.0.Beta2
>
>
> The current jboss-head build seems rather crusty with outdated modules (media which I removed) and weird modules like jbossas. From the dev list:
> This is the remoting/jbossas integration code.
> i.e. the UnifiedInvoker
> It shouldn't really be in jbossas which was meant to be the top level build folder replacement for "build"
> e.g. in the new build
> cvs .. co jbossas
> cd jbossas
> ant rebuild
> would pull down all modules and thirdparty and build the release.
> Instead jbossas has turned into another "varia" ;-)
> On Tue, 2005-12-13 at 03:00, Scott M Stark wrote:
> > Why is there this jbossas module in jboss-head when there is also
> > remoting being pulled via the thirdparty?
> >
> We need a plan on cleaning up the jboss-head build using the jbossbuild before creating a jboss5 branch.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-2889) AppClientUnitTestCase doesn't clean up if it fails
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2889?page=all ]
Dimitris Andreadis updated JBAS-2889:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
> AppClientUnitTestCase doesn't clean up if it fails
> --------------------------------------------------
>
> Key: JBAS-2889
> URL: http://jira.jboss.com/jira/browse/JBAS-2889
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Ryan Campbell
> Fix For: JBossAS-5.0.0.Beta2
>
>
> The org.jboss.test.client.test.AppClientUnitTestCase deploys a bunch of services but fails to clean them.
> If you run a CMP test before the AppClientUnitTest, it passes, but if you run it immediately after, it fails:
> > ./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> one-test:
> [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Tests run: 19, Failures: 0, Errors: 0, Time elapsed: 6.04 sec
> > ./build.sh one-test -Dtest=org.jboss.test.client.test.AppClientUnitTestCase
> [junit] Running org.jboss.test.client.test.AppClientUnitTestCase
> [junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 3.149 sec
> [junit] Test org.jboss.test.client.test.AppClientUnitTestCase FAILED
> > ./build.sh one-test -Dtest=org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Running org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase
> [junit] Tests run: 19, Failures: 0, Errors: 19, Time elapsed: 1.05 sec
> [junit] Test org.jboss.test.cmp2.ejbselect.EJBSelectUnitTestCase FAILED
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months
[JBoss JIRA] Updated: (JBAS-3277) Webservices tests deployment exceptions in jboss-head testsuite
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3277?page=all ]
Dimitris Andreadis updated JBAS-3277:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta2
(was: JBossAS-5.0.0.Beta1)
> Webservices tests deployment exceptions in jboss-head testsuite
> ---------------------------------------------------------------
>
> Key: JBAS-3277
> URL: http://jira.jboss.com/jira/browse/JBAS-3277
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Test Suite
> Reporter: Rajesh Rajasekaran
> Assigned To: Thomas Diesler
> Fix For: JBossAS-5.0.0.Beta2
>
>
> All webservices tests in the jboss-head testsuite are unable to deploy the test resources.
> http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-1.5/2006...
> The DeplomentException stack trace is given below.
> org.jboss.deployment.DeploymentException: Could not create deployment: file:/services/cruisecontrol/checkout/jboss-head-testsuite-1.5/testsuite/output/lib/ws4ee-admindevel.jar; - nested throwable: (java.lang.NoClassDefFoundError: org/jboss/webservice/metadata/jaxrpcmapping/MethodParamPartsMapping)
> at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
> at org.jboss.deployment.MainDeployer.create(MainDeployer.java:975)
> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
> at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:560)
> ..................................
> Caused by: java.lang.NoClassDefFoundError: org/jboss/webservice/metadata/jaxrpcmapping/MethodParamPartsMapping
> at org.jboss.ws.server.WebServiceDeployerEJB21.createWebServicesMetaData(WebServiceDeployerEJB21.java:110)
> at org.jboss.ws.server.WebServiceDeployer.create(WebServiceDeployer.java:103)
> at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
> at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
> at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years, 8 months