[JBoss JIRA] Created: (JBWS-3215) Review the way testsuite is run using Maven
by Alessio Soldano (JIRA)
Review the way testsuite is run using Maven
-------------------------------------------
Key: JBWS-3215
URL: https://issues.jboss.org/browse/JBWS-3215
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-native, productization
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
Instead of requiring us/users to do what follows to run the testsuite
> mvn -Ptestsuite,jbossXYZ -DjbossXYZ.home=.. test
we should probably be able to support something like:
> mvn -DjbossXYZ.home=.. integration-test
The move of non-unit tests to integration-test phase is being done as part of JBWS-3210, the rest is probably a matter of implicitly getting the target container from the jbossXYZ.home defined in the env and removing the testsuite profile / automatically enabling the testsuite modules, which just have integration tests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] Created: (JBWS-3234) JNDI over RMI not supported on AS7 yet
by Richard Opalka (JIRA)
JNDI over RMI not supported on AS7 yet
--------------------------------------
Key: JBWS-3234
URL: https://issues.jboss.org/browse/JBWS-3234
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Richard Opalka
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
<opalka> wolfc, dmlloyd I'm not able to connect to JNDI on AS7. in the AS7 config I see it should be running on 1099, but I'm getting http://fpaste.org/wgy8/ :(
<opalka> wolfc, dmlloyd in the config I see the following ports defined
<opalka> ---
<opalka> <socket-binding name="jndi" port="1099"/>
<opalka> <socket-binding name="jmx-connector-registry" port="1090"/>
<opalka> <socket-binding name="jmx-connector-server" port="1091"/>
<opalka> ---
<dmlloyd> we don't do JNDI over RMI anymore
<dmlloyd> that listing is an error
<opalka> dmlloyd, So we're not able to do JNDI lookups to AS7 anymore and don't plan to?
<opalka> dmlloyd, or we'll be doing JNDI over different binary protocol?
<dmlloyd> no, we will be able to, it'll just work somewhat differently
<opalka> dmlloyd, ok, I'm excluding the tests then ...
<opalka> dmlloyd, Is there a JIRA covering this issue so I can use it in my excludes comment?
<dmlloyd> not that I'm aware of, it's just an outstanding task
<dmlloyd> remote invocation is not planned to be covered in next months' beta release
<opalka> dmlloyd, ok, thx for info ;)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBWS-3257) No class available with name 'org.jboss.security.plugins.JaasSecurityDomain'
by Richard Opalka (JIRA)
No class available with name 'org.jboss.security.plugins.JaasSecurityDomain'
----------------------------------------------------------------------------
Key: JBWS-3257
URL: https://issues.jboss.org/browse/JBWS-3257
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Fix For: jbossws-native-4.0
15:09:47,379 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."jaxws-jbws3182-service.sar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-jbws3182-service.sar".INSTALL: Failed to process phase INSTALL of deployment "jaxws-jbws3182-service.sar"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]
Caused by: java.lang.IllegalStateException: No class available with name 'org.jboss.security.plugins.JaasSecurityDomain'
at org.jboss.msc.value.LookupClassValue.getValue(LookupClassValue.java:70)
at org.jboss.msc.value.LookupClassValue.getValue(LookupClassValue.java:32)
at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54)
at org.jboss.msc.value.LookupConstructorValue.getValue(LookupConstructorValue.java:66)
at org.jboss.msc.value.LookupConstructorValue.getValue(LookupConstructorValue.java:37)
at org.jboss.msc.value.CachedValue.getValue(CachedValue.java:54)
at org.jboss.msc.value.ConstructedValue.<init>(ConstructedValue.java:51)
at org.jboss.as.service.ParsedServiceDeploymentProcessor.addService(ParsedServiceDeploymentProcessor.java:127)
at org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:102)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] Created: (JBWS-3240) Rewrite tests relying on $JBOSS_HOME/server/default/tmp/jbossws folder existence
by Richard Opalka (JIRA)
Rewrite tests relying on $JBOSS_HOME/server/default/tmp/jbossws folder existence
--------------------------------------------------------------------------------
Key: JBWS-3240
URL: https://issues.jboss.org/browse/JBWS-3240
Project: JBoss Web Services
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Richard Opalka
Fix For: jbossws-native-4.0
junit.framework.AssertionFailedError: Temp dir doesn't exist: /server/default/tmp/jbossws
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.jboss.test.ws.jaxws.samples.xop.doclit.XOPBase.testAttachmentpartSwap(XOPBase.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at junit.framework.TestCase.runTest(TestCase.java:154)
at junit.framework.TestCase.runBare(TestCase.java:127)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.extensions.TestSetup.run(TestSetup.java:23)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98)
at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107)
at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
at $Proxy0.invoke(Unknown Source)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months