[jira] Created: (AXIS2-4564) Axis2 WSDL2Java Innvocation Target Exception
Axis2 WSDL2Java Innvocation Target Exception Key: AXIS2-4564 URL: https://issues.apache.org/jira/browse/AXIS2-4564 Project: Axis 2.0 (Axis2) Issue Type: Bug Reporter: Srinivas I can create Stubs for a WSDL using Axis 1.4 using Command Prompt.But If I try same thing with Axis2 1.4 I am getting InvocationTargetException.Followed all steps that have mentioned in solved https://issues.apache.org/jira/browse/AXIS2-3792.But Not Works -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (AXIS2-4562) JAX-WS: JAXBContext construction in JAX-WS should avoid SessionBean
[ https://issues.apache.org/jira/browse/AXIS2-4562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle reopened AXIS2-4562: --- JAX-WS: JAXBContext construction in JAX-WS should avoid SessionBean --- Key: AXIS2-4562 URL: https://issues.apache.org/jira/browse/AXIS2-4562 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assignee: Rich Scheuerle Original Estimate: 24h Remaining Estimate: 24h Background: The JAX-WS runtime inspects the JAX-WS artifacts to determine which packages or classes should be part of the JAXBContext. In most cases, the JAXBContext is constructed with a series of packages (which is relatively fast). However if a package does not contain JAXB ObjectFactory or package.info, then the JAXBUtils code must inspect individual classes in the package to see if they are actually JAXB tolerable. Problem: When the code falls down this secondary lookup path, it should avoid classes that implement javax.ejb.SessionBean. Such classes are not JAXB classes and inspecting those classes can result in degraded performance. Solution: I have a design to inspect classes to see if they should be skipped over. For example classes that implement SessionBean should be skipped. This new code avoids loading the SessionBean objects (which may not be present). I am testing the solution, and I am designing a unit test to verify the code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (AXIS2-4565) JAX-WS: Fails to examine the @RequestWrapper targetNamespace. Also needs to tolerate wsimport NS-PKG mapping algorithm
JAX-WS: Fails to examine the @RequestWrapper targetNamespace. Also needs to tolerate wsimport NS-PKG mapping algorithm - Key: AXIS2-4565 URL: https://issues.apache.org/jira/browse/AXIS2-4565 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assignee: Rich Scheuerle Background: The JAX-WS runtime examines the web service annotations and packages to determine which packages should be included in the JAXBContext. The JAX-WS runtime uses the namespace-package algorithm defined by the JAXB Specification when it needs to convert namespace references into packages. --- Problem 1: The JAX-WS runtime is not examining the targentnamespace parameter on the @RequestWrapper and @ResponseWrapper annotations. Thus it might neglect to include a package in the JAXBContext. (Note that this is rare. The JAX-WS runtime looks at the package referenced in the className parameter. Thus problems only occur if the wrapper element and the wrapper complexType are defined in two separate schemas...which is rare) Problem 2: Many applications are built using the wsimport tool. This tool apparently has a slightly different namespace-package mapping algorithm. For example, the JAXB specification (rule 8b) indicates if a namespace word collides with a java keyword, then a _ is appended . JAXB Rule: urn://my.interface.com becomes com.interface_.my. The wsimport tool prepends the underscore. WSIMPORT Rule: urn://my.interface.com becomes com._interface.my. -- Proposed Solution: For 1) The engine will be changed to examine the @RequestWrapper and @ResponseWrapper targetnamespace parameters. For 2) The engine will be changed to tolerate both rules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AXIS2-4565) JAX-WS: Fails to examine the @RequestWrapper targetNamespace. Also needs to tolerate wsimport NS-PKG mapping algorithm
[ https://issues.apache.org/jira/browse/AXIS2-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rich Scheuerle resolved AXIS2-4565. --- Resolution: Fixed JAX-WS: Fails to examine the @RequestWrapper targetNamespace. Also needs to tolerate wsimport NS-PKG mapping algorithm - Key: AXIS2-4565 URL: https://issues.apache.org/jira/browse/AXIS2-4565 Project: Axis 2.0 (Axis2) Issue Type: Bug Components: jaxws Reporter: Rich Scheuerle Assignee: Rich Scheuerle Original Estimate: 24h Remaining Estimate: 24h Background: The JAX-WS runtime examines the web service annotations and packages to determine which packages should be included in the JAXBContext. The JAX-WS runtime uses the namespace-package algorithm defined by the JAXB Specification when it needs to convert namespace references into packages. --- Problem 1: The JAX-WS runtime is not examining the targentnamespace parameter on the @RequestWrapper and @ResponseWrapper annotations. Thus it might neglect to include a package in the JAXBContext. (Note that this is rare. The JAX-WS runtime looks at the package referenced in the className parameter. Thus problems only occur if the wrapper element and the wrapper complexType are defined in two separate schemas...which is rare) Problem 2: Many applications are built using the wsimport tool. This tool apparently has a slightly different namespace-package mapping algorithm. For example, the JAXB specification (rule 8b) indicates if a namespace word collides with a java keyword, then a _ is appended . JAXB Rule: urn://my.interface.com becomes com.interface_.my. The wsimport tool prepends the underscore. WSIMPORT Rule: urn://my.interface.com becomes com._interface.my. -- Proposed Solution: For 1) The engine will be changed to examine the @RequestWrapper and @ResponseWrapper targetnamespace parameters. For 2) The engine will be changed to tolerate both rules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Notification Operation and Axis2 support
Hi all, I am using Axis 1.5 to create a client to Microsoft .net web services ,it has a notification operation. Here is the simple WSDL I am using to try to codegen. wsdl:definitions xmlns:axis2=http://quickstart.samples/; xmlns:soap12= http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:http= http://schemas.xmlsoap.org/wsdl/http/; xmlns:mime= http://schemas.xmlsoap.org/wsdl/mime/; xmlns:ns= http://quickstart.samples/xsd; xmlns:soap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; targetNamespace= http://quickstart.samples/; wsdl:types xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema; attributeFormDefault=qualified elementFormDefault=qualified targetNamespace=http://quickstart.samples/xsd; xs:element name=notify xs:complexType xs:sequence xs:element name=title nillable=true type=xs:string / xs:element name=message nillable=true type=xs:string / /xs:sequence /xs:complexType /xs:element /xs:schema /wsdl:types wsdl:message name=notifyMessage wsdl:part name=part1 element=ns:notify / /wsdl:message wsdl:portType name=StockQuoteServicePortType wsdl:operation name=notify wsdl:output message=notifyMessage / /wsdl:operation /wsdl:portType wsdl:binding name=StockQuoteServiceSOAP11Binding type=StockQuoteServicePortType soap:binding transport=http://schemas.xmlsoap.org/soap/http; style=document / wsdl:operation name=notify soap:operation soapAction=urn:notify style=document / wsdl:output soap:body use=literal namespace= http://quickstart.samples/; / /wsdl:output /wsdl:operation /wsdl:binding wsdl:binding name=StockQuoteServiceSOAP12Binding type=StockQuoteServicePortType soap12:binding transport=http://schemas.xmlsoap.org/soap/http; style=document / wsdl:operation name=notify soap12:operation soapAction=urn:notify style=document / wsdl:output soap12:body use=literal namespace= http://quickstart.samples/; / /wsdl:output /wsdl:operation /wsdl:binding wsdl:service name=StockQuoteService wsdl:port name=StockQuoteServiceSOAP11port binding=StockQuoteServiceSOAP11Binding soap:address location= http://localhost:8080/axis2/services/StockQuoteService; / /wsdl:port /wsdl:service /wsdl:definitions I'm going to genarate client side code using WSDL2java command, but i got this kind of error [ERROR] java.lang.NullPointerException at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOperations(WSDL11ToAxisServiceBuilder.java:1340) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortType(WSDL11ToAxisServiceBuilder.java:591) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:468) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:362) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Exception in thread main org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:153) at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24) Caused by: org.apache.axis2.AxisFault at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:396) at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:107) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:147) ... 2 more Caused by: java.lang.NullPointerException at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateOperations(WSDL11ToAxisServiceBuilder.java:1340) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populatePortType(WSDL11ToAxisServiceBuilder.java:591) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:468) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:362) ... 4 more Please help us in resolving this issue. thanks. shivantha.
Is Usernametoken username and keystore alias should be equal?
Hi Friends, I am implement axis2 security by using rampart and i using UsernameToken and Signature as a securities, what i need is the user name in usernameToken and alias name in Signature as different , but i am unable to configure like this. kindly help me to provide different names for usernametoken and signature. My axis2.xml configuration is as follows: parameter name=OutflowSecurity action itemsUsernameToken Signature/items userclientToken/user signaturePropFileclient.properties/signaturePropFile passwordCallbackClasscom.test.PWCBHandler/passwordCallbackClass signatureKeyIdentifierDirectReference/signatureKeyIdentifier /action /parameter signature properties file is: org.apache.ws.security.crypto.provider=org.apache.ws.security.components.crypto.Merlin org.apache.ws.security.crypto.merlin.keystore.type=jks org.apache.ws.security.crypto.merlin.keystore.alias=clientsecurity org.apache.ws.security.crypto.merlin.keystore.password=password org.apache.ws.security.crypto.merlin.file=kiwiclient.jks and also provide me the flow of PasswordCallHandler if possible. Thanks Regards Siva kumar -- View this message in context: http://old.nabble.com/Is-Usernametoken-username-and-keystore-alias-should-be-equal--tp26525254p26525254.html Sent from the Axis - Dev mailing list archive at Nabble.com.
