[JBoss JIRA] Created: (JBWS-3322) Ensure proper creation of WebMD for EJBs present in web archive.
by Richard Opalka (JIRA)
Ensure proper creation of WebMD for EJBs present in web archive.
----------------------------------------------------------------
Key: JBWS-3322
URL: https://issues.jboss.org/browse/JBWS-3322
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-integration
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
15:21:48,858 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.subunit."jaxws-jbws2957-ejbinwarwebinflib.ear"."jaxws-jbws2957-ejbinwarwebinflib_web.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."jaxws-jbws2957-ejbinwarwebinflib.ear"."jaxws-jbws2957-ejbinwarwebinflib_web.war".INSTALL: Failed to process phase INSTALL of subdeployment "jaxws-jbws2957-ejbinwarwebinflib_web.war" of deployment "jaxws-jbws2957-ejbinwarwebinflib.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22]
at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
Caused by: java.lang.NullPointerException
at org.jboss.as.webservices.util.WebMetaDataHelper.getServlets(WebMetaDataHelper.java:130)
at org.jboss.as.webservices.tomcat.WebMetaDataCreator.createServlets(WebMetaDataCreator.java:174)
at org.jboss.as.webservices.tomcat.WebMetaDataCreator.createWebAppDescriptor(WebMetaDataCreator.java:110)
at org.jboss.as.webservices.tomcat.WebMetaDataCreator.create(WebMetaDataCreator.java:94)
at org.jboss.as.webservices.tomcat.WebMetaDataCreatingDeploymentAspect.start(WebMetaDataCreatingDeploymentAspect.java:48)
at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.internalDeploy(AspectDeploymentProcessor.java:78)
at org.jboss.as.webservices.deployers.TCCLDeploymentProcessor.deploy(TCCLDeploymentProcessor.java:42)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
... 5 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBWS-3321) Enhance ModelDeploymentAspect to generate compatible PathElements
by Richard Opalka (JIRA)
Enhance ModelDeploymentAspect to generate compatible PathElements
-----------------------------------------------------------------
Key: JBWS-3321
URL: https://issues.jboss.org/browse/JBWS-3321
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-integration
Reporter: Richard Opalka
Assignee: Richard Opalka
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
<servlet-name> element can contain any string, including spaces.
PathElement used in ModelDeploymentAspect forbids space usage.
We need to encode endpoint name (which maps to servlet name)
to the special string somehow so it will be compatible
with PathElement value restrictions.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBWS-3315) MTOM/XOP root MIME part does not contain charset parameter
by Brad Maxwell (JIRA)
MTOM/XOP root MIME part does not contain charset parameter
----------------------------------------------------------
Key: JBWS-3315
URL: https://issues.jboss.org/browse/JBWS-3315
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.2.2
Reporter: Brad Maxwell
Assignee: Alessio Soldano
Fix For: jbossws-native-3.3.0.CR1
Web service responses sent from JBoss that are MTOM/XOP encoded cannot be parsed by some clients because the root MIME part does not contain charset parameter.
RFC2616 Sections 14.17 and 3.7.1 state that the charset is not required unless it differs from the implicit default of "ISO-8859-1". JBossWS is encoding the root MIME part in UTF8, so the charset must be provided.
As such, this is a bug in JBossWS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] Created: (JBWS-3312) Cleanup previously deprecated methods
by Alessio Soldano (JIRA)
Cleanup previously deprecated methods
-------------------------------------
Key: JBWS-3312
URL: https://issues.jboss.org/browse/JBWS-3312
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jbossws-cxf, jbossws-integration, jbossws-native
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
Especially in the jbossws-spi Endpoint area, we have previously deprecated methods that can now be cleaned up (as part of the AS7 JMS-WS integration work, for instance)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 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
12 years, 10 months