December 2007 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: Embedded - EJB deployment problems

by pete.muir＠jboss.org

"scott.stark(a)jboss.org" wrote : The standardjboss.xml should be a property on the JBossEjbParsingDeployer. I have added a standardJBossXmlPath for the standardjboss.xml URL, along with an ignoreMissingStandardJBossXml that can be set to false to allow for use of the JBossEjbParsingDeployer without a standardjboss.xml. A pure ejb3 setup would not need it Ok, but I still get the exception. It originates on line 199 URL configUrl = new URL(configPath); and caught and rethrown catch (Exception ex) | { | DeploymentException.rethrowAsDeploymentException(ex.getMessage(), ex); | } This is without my alteration to embedded bootstrap to set the SERVER_CONFIG_URL and with this xml <bean name="JBossEjb2ParsingDeployer" class="org.jboss.deployment.JBossEjbParsingDeployer"> | <property name="type">ejb2x</property> | <property name="relativeOrder">3001</property> | <property name="useSchemaValidation">false</property> | <property name="ignoreMissingStandardJBossXml">true</property> | </bean> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110356#4110356 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110356

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Embedded - EJB deployment problems

by scott.stark＠jboss.org

"scott.stark(a)jboss.org" wrote : ... along with an ignoreMissingStandardJBossXml that can be set to false to allow for use of the JBossEjbParsingDeployer without a standardjboss.xml. Correction, ignoreMissingStandardJBossXml would need to be set to true to allow for a setup without a standardjboss.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110350#4110350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110350

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Embedded - EJB deployment problems

by scott.stark＠jboss.org

"pete.muir(a)jboss.org" wrote : | This is caused by getStandardMetaData assuming that the SERVER_CONFIG_URL system property is set (Embedded doesn't set this). I have worked around this in Embedded bootstrap by setting the property (and adding standardjboss.xml to the bootstrap/conf directory), but I don't know if this is the correct solution. | The standardjboss.xml should be a property on the JBossEjbParsingDeployer. I have added a standardJBossXmlPath for the standardjboss.xml URL, along with an ignoreMissingStandardJBossXml that can be set to false to allow for use of the JBossEjbParsingDeployer without a standardjboss.xml. A pure ejb3 setup would not need it. "pete.muir(a)jboss.org" wrote : | 2) Having done this, I find that no EJBs from WEB-INF/lib/jboss-seam.jar are being deployed so transaction synchronization fails. This may of course be due to my fix to (1). | It would not be due to changes for 1. Most like due to an interaction with the new AnnotationMetaDataDeployer and the Ejb3Deployer. I don't think its processing war libs for ejb deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110349#4110349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110349

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JavaEE Deployers need redoing again

by scott.stark＠jboss.org

The mc tests need to focus on the types of deployer chains we are using (merging multiple sources of metadata), the new pre-real deployer state, annotation support, support for metadata complete deployments that bypass parsing deployers, etc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110340#4110340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110340

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Embedded - EJB deployment problems

by pete.muir＠jboss.org

(2) is caused by not having an ejb-jar.xml (or I guess jboss.xml) in jboss-seam.jar. I'm not sure if this is intentional, but it is certainly a change from AS 4.2 and other EE servers like Glassfish and OC4J. I will post this in the EJB3 forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110338#4110338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110338

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JavaEE Deployers need redoing again

by alesj

"scott.stark(a)jboss.org" wrote : We need tests in both. The AS tests should initially focus on the various combinations of metadata sources: | What about in MC? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110326#4110326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110326

18 years, 1 month

1
0
0 / 0

[Design of JBoss IIOP on JBoss] - Re: tomcat deployer dependency on jboss-iiop.jar

by sguilhen＠redhat.com

Francisco, I think that downloading stubs via HTTP is not applicable in this case because the stubs are generated by the RI, and are available in the web app war file that is deployed on JBoss. Thus, I don't think the RI's IORs include a codebase URL to indicate where to download the stubs from. This brings us to another discussion: why WebAppClassLoader has to dynamically generate stubs that are already available in the wep app war file? After taking another look at issues JBCTS-591 and JBCTS-609, I have to agree with Francisco that the dependency on IIOPStubCompiler looks unnecessary, as the WebAppClassLoader should be able to load the stub classes from the deployed war file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110321#4110321 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110321

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Embedded - EJB deployment problems

