January 2007 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Updated: (JBWS-652) Add JAAS certificate authentication support to ws-security implementation

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-652?page=all ] Thomas Diesler updated JBWS-652: -------------------------------- Fix Version/s: (was: jbossws-1.0.5) > Add JAAS certificate authentication support to ws-security implementation > ------------------------------------------------------------------------- > > Key: JBWS-652 > URL: http://jira.jboss.com/jira/browse/JBWS-652 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ws-security > Reporter: Jason T. Greene > Assigned To: Jason T. Greene > Fix For: jbossws-1.2.0 > > > Currently X.509 tokens are validated against a truststore that is local to the ws-security deployment. We should offer support for delegating to JAAS/JBossSX so that JEE declarative security can reference known certificates. There is one problem with adding support for this, which is that a WS-Security message may contain many X.509 tokens (perhaps one for signature, and one for encryption), so we would have to somehow decide to pick one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-434) Support sequences of anys

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-434?page=all ] Thomas Diesler updated JBWS-434: -------------------------------- Fix Version/s: (was: jbossws-1.0.5) > Support sequences of anys > ------------------------- > > Key: JBWS-434 > URL: http://jira.jboss.com/jira/browse/JBWS-434 > Project: JBoss Web Services > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Alexey Loubyansky > Priority: Critical > Fix For: jbossws-1.2.0 > > > Francisco wrote: > Are there plans for supporting sequences of anys? One of my grad students is working on WS transactions, which use things like > <xsd:sequence> > <xsd:any namespace="##other" processContents="lax" > minOccurs="0" maxOccurs="unbounded"/> > </xsd:sequence> > His work should help us to get JBWS-36 done. I expect him to implement at least WS-Coordination and WS-AtomicTransaction, which should be (mostly) WS layers over the existing DTM code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1406) WS-Eventing: event notification failure

by Alessio Soldano (JIRA)

WS-Eventing: event notification failure --------------------------------------- Key: JBWS-1406 URL: http://jira.jboss.com/jira/browse/JBWS-1406 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ws-eventing Affects Versions: jbossws-1.0.4 Environment: JBoss 4.0.4.GA, JBossWS 1.0.4.GA Reporter: Alessio Soldano Attachments: dsvn.txt We noticed that event notification failures are completely lost. If an event notification fail (for example because the event sink is down) the current jbossws engine just logs the error and does nothing else. Of course it could be useful at least to keep track of failed notification in order to analyze the problem, send them again later or simply to warn the sink's owner. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-1399) JBWS-1178 implementation trouble

by Stefano Maestri (JIRA)

JBWS-1178 implementation trouble -------------------------------- Key: JBWS-1399 URL: http://jira.jboss.com/jira/browse/JBWS-1399 Project: JBoss Web Services Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: Stefano Maestri I got jbossws-1.0.4 and I installed it in my environment (for the description of the environment refer to my original blog post about multiple virtual host: http://www.javalinux.it/blogs/index.php?title=multiple_virtual_host_and_s... ). There are some problems * If I follow instruction in jboss-beans.xml leaving webservicehost as a null string I get this Exception during deploy of jbossws: Code: 09:11:02,349 ERROR [AbstractKernelController] Error installing to Configured: name=ServiceEndpointMa nager state=Instantiated mode=Manual requiredState=Create java.lang.IllegalArgumentException: Null value metadata at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java :487) at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java :434) at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoints(Configurator.jav a:398) at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getPropertySetterJoinPoints(Ab [...] *** DEPLOYMENTS IN ERROR: ServiceEndpointManager -> java.lang.IllegalArgumentException: Null value metadata If I comment the webServiceHost tag the deploy works correctly. I think here the explaination in the commented part of jboss-beans.xml have to be changed . * The current implementation only replaces the host name, but not the port used to call the webservice. I think the port replacing is also very important in an environment of complete virtual hosting like our one. Using Linux Virtual Server is normal to virtualize ports. For example we use ports > 1024 on real servers and standard 80/443 ports on virtual servers * You didn't apply the patch on showServiceEndpointTable method in ServiceEndPointManager. This method is called from context servlets and IMHO have to replace host and ports accordingly to wsdl's replacing. Otherwise you get an horrible list of wsdl pointing to "http://jbossws.undefined.host/..." and of course links do not work -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-1409) WsdlGenerator crashes on void-methods

by Thomas Diesler (JIRA)

