March 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2979) Switch to Netty 3.2.0.BETA1

by Richard Opalka (JIRA)

Switch to Netty 3.2.0.BETA1 --------------------------- Key: JBWS-2979 URL: https://jira.jboss.org/jira/browse/JBWS-2979 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Affects Versions: jbossws-native-3.3.0.CR1, jbossws-metro-3.3.0.CR1, jbossws-cxf-3.3.0.CR1 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.0, jbossws-metro-3.3.0, jbossws-cxf-3.3.0 AS trunk uses it -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2923) Move all jbossws jars from deployers to common/lib folder

by Alessio Soldano (JIRA)

Move all jbossws jars from deployers to common/lib folder --------------------------------------------------------- Key: JBWS-2923 URL: https://jira.jboss.org/jira/browse/JBWS-2923 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-integration, jbossws-metro, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0, jbossws-metro-3.3.0, jbossws-native-3.3.0 This is basically for two reasons: - slim down the AS distribution - allow for an easier handling of the double deployer (jaxws / jaxrpc) structure when using jbossws-cxf and jbossws-metro stacks There shouldn't be major issues with this, except for some tuning / changes required in the installation / deploy scripts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
5
0 / 0

[JBoss JIRA] Created: (JBWS-2974) Allow eager load of CXF Bus during deployment

by Alessio Soldano (JIRA)

Allow eager load of CXF Bus during deployment --------------------------------------------- Key: JBWS-2974 URL: https://jira.jboss.org/jira/browse/JBWS-2974 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-3.3.0 Currently the CXF Bus is created when CXFServlet serving a given endpoint is first initialized. This jira is for allowing users to have the bus created at deploy time (iow no lazy load), the same way as with Native stack. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2977) Native does not repsect the fault value in @Action

by Jim Ma (JIRA)

Native does not repsect the fault value in @Action -------------------------------------------------- Key: JBWS-2977 URL: https://jira.jboss.org/jira/browse/JBWS-2977 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.CR1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 WSA Action shold be set to "http://fault1" in soap fault message : @Action(input="finput1", output="foutput1", fault={ @FaultAction(className=AddNumbersException.class, value="http://fault1") }) public int addNumbersFault1(int number1, int number2) throws AddNumbersException { return doStuff(number1, number2); } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
3
0 / 0

[JBoss JIRA] Created: (JBWS-2969) CommonBindingProvider.getEndpointReference(Class clazz) :WebServiceExeption should be thrown when the clazz is not assignableFrom W3CEndpointReference

by Jim Ma (JIRA)

CommonBindingProvider.getEndpointReference(Class clazz) :WebServiceExeption should be thrown when the clazz is not assignableFrom W3CEndpointReference ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBWS-2969 URL: https://jira.jboss.org/jira/browse/JBWS-2969 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.3.0.Beta4 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-native-3.3.0 As per JAX-WS spec , WebServiceException should be thrown when the clazz is not assignableFrom W3CEndpointReference in CommonBindingProvider.getEndpointReference(Class clazz) method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-2985) TODO - better description

by Richard Opalka (JIRA)

TODO - better description ------------------------- Key: JBWS-2985 URL: https://jira.jboss.org/jira/browse/JBWS-2985 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.3.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBWS-2983) Fix regressions due to HornetQ update

by Richard Opalka (JIRA)

Fix regressions due to HornetQ update ------------------------------------- Key: JBWS-2983 URL: https://jira.jboss.org/jira/browse/JBWS-2983 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Alessio Soldano Fix For: jbossws-native-3.3.0 Failing tests against AS trunk: org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase.testPublishedContract org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase.testJMSEndpointPort org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase.testHTTPEndpointPort org.jboss.test.ws.jaxws.samples.jmstransport.JMSTransportTestCase.testMessagingClient -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2986) Factor out stack agnostic wsdl file publish procedure to jbossws-common

by Alessio Soldano (JIRA)

Factor out stack agnostic wsdl file publish procedure to jbossws-common ----------------------------------------------------------------------- Key: JBWS-2986 URL: https://jira.jboss.org/jira/browse/JBWS-2986 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-native Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-native-3.3.0, jbossws-cxf-3.3.0 Create an AbstractWSDLFilePublisher with the stack agnostic part of the procedure required for publishing a deployed wsdl (as per jsr-109 spec, section 8.2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-2718) Loading artifacts from WEB-INF/wsdl1 fails