by pete.muir＠jboss.org

I'm seeing two problems currently (apart from hibernate being able to scan for Entities). Both of these were working in my checkout from Friday 1) [testng] ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Parse: name=vfsfile:/Users/pmuir/workspace/jboss-seam/examples/booking/test-build/ state=Not Installed mode=Manual requiredState=Parse | [testng] org.jboss.deployers.spi.DeploymentException | [testng] at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | [testng] at org.jboss.deployment.JBossEjbParsingDeployer.getStandardMetaData(JBossEjbParsingDeployer.java:180) | [testng] at org.jboss.deployment.JBossEjbParsingDeployer.createMetaData(JBossEjbParsingDeployer.java:89) | [testng] at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:162) | [testng] at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) | [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853) | [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794) | [testng] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327) | [testng] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309) | [testng] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734) | [testng] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862) | [testng] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784) | [testng] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622) | [testng] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411) | [testng] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498) | [testng] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506) | [testng] at org.jboss.embedded.DeploymentGroup.process(DeploymentGroup.java:127) | [testng] at org.jboss.embedded.Bootstrap.deployResourceBases(Bootstrap.java:289) | [testng] at org.jboss.seam.mock.EmbeddedBootstrap.startAndDeployResources(EmbeddedBootstrap.java:16) | [testng] at org.jboss.seam.mock.BaseSeamTest.startJbossEmbeddedIfNecessary(BaseSeamTest.java:1006) | [testng] at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:930) | [testng] at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) | [testng] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | [testng] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | [testng] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | [testng] at java.lang.reflect.Method.invoke(Method.java:585) | [testng] at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:604) | [testng] at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:394) | [testng] at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:142) | [testng] at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:79) | [testng] at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:165) | [testng] at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:103) | [testng] at org.testng.TestRunner.runWorkers(TestRunner.java:678) | [testng] at org.testng.TestRunner.privateRun(TestRunner.java:624) | [testng] at org.testng.TestRunner.run(TestRunner.java:495) | [testng] at org.testng.SuiteRunner.runTest(SuiteRunner.java:300) | [testng] at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:295) | [testng] at org.testng.SuiteRunner.privateRun(SuiteRunner.java:275) | [testng] at org.testng.SuiteRunner.run(SuiteRunner.java:190) | [testng] at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:792) | [testng] at org.testng.TestNG.runSuitesLocally(TestNG.java:765) | [testng] at org.testng.TestNG.run(TestNG.java:699) | [testng] at org.testng.TestNG.privateMain(TestNG.java:824) | [testng] at org.testng.TestNG.main(TestNG.java:802) | [testng] Caused by: java.net.MalformedURLException | [testng] at java.net.URL.<init>(URL.java:601) | [testng] at java.net.URL.<init>(URL.java:464) | [testng] at java.net.URL.<init>(URL.java:413) | [testng] at org.jboss.deployment.JBossEjbParsingDeployer.getStandardMetaData(JBossEjbParsingDeployer.java:170) | [testng] ... 42 more This is caused by getStandardMetaData assuming that the SERVER_CONFIG_URL system property is set (Embedded doesn't set this). I have worked around this in Embedded bootstrap by setting the property (and adding standardjboss.xml to the bootstrap/conf directory), but I don't know if this is the correct solution. 2) Having done this, I find that no EJBs from WEB-INF/lib/jboss-seam.jar are being deployed so transaction synchronization fails. This may of course be due to my fix to (1). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110317#4110317 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110317

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JavaEE Deployers need redoing again

by scott.stark＠jboss.org

We need tests in both. The AS tests should initially focus on the various combinations of metadata sources: - annotation only deployment - standard descriptor, metadata complete deployment - standard descriptor + annotations - jboss descriptor + annotations ... - profile service type of metadata override to see that parsing type deployers are bypassed View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110316#4110316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110316

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JavaEE Deployers need redoing again

by alesj

"scott.stark(a)jboss.org" wrote : | Yes, the current deployment tests in the mc are way too simple. We need tests that exercise deployers at every stage. | I can work on this (for CR1), just give me initial requirements. Should this tests be in MC or AS or both? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110306#4110306 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110306

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums December 2007