June 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss internal QA (Test Suite)] - ant 1.7.0 junit issue

by scott.stark＠jboss.org

I have been seeing this for a while on osx when I updated to ant 1.7.0 but thought it might be osx specific. I'm seeing it on fedora 9 as well, so its some ant/junit issue. The test runs fine but the junit monitor behavior seems to lose track of the test. | [starksm@banshee testsuite]$ ant -Dtest=org.jboss.test.web.test.WebIntegrationUnitTestCase one-test | Buildfile: build.xml | | one-test: | [junit] Tests run: 37, Failures: 1, Errors: 0, Time elapsed: 23.579 sec | [junit] java.io.FileNotFoundException: /home/svn/JBossHead/trunk/testsuite/junitvmwatcher694724713.properties (No such file or directory) | [junit] at java.io.FileInputStream.open(Native Method) | [junit] at java.io.FileInputStream.<init>(FileInputStream.java:106) | [junit] at java.io.FileReader.<init>(FileReader.java:55) | [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeAsForked(JUnitTask.java:1028) | [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:817) | [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.executeOrQueue(JUnitTask.java:1657) | [junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTask.execute(JUnitTask.java:764) | [junit] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) | [junit] at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) | [junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | [junit] at java.lang.reflect.Method.invoke(Method.java:585) | [junit] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105) | [junit] at org.apache.tools.ant.Task.perform(Task.java:348) | [junit] at org.apache.tools.ant.Target.execute(Target.java:357) | [junit] at org.apache.tools.ant.Target.performTasks(Target.java:385) | [junit] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329) | [junit] at org.apache.tools.ant.Project.executeTarget(Project.java:1298) | [junit] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41) | [junit] at org.apache.tools.ant.Project.executeTargets(Project.java:1181) | [junit] at org.apache.tools.ant.Main.runBuild(Main.java:698) | [junit] at org.apache.tools.ant.Main.startAnt(Main.java:199) | [junit] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257) | [junit] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104) | [junit] Running org.jboss.test.web.test.WebIntegrationUnitTestCase | [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0 sec | [junit] Test org.jboss.test.web.test.WebIntegrationUnitTestCase FAILED (crashed) | | BUILD SUCCESSFUL | Total time: 28 seconds | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157021#4157021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157021

16 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: VFS security issues for jbossweb

by scott.stark＠jboss.org

Sounds fine. The issue is testing it. I guess the test itself should determine if its being run on a case insensitive file system. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157019#4157019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157019

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - AOP and CL warning at undeploy

by alesj

When stopping server with previously deployed Seam app, I get this nasty warning: | 15:09:13,875 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1f79045 | 15:09:13,890 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1f79045 | 15:09:13,906 WARN [AspectDeployer] Error undeploying xml ejb3-interceptors-aop.xml from org.jboss.aop.AspectManager@1e0e650 | java.lang.RuntimeException: java.lang.IllegalStateException: BaseClassLoader@3daebc{vfszip:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.CR1/server/default/deploy/jboss-seam-numberguess.ear} classLoader is not connected to a domain (probably und | eployed?) for class org.jboss.ejb3.annotation.SecurityDomain | at org.jboss.aop.pointcut.Util.matchesClassExpr(Util.java:137) | at org.jboss.aop.pointcut.MethodMatcher.matchesClass(MethodMatcher.java:264) | at org.jboss.aop.pointcut.MethodMatcher.matches(MethodMatcher.java:106) | at org.jboss.aop.pointcut.MethodMatcher.visit(MethodMatcher.java:100) | at org.jboss.aop.pointcut.ast.ASTMethod.jjtAccept(ASTMethod.java:44) | at org.jboss.aop.pointcut.ExecutionMethodMatcher.visit(ExecutionMethodMatcher.java:58) | at org.jboss.aop.pointcut.ast.ASTExecution.jjtAccept(ASTExecution.java:37) | at org.jboss.aop.pointcut.MatcherHelper.visit(MatcherHelper.java:89) | at org.jboss.aop.pointcut.MatcherHelper.matches(MatcherHelper.java:83) | at org.jboss.aop.pointcut.PointcutExpression.matchesExecution(PointcutExpression.java:119) | at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:956) | at org.jboss.aop.ClassAdvisor.resolvePointcuts(ClassAdvisor.java:699) | at org.jboss.aop.ClassAdvisor.updateInterceptorChains(ClassAdvisor.java:628) | at org.jboss.aop.ClassAdvisor.doRebuildInterceptors(ClassAdvisor.java:991) | at org.jboss.aop.ClassAdvisor$RebuildInterceptorsAction$2.rebuildInterceptors(ClassAdvisor.java:2186) | at org.jboss.aop.ClassAdvisor.rebuildInterceptors(ClassAdvisor.java:971) | at org.jboss.aop.ClassAdvisor.removeAdviceBindings(ClassAdvisor.java:426) | at org.jboss.aop.AspectManager.removeBindings(AspectManager.java:1422) | at org.jboss.aop.Domain.removeBindings(Domain.java:198) | at org.jboss.aop.AspectXmlLoader.bulkUndeploy(AspectXmlLoader.java:1220) | at org.jboss.aop.AspectXmlLoader.undeployDomain(AspectXmlLoader.java:1091) | at org.jboss.aop.AspectXmlLoader.undeployTopElements(AspectXmlLoader.java:1305) | at org.jboss.aop.AspectXmlLoader.undeployXML(AspectXmlLoader.java:1209) | at org.jboss.aop.deployers.AspectDeployer.undeployXml(AspectDeployer.java:205) | at org.jboss.aop.deployers.AspectDeployer.undeployXml(AspectDeployer.java:189) | at org.jboss.aop.deployers.AspectDeployer.undeploy(AspectDeployer.java:134) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSRealDeployer.internalUndeploy(AbstractVFSRealDeployer.java:54) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.undeploy(AbstractRealDeployer.java:112) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.undeploy(DeployerWrapper.java:197) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doUninstallParentLast(DeployersImpl.java:1189) | at org.jboss.deployers.plugins.deployers.DeployersImpl.uninstall(DeployersImpl.java:1144) | at org.jboss.dependency.plugins.AbstractControllerContext.uninstall(AbstractControllerContext.java:354) | at org.jboss.dependency.plugins.AbstractController.uninstall(AbstractController.java:1406) | at org.jboss.dependency.plugins.AbstractController.uninstallContext(AbstractController.java:1064) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:677) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:510) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.unload(ProfileServiceBootstrap.java:371) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.unloadProfile(ProfileServiceBootstrap.java:332) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.shutdown(ProfileServiceBootstrap.java:160) | at org.jboss.bootstrap.AbstractServerImpl.shutdownServer(AbstractServerImpl.java:508) | at org.jboss.bootstrap.AbstractServerImpl$ShutdownHook.run(AbstractServerImpl.java:827) | Caused by: java.lang.IllegalStateException: BaseClassLoader@3daebc{vfszip:/C:/projects/jboss5/trunk/build/output/jboss-5.0.0.CR1/server/default/deploy/jboss-seam-numberguess.ear} classLoader is not connected to a domain (probably undeployed?) for cla | ss org.jboss.ejb3.annotation.SecurityDomain | at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:723) | at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:372) | at java.lang.ClassLoader.loadClass(ClassLoader.java:251) | at org.jboss.ejb3.metadata.annotation.AnnotationRepositoryToMetaData.loadClass(AnnotationRepositoryToMetaData.java:209) | at org.jboss.ejb3.metadata.annotation.AnnotationRepositoryToMetaData.hasClassAnnotation(AnnotationRepositoryToMetaData.java:328) | at org.jboss.aop.Advisor.hasAnnotation(Advisor.java:412) | at org.jboss.aop.Advisor.hasAnnotation(Advisor.java:387) | at org.jboss.aop.pointcut.Util.matchesClassExpr(Util.java:115) | ... 42 more | I also see the first two warnings at Seam app deploy. Test to reproduce this is: 1) build seam 2) build one-test -Dtest=org.jboss.test.deployers.seam.test.SeamNumberguessExampleTestCase 3) shutdown AS View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157013#4157013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157013

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Seam numberguess cannot find resources

