December 2010 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3165) Add support for jax-ws xml catalog to be spec-compliant

by Robert Dale (JIRA)

Add support for jax-ws xml catalog to be spec-compliant ------------------------------------------------------- Key: JBWS-3165 URL: https://jira.jboss.org/browse/JBWS-3165 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Robert Dale <ropalka> rdale, OK, JAXWS 2.2 - section 4.4 <ropalka> --- <ropalka> The catalog is assembled by taking into account all accessible resources whose name is META-INF/jax- <ropalka> -ws-catalog.xml. Each resource MUST be a valid entity catalog according to the XML Catalogs 1.1 <ropalka> specification. When running on the Java SE platform, the current context class loader MUST be used to <ropalka> retrieve all the resources with the specified name. Relative URIs inside a catalog file are relative to the <ropalka> location of the catalog that contains them. <ropalka> --- <ropalka> rdale, AFAIK Native doesn't support it. It uses proprietary jbossws-entities.properties approach <ropalka> rdale, CXF should support it. <ropalka> rdale, Do U use JBossWS Native or JBossWS CXF? <darran> ropalka, CXF does, we are using it in SOA-P 5.1 <ropalka> rdale, I confirm JBossWS Native doesn't support it (although this is required by JAX-WS spec). The reason is this is not tested in TCK6 (certification suites) and we didn't have feature request to implement it yet. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBWS-3176) JbossWS native client handler issue

by Gary Brown (JIRA)

JbossWS native client handler issue ----------------------------------- Key: JBWS-3176 URL: https://jira.jboss.org/browse/JBWS-3176 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.2.2 Environment: RiftSaw 2.2.0.CR1, JBossAS 5.1.0.GA, JBossWS 3.2.2.GA (installed as part of the RiftSaw installation), JBossESB 4.9, JDK6, Savara 1.1.0.CR1 Reporter: Gary Brown I have a BPEL process that invokes two JAX-WS services, one after the other. The first invocation does not trigger the client handler configured in the 'standard-jaxws-client-config.xml' file, however the second invocation does. In terms of the environment, when you have a clean JBossAS environment, install the ESB, install Riftsaw using "ant deploy -Ddatabase=hsql -Dws.version=3.2.2.GA" (which will install jbossws native 3.2.2.GA). For now don't worry about installing Savara, as it is only configuring the client handler. May be easier for you to use your own handler, rather than installing yet another project - although if you have problems reproducing the issue, then may need to install Savara in case that is the problem. Attached are the various artifacts that need to be deployed into the server's deploy folder. The policy-quote-queue-service.xml will need to be deployed first. SoapUI can be used to send the following messages. The instructions for running the example are: 1) Send <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pol="http://www.example.org/policyQuote"> <soapenv:Header/> <soapenv:Body> <pol:policyQuote> <pol:receivePolicyQuote> <pol:requestDate>2009-01-01</pol:requestDate> <pol:task>receivePolicyQuote</pol:task> <pol:policyQuoteInfo> <pol:policyType>AUTO</pol:policyType> <pol:vehicleYear>2004</pol:vehicleYear> <pol:driverName>Bill Smith</pol:driverName> <pol:ssn>412345678</pol:ssn> <pol:dlNumber>987654321</pol:dlNumber> <pol:age>30</pol:age> <pol:numberOfAccidents>0</pol:numberOfAccidents> <pol:numberOfTickets>0</pol:numberOfTickets> <pol:creditScore>0</pol:creditScore> <pol:price>0</pol:price> </pol:policyQuoteInfo> </pol:receivePolicyQuote> </pol:policyQuote> </soapenv:Body> </soapenv:Envelope> to this URL http://localhost:8080/PolicyQuoteProcessServiceService/PolicyQuoteProcess... 2) Then wait until you see the following on the console: Received Driving Record Request for: Bill Smith 3) Then send: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:drv="http://dmv.com/drivingRecord"> <soapenv:Header/> <soapenv:Body> <drv:drivingRecordResponse> <drv:name>Bill Smith</drv:name> <drv:ssn>412345678</drv:ssn> <drv:dlNumber>987654321</drv:dlNumber> <drv:age>30</drv:age> <drv:numberOfTickets>2</drv:numberOfTickets> <drv:numberOfAccidents>1</drv:numberOfAccidents> </drv:drivingRecordResponse> </soapenv:Body> </soapenv:Envelope> to http://localhost:8080/PolicyQuoteProcessServiceService/DrivingRecordCallb... (The example has been provided by Jeff DeLong). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-3150) Investigate org.jboss.test.ws.common.soap.SOAPConnectionTestCase causing Hudson to freeze

by Alessio Soldano (JIRA)

Investigate org.jboss.test.ws.common.soap.SOAPConnectionTestCase causing Hudson to freeze ----------------------------------------------------------------------------------------- Key: JBWS-3150 URL: https://jira.jboss.org/browse/JBWS-3150 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Alessio Soldano Fix For: jbossws-native-3.4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-2157) Child nodes truncated when using jaxb to marshall data into a SOAP header

by Andrew Dinn (JIRA)