WsdlGenerator crashes on void-methods ------------------------------------- Key: JBWS-1409 URL: http://jira.jboss.com/jira/browse/JBWS-1409 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: jbossws-1.0.4 Reporter: Thomas Diesler The automatic generation of a wsdl to deploy time crashes, if there is a method which returns void. Changing the return parameter to everything else besides void (i.e. String, boolean, ..) fixes the problem. Using JBoss 4.04 with JBossWS 1.0.4 + jboss-xml-binding.jar 1.0.0.CR7. Seems this bug http://jira.jboss.org/jira/browse/JBWS-647 is back in 1.0.4 again. Quote: 2006-11-22 16:16:35,181 ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/D:/jzx/zxdev_jboss/server/default/tmp/deploy/tmp19079zxapp_webservices.ear-contents/zxapp_webservices_logic.jar java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:559) at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:146) at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:249) at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:170) at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:321) at org.jboss.ws.deployment.AnnotationsMetaDataBuilder.processOrGenerateWSDL(AnnotationsMetaDataBuilder.java:93) at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:177) at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75) at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:106) at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:80) at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-1426) Release jbossws-1.2.0.CR1

by Thomas Diesler (JIRA)

Release jbossws-1.2.0.CR1 ------------------------- Key: JBWS-1426 URL: http://jira.jboss.com/jira/browse/JBWS-1426 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Thomas Diesler Fix For: jbossws-1.2.0 The release criteria for jbossws-1.1.0.GA are: * pass all internal jbossws tests * pass all portable j2ee-1.4 tests from the jboss testsuite * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite * generate all test artifacts with wstools -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBWS-1273) Release jbossws-1.2.0.GA binary

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-1273?page=all ] Thomas Diesler updated JBWS-1273: --------------------------------- Fix Version/s: (was: jbossws-1.0.5) > Release jbossws-1.2.0.GA binary > ------------------------------- > > Key: JBWS-1273 > URL: http://jira.jboss.com/jira/browse/JBWS-1273 > Project: JBoss Web Services > Issue Type: Task > Security Level: Public(Everyone can see) > Components: jaxrpc > Reporter: Thomas Diesler > Assigned To: Thomas Diesler > Fix For: jbossws-1.2.0 > > > The release criteria for jbossws-1.1.0.GA are: > * pass all internal jbossws tests > * pass all portable j2ee-1.4 tests from the jboss testsuite > * pass all tests in module jaxr,jaxrpc,saaj,webservice from the Sun compatiblity testsuite > * generate all test artifacts with wstools -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBWS-800) ClassCastException when trying to marshal a SybaseTimestamp

by Thomas Diesler (JIRA)