by alesj

Adding root to classpath for ear solves the problem of Seam Numberguess! 1 down, 2 examples to go. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157012#4157012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157012

16 years, 3 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: BaseClassLoader attachement makes DeploymentUnit non-ser

by scott.stark＠jboss.org

Set a breakpoint at the NotSerializableException point in ObjectOutputStream. Its the org.jboss.metadata.ejb.jboss.jndipolicy.spi.DeploymentSummary class that is including a class loader that should be marked as a transient field. It will be fixed in the next jboss-metadata release. http://jira.jboss.com/jira/browse/JBMETA-52 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157008#4157008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157008

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBPAPP-864/EJBTHREE-1109 - clustered home proxies

by galder.zamarreno＠jboss.com

"bstansberry(a)jboss.com" wrote : I'm guessing the reason you use the Dispatcher to find the StatefulClusteredProxyFactory in StatefulContainer.createClusteredProxy(Object id) is you lose the id info if you do it via JNDI? Indeed. I think it might have been possible to retrieve the proxy factory by looking it up in JNDI and the calling any of the createProxies accordingly. I have the feeling that this solution would have indirectly gone through the Dispatcher as well. What was clear though is that I needed to go through factory.createProxy() call to generate this so that the partition, family wrapper...etc where initialised correctly (I did test other alternatives and would fail without these being initialised). In the case of SLSBs, this is much simpler cos getting an instance of the SLSB proxy is just a matter of retrieving it from JNDI as proxies are the same. But in the case of SFSB, it's different cos you have to retrieve the proxy for a specific instance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157006#4157006 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157006

16 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: A problem about soapAction and wsdl in JBossESB

by Kevin.Conner＠jboss.com

Sorry, I haven't received anything. Can you try resending? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157004#4157004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157004

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by scott.stark＠jboss.org

Nothing else should be needed. You could add: | <entry> | <key>persistence</key> | <value>org.jboss.metadata.jpa.spec.PersistenceMetaData</value> | </entry> | as a fallback to map the persistence root element for a descriptor that has no schemaLocation attribute I suppose. That logic might only work if there is no namespace though(dtds), I can't remember. Adding it won't hurt anything. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157001#4157001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157001

16 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Annotation Tests in deployers-vfs

by adrian＠jboss.org

Green. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156999#4156999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156999

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: trunk Ejb3Deployment is incompatible with jbossas trunk

by alesj

"scott.stark(a)jboss.org" wrote : | A new set of entrys for the persistence.xml schemaLocation uri xsd need to be added and mapped to the new PersistenceMetaData. | Is there anything else I can add, apart from this: | <entry> | <key>persistence_1_0.xsd</key> | <value>org.jboss.metadata.jpa.spec.PersistenceMetaData</value> | </entry> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156996#4156996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156996

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008