Child nodes truncated when using jaxb to marshall data into a SOAP header -------------------------------------------------------------------------- Key: JBWS-2157 URL: http://jira.jboss.com/jira/browse/JBWS-2157 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.1 Reporter: Andrew Dinn I wish to serialise a CoordinationContext type (a complex type defined in the OASIS WS-COOR 1.1 spec) into a SOAP message header as follows: <code> final JAXBContext jaxbCtx = getJaxbContext(); final SOAPMessage soapMessage = context.getMessage(); final SOAPEnvelope soapEnvelope = soapMessage.getSOAPPart().getEnvelope(); SOAPHeader soapHeader = soapEnvelope.getHeader() ; if (soapHeader == null) { soapHeader = soapEnvelope.addHeader() ; } Marshaller marshaller = jaxbCtx.createMarshaller(); marshaller.marshal(coordinationContext, soapHeader); </code> The problem is that the header gets inserted without any children. What happens is that the marshaller creates a SOAP tree top down consisting of SOAPElementImpl instances. It inserts these nodes into the tree below the SOAPHeader as it creates them. So, when the first node is created a call to SOAPHeader.addchild() is made. This call deteccts that the supplied node is of the wrong type so it substitutes a SOAPHeaderElementImpl. It attempts to copy the supplied node's substructure but the marshaller has not created the children at this point. -- 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

12 years, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBWS-2338) Review our SPI abstractsions and interfaces

by Richard Opalka (JIRA)

Review our SPI abstractsions and interfaces ------------------------------------------- Key: JBWS-2338 URL: https://jira.jboss.org/jira/browse/JBWS-2338 Project: JBoss Web Services Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jbossws-cxf, jbossws-metro, jbossws-native Affects Versions: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-cxf-3.0.4 Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5, jbossws-cxf-3.0.5 Terminology: DA = Deployment Aspect Issues: * WSFRuntime isn't good abstraction and should be removed from our SPI because it doesn't integrate with JBossAS deployers architecture very well (it's issue is it depends on web container runtime which can be unavailable at AS start time (e.g. there can be multiple webservice archives in deploy directory that are started before web container is available) * We moved some servlet dependent DAs to servlet lifecycle init()/destroy() methods. The problem of it is it executes DAs for whole deployment, not just particular deployed endpoint. (IOW we execute the same DAs multiple times if there are more than one webservice endpoints in deployment. This need SPI review and repair) -- 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

12 years, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (JBWS-3120) Virtual host feature have been removed in AS 6 series

by Richard Opalka (JIRA)

Virtual host feature have been removed in AS 6 series ----------------------------------------------------- Key: JBWS-3120 URL: https://jira.jboss.org/browse/JBWS-3120 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-native-4.0, jbossws-metro-4.0, jbossws-cxf-4.0 We should remove the test from our test suite and update our SPI accordingly to remove this feature for AS 6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2570) @SchemaValidation annotation does not work if schemaLocation property is not specified

by Nick Gudushauri (JIRA)

@SchemaValidation annotation does not work if schemaLocation property is not specified -------------------------------------------------------------------------------------- Key: JBWS-2570 URL: https://jira.jboss.org/jira/browse/JBWS-2570 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Environment: jboss 4.2.3.GA jbossws-native-3.0.5.GA Reporter: Nick Gudushauri Steps to reproduce: 1. Create simpe JAX-WS service 2. Annotate it with @SchemaValidation annotation WITHOUT specifying optional schemaLocation property (In such case schema should be extracted from the WSDL) 3. Send test request As the result no schema validation is performed and you will see the following messages in log: 17:07:13,421 INFO [SOAPBodyElementDoc] Validating: DOM_VALID 17:07:13,421 WARN [SchemaExtractor] Cannot find element: {http://schemas.xmlsoap.org/wsdl/}types 17:07:13,625 INFO [UCCServicesBean] Invoking UCC registerClearingOrder service by cer 17:07:14,515 INFO [SOAPBodyElementDoc] Validating: DOM_VALID 17:07:14,515 WARN [SchemaExtractor] Cannot find element: {http://schemas.xmlsoap.org/wsdl/}types The problem root is that org.jboss.ws.extensions.validation.SchemaExtractor class could not load 'types' element from WSDL as this element does not present in WSDL directly but imported via 'import' element. -- 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

12 years, 6 months

6
9
0 / 0

[JBoss JIRA] Created: (JBWS-3125) SOAP over JMS 1.0 support

by Alessio Soldano (JIRA)

SOAP over JMS 1.0 support ------------------------- Key: JBWS-3125 URL: https://jira.jboss.org/browse/JBWS-3125 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-3.4.1 Apache CXF 2.3 is coming with SOAP over JMS 1.0 support. We need to verify integration. See: http://cxf.apache.org/docs/soap-over-jms-10-support.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBWS-2709) Review JBossWS public api and provide online javadoc

by Alessio Soldano (JIRA)

Review JBossWS public api and provide online javadoc ---------------------------------------------------- Key: JBWS-2709 URL: https://jira.jboss.org/jira/browse/JBWS-2709 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: productization Reporter: Alessio Soldano Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1 We should make the javadoc available online for api/spi meant to be public. -- 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

12 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBWS-3105) Review and fix AS IL maven dependencies

by Richard Opalka (JIRA)

Review and fix AS IL maven dependencies --------------------------------------- Key: JBWS-3105 URL: https://jira.jboss.org/browse/JBWS-3105 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-integration Reporter: Richard Opalka Assignee: Richard Opalka Fix For: jbossws-cxf-3.4.1, jbossws-native-3.4.1, jbossws-metro-3.4.1 I found some weirdness related to VirtualFile in AS IL. This blocked me to clean AS IL maven dependencies. We need to review AS IL dependencies and make them explicit i.e. to know which libraries we're exactly depending on. The result of this process should be VirtualFile weirdness fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues December 2010