May 2011 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-3295) Change default folder for wsconsume generated sources

by Anders Hammar (JIRA)

Change default folder for wsconsume generated sources ----------------------------------------------------- Key: JBWS-3295 URL: https://issues.jboss.org/browse/JBWS-3295 Project: JBoss Web Services Issue Type: Enhancement Security Level: Public (Everyone can see) Components: jaxws-tools-maven-plugin Affects Versions: jbossws-jaxws-tools-maven-plugin-1.0.1.GA Environment: n/a Reporter: Anders Hammar Priority: Minor The Maven convention for generated sources is for those to be created under target/generated-sources/blabla. The AbstractWsConsumeMojo class specifies that sources be created under target/wsconsume/java (through the default-value of the sourceDirectory param). I suggest this is changed to "${project.build.directory}/generated-sources/wsconsume". (I don't see a need for adding a trailing "java".) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3255) Unable to lookup AuthenticationManager

by Richard Opalka (JIRA)

Unable to lookup AuthenticationManager -------------------------------------- Key: JBWS-3255 URL: https://issues.jboss.org/browse/JBWS-3255 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 12:18:01,235 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-nucleus%2F127.0.0.1-8080-2) SOAP request exception: org.jboss.ws.WSException: Unable to lookup AuthenticationManager at org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:86) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.WSSecurityDispatcher.authorize(WSSecurityDispatcher.java:150) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:101) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:90) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53) [jbossws-common.jar:2.0.0-SNAPSHOT] at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:328) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:146) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callRequestHandlerChain(HandlerDelegateJAXWS.java:98) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.server.ServiceEndpointInvoker.callRequestHandlerChain(ServiceEndpointInvoker.java:129) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:176) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:527) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:316) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:222) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:147) [jbossws-native-core.jar:4.0.0-SNAPSHOT] at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87) [jbossws-common.jar:2.0.0-SNAPSHOT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.0.Final.jar:1.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:154) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:660) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [jbossweb-7.0.0.Beta7.jar:7.0.0.Beta2-SNAPSHOT] at java.lang.Thread.run(Thread.java:636) [:1.6.0_20] Caused by: javax.naming.NameNotFoundException: Name 'env' not found in context '' at org.jboss.as.naming.util.NamingUtils.nameNotFoundException(NamingUtils.java:109) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.InMemoryNamingStore$NodeTraversingVisitor.visit(InMemoryNamingStore.java:355) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.InMemoryNamingStore$ContextNode.accept(InMemoryNamingStore.java:297) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.InMemoryNamingStore.lookup(InMemoryNamingStore.java:151) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:180) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:211) [jboss-as-naming-7.0.0.Beta2-SNAPSHOT.jar:7.0.0.Beta2-SNAPSHOT] at javax.naming.InitialContext.lookup(InitialContext.java:409) [:1.6.0_20] at org.jboss.ws.extensions.security.operation.AuthorizeOperation.<init>(AuthorizeOperation.java:80) [jbossws-native-core.jar:4.0.0-SNAPSHOT] ... 28 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

5
7
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

13 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBWS-3252) Investigate WSA interop tests regression

by Richard Opalka (JIRA)

Investigate WSA interop tests regression ---------------------------------------- Key: JBWS-3252 URL: https://issues.jboss.org/browse/JBWS-3252 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Fix For: jbossws-native-4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

2
1
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

13 years, 1 month

4
7
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

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBWS-3275) AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message

by Jim Ma (JIRA)

AddressingFeature required Client should throw exception when the wsa header is missing in the inbound message --------------------------------------------------------------------------------------------------------------- Key: JBWS-3275 URL: https://issues.jboss.org/browse/JBWS-3275 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jbossws-cxf Affects Versions: jbossws-cxf-3.4.1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-4.0 Related CXF issue: https://issues.apache.org/jira/browse/CXF-3458 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

3
2
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

13 years, 1 month

3
12
0 / 0

[JBoss JIRA] Created: (JBWS-3235) org.jboss.ws.core.soap.SOAPFaultImpl should be Serializable

by david.boeren (JIRA)

org.jboss.ws.core.soap.SOAPFaultImpl should be Serializable ----------------------------------------------------------- Key: JBWS-3235 URL: https://issues.jboss.org/browse/JBWS-3235 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.4.1 Reporter: david.boeren Priority: Trivial Fix For: jbossws-native-4.0 org.jboss.ws.core.soap.SOAPFaultImpl is currently not Serializable at runtime, which is counterintuitive since descendants of Throwable generally are, and all descendants of Throwable are marked as implementing the Serializable interface. There is a workaround to extract the message and place it in a different Exception class but this is an extra step that should not be necessary. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
1
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

13 years, 2 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues May 2011