[ http://jira.jboss.com/jira/browse/JBWS-800?page=all ] Thomas Diesler updated JBWS-800: -------------------------------- Fix Version/s: (was: jbossws-1.0.5) > ClassCastException when trying to marshal a SybaseTimestamp > ----------------------------------------------------------- > > Key: JBWS-800 > URL: http://jira.jboss.com/jira/browse/JBWS-800 > Project: JBoss Web Services > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jaxrpc > Affects Versions: jbossws-1.0.0.CR4 > Environment: Windows XP, JBoss 4.0.4.CR2 > Reporter: Chris Baxter > Assigned To: Thomas Diesler > Fix For: jbossws-1.2.0 > > > I have a EJB3 persistent bean mapped to a Sybase DB table. This table has datetime column that I have mapped back to a java.util.Date property on the persistent bean. This same bean class is returned from a webservice call. On JBoss 4.0.3SP1 (using Axis), I had no issues returning this object from my finder call. Now, when I switch to JBoss 4.0.4CR2 (using JBossWS), I get the following exception: > Caused by: java.lang.ClassCastException: com.sybase.jdbc3.tds.SybTimestamp > at org.jboss.xb.binding.SimpleTypeBindings.marshal(SimpleTypeBindings.java:1150) > at org.jboss.xb.binding.XercesXsMarshaller.marshalCharacters(XercesXsMarshaller.java:1169) > at org.jboss.xb.binding.XercesXsMarshaller.marshalSimpleType(XercesXsMarshaller.java:451) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementType(XercesXsMarshaller.java:405) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElement(XercesXsMarshaller.java:380) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementOccurence(XercesXsMarshaller.java:886) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:823) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroupSequence(XercesXsMarshaller.java:1102) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroup(XercesXsMarshaller.java:1057) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:729) > at org.jboss.xb.binding.XercesXsMarshaller.marshalComplexType(XercesXsMarshaller.java:685) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementType(XercesXsMarshaller.java:414) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElement(XercesXsMarshaller.java:380) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementOccurence(XercesXsMarshaller.java:886) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:810) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroupSequence(XercesXsMarshaller.java:1102) > at org.jboss.xb.binding.XercesXsMarshaller.marshalModelGroup(XercesXsMarshaller.java:1057) > at org.jboss.xb.binding.XercesXsMarshaller.marshalParticle(XercesXsMarshaller.java:729) > at org.jboss.xb.binding.XercesXsMarshaller.marshalComplexType(XercesXsMarshaller.java:685) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementType(XercesXsMarshaller.java:414) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElement(XercesXsMarshaller.java:380) > at org.jboss.xb.binding.XercesXsMarshaller.marshalElementOccurence(XercesXsMarshaller.java:886) > at org.jboss.xb.binding.XercesXsMarshaller.marshallInternal(XercesXsMarshaller.java:275) > at org.jboss.xb.binding.XercesXsMarshaller.marshal(XercesXsMarshaller.java:222) > at org.jboss.ws.jaxb.JAXBMarshallerImpl.marshal(JAXBMarshallerImpl.java:172) > at org.jboss.ws.jaxrpc.encoding.JAXBSerializer.serialize(JAXBSerializer.java:100) > at org.jboss.ws.soap.SOAPContentElement.getXMLFragment(SOAPContentElement.java:172) > at org.jboss.ws.soap.SOAPContentElement.expandToDOM(SOAPContentElement.java:844) > at org.jboss.ws.soap.SOAPContentElement.getChildNodes(SOAPContentElement.java:761) > at org.jboss.util.xml.DOMWriter.printInternal(DOMWriter.java:201) > at org.jboss.util.xml.DOMWriter.printInternal(DOMWriter.java:260) > at org.jboss.util.xml.DOMWriter.printInternal(DOMWriter.java:260) > at org.jboss.util.xml.DOMWriter.print(DOMWriter.java:177) > at org.jboss.util.xml.DOMWriter.printNode(DOMWriter.java:126) > at org.jboss.ws.server.ServiceEndpoint.postProcessResponse(ServiceEndpoint.java:306) > ... 23 more > In looking at the source code, I think I see why there may be a problem: > else if(typeCode == XS_DATETIME) > { > Calendar c; > if(value.getClass() == java.util.Date.class) > { > c = Calendar.getInstance(); > c.clear(); > c.setTime((java.util.Date)value); > } > else > { > c = (Calendar)value; > } > result = marshalDateTime(c); > } > The SybaseTimestamp class extends java.sql.Timestamp which in turn extends java.util.Date. That first 'if' should hit, but it won't because SybaseTimestamp.class != java.util.Date.class. Instead, I think the if statement should be: > if(java.util.Date.class.isAssignableFrom(value.getClass())) > I made this change and recompiled and everything works as expected now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBWS-1428) Java to WSDL - Arrays within value type are skipped when generating the WSDL

by Darran Lofthouse (JIRA)

Java to WSDL - Arrays within value type are skipped when generating the WSDL ---------------------------------------------------------------------------- Key: JBWS-1428 URL: http://jira.jboss.com/jira/browse/JBWS-1428 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: wstools Affects Versions: jbossws-1.0.4 Reporter: Darran Lofthouse Assigned To: Darran Lofthouse Fix For: jbossws-1.2.0 Java to WSDL - Arrays within value type are skipped when generating the WSDL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWS-1333) Fix marshalling of null values in base64Binary, hexBinary

by Thomas Diesler (JIRA)

Fix marshalling of null values in base64Binary, hexBinary --------------------------------------------------------- Key: JBWS-1333 URL: http://jira.jboss.com/jira/browse/JBWS-1333 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxrpc Reporter: Thomas Diesler Assigned To: Heiko Braun Priority: Blocker Fix For: jbossws-1.0.4 19:53:55,783 ERROR [SOAPFaultExceptionHelper] SOAP request exception java.lang.IllegalArgumentException: multipart/related stream invalid, no root part was found at org.jboss.ws.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:153) at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:185) at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:145) /home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test [tdiesler@tddell test]$ ant -Dtest=jaxrpc/marshall test tests-main: [junit] Running org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase [junit] Tests run: 63, Failures: 0, Errors: 0, Time elapsed: 14.64 sec [junit] Running org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitDIITestCase [junit] Tests run: 63, Failures: 0, Errors: 2, Time elapsed: 6.636 sec [junit] Test org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitDIITestCase FAILED [junit] Running org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitTestCase [junit] Tests run: 63, Failures: 0, Errors: 1, Time elapsed: 11.84 sec [junit] Test org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitTestCase FAILED -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 3 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2007