by Alessio Soldano (JIRA)

Loading artifacts from WEB-INF/wsdl1 fails ------------------------------------------ Key: JBWS-2718 URL: https://jira.jboss.org/jira/browse/JBWS-2718 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 > how is your pojo endpoint annotated? @javax.jws.WebService( name = "WSRPV1MarkupPortType", serviceName = "WSRPV1Service", portName = "WSRPMarkupService", targetNamespace = "urn:oasis:names:tc:wsrp:v1:wsdl", wsdlLocation = "/WEB-INF/wsdl1/wsrp_services.wsdl", endpointInterface = "org.oasis.wsrp.v1.WSRPV1MarkupPortType" ) public class MarkupEndpoint extends WSRPBaseEndpoint implements WSRPV1MarkupPortType > And what exception you get exactly? 15:09:30,232 INFO [TomcatDeployer] deploy, ctxPath=/wsrp-producer, warUrl=.../tmp/deploy/tmp7635205325184845617wsrp-producer-exp.war/ 15:09:36,999 INFO [WSDLFilePublisher] WSDL published to: file:/Users/claprun/Dev/jboss-4.2.3.GA-jdk6/server/default/data/wsdl/wsrp-producer.war/wsrp_services.wsdl 15:09:37,013 ERROR [MainDeployer] Could not start deployment: file:/Users/claprun/Dev/jboss-4.2.3.GA-jdk6/server/default/deploy/wsrp-producer.war org.jboss.ws.WSException: Cannot publish wsdl to: /Users/claprun/Dev/jboss-4.2.3.GA-jdk6/server/default/data/wsdl/wsrp-producer.war/wsrp_services.wsdl at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:143) at org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect.create(PublishContractDeploymentAspect.java:52) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy45.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: java.io.IOException: Cannot get URL for: WEB-INF/wsdl/wsrp_v1_types.xsd at org.jboss.wsf.common.URLLoaderAdapter.findChild(URLLoaderAdapter.java:106) at org.jboss.wsf.framework.deployment.ArchiveDeploymentImpl.getMetaDataFileURL(ArchiveDeploymentImpl.java:99) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:242) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:262) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishSchemaImports(WSDLFilePublisher.java:262) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlImports(WSDLFilePublisher.java:192) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlImports(WSDLFilePublisher.java:188) at org.jboss.wsf.stack.jbws.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:126) ... 32 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
15
0 / 0

[JBoss JIRA] Created: (JBWS-2984) Benchmark tests are setting incorrect date

by Richard Opalka (JIRA)

Benchmark tests are setting incorrect date ------------------------------------------ Key: JBWS-2984 URL: https://jira.jboss.org/jira/browse/JBWS-2984 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: productization Reporter: Richard Opalka Assignee: Martin Vecera Fix For: jbossws-native-3.3.0, jbossws-metro-3.3.0, jbossws-cxf-3.3.0 I'm assigning this issue to you Martin because I can't see pmacik in "Assign to" pop up list. I found that benchmark tests QA team provided us are failing every last day in every month. The tests are trying to set up e.g. 32-nd of March as valid date. I can see this failure locally when running our test suite today (31-st of March): --- [INFO] Surefire report directory: /home/opalka/svn/jbossws/stack/native/trunk/modules/testsuite/framework-tests/target/surefire-reports org.apache.maven.surefire.booter.SurefireExecutionException: null; nested exception is java.lang.ExceptionInInitializerError: null java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.apache.maven.surefire.testset.PojoTestSet.<init>(PojoTestSet.java:55) at org.apache.maven.surefire.junit.JUnitDirectoryTestSuite.createTestSet(JUnitDirectoryTestSuite.java:64) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:96) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:209) at org.apache.maven.surefire.Surefire.run(Surefire.java:156) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:345) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:1009) Caused by: java.lang.IllegalArgumentException: Invalid value 32 for Day field. at org.apache.xerces.jaxp.datatype.XMLGregorianCalendarImpl.checkFieldValueConstraint(Unknown Source) at org.apache.xerces.jaxp.datatype.XMLGregorianCalendarImpl.setDay(Unknown Source) at org.jboss.test.ws.jaxws.benchmark.test.datatypes.unwrapped.pojo.CalendarRPCTest.<clinit>(CalendarRPCTest.java:60) ... 17 more [ERROR] There are test failures. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues March 2010