[jira] [Commented] (AXIS2-5918) Axis2 migration failure with SOAP with Attachment
[ https://issues.apache.org/jira/browse/AXIS2-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506343#comment-16506343 ] robert lazarski commented on AXIS2-5918: The axis2 version is not listed, and the stack trace does not line up with the last few releases. What version are you running? I suggest upgrading to 1.7.8 as the first next step. Best I can tell, RPCUtil.invokeServiceClass() is failing in its reflection attempt because the number of arguments is not what is expected, i.e. your param list has too many or too few arguments. If your problem is time sensitive I suggest compiling from source from the latest release, and adding some debug statements around the reflection area in RPCUtil.invokeServiceClass() . svn co http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.8/ > Axis2 migration failure with SOAP with Attachment > - > > Key: AXIS2-5918 > URL: https://issues.apache.org/jira/browse/AXIS2-5918 > Project: Axis2 > Issue Type: Bug >Reporter: Anoobkumar >Priority: Major > > I am migrating a project which accepts SOAP with Attachment as request from > Axis to Axis2 framework. Modules, services everything created and > build/deployment went fine. But when I try a request, I am getting below > error. in log. Any advise to share? > > 01 Jun 2018 11:21:01 ERROR : wrong number of arguments > java.lang.IllegalArgumentException: wrong number of arguments > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178) > at > org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) > at > org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) > at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) > at > weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) > at > weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) > at > weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3732) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) > at > weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273) > at > weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179) > at > weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5918) Axis2 migration failure with SOAP with Attachment
[ https://issues.apache.org/jira/browse/AXIS2-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506293#comment-16506293 ] Anoobkumar commented on AXIS2-5918: --- Any one have any comment here? > Axis2 migration failure with SOAP with Attachment > - > > Key: AXIS2-5918 > URL: https://issues.apache.org/jira/browse/AXIS2-5918 > Project: Axis2 > Issue Type: Bug >Reporter: Anoobkumar >Priority: Major > > I am migrating a project which accepts SOAP with Attachment as request from > Axis to Axis2 framework. Modules, services everything created and > build/deployment went fine. But when I try a request, I am getting below > error. in log. Any advise to share? > > 01 Jun 2018 11:21:01 ERROR : wrong number of arguments > java.lang.IllegalArgumentException: wrong number of arguments > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RPCUtil.java:178) > at > org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:117) > at > org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40) > at > org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:114) > at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:181) > at > org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172) > at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:146) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) > at > weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) > at > weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301) > at > weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:184) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3732) > at > weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696) > at > weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) > at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) > at > weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273) > at > weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179) > at > weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490) > at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256) > at weblogic.work.ExecuteThread.run(ExecuteThread.java:221) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5827) axis2-wsdl2code-maven-plugin shouldn't use Log4j
[
https://issues.apache.org/jira/browse/AXIS2-5827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506153#comment-16506153
]
Petr Dvorak commented on AXIS2-5827:
Is there any roadmap for 1.8.0 release? We are postponing our issue that
depends on this one for several releases...
> axis2-wsdl2code-maven-plugin shouldn't use Log4j
>
>
> Key: AXIS2-5827
> URL: https://issues.apache.org/jira/browse/AXIS2-5827
> Project: Axis2
> Issue Type: Bug
> Components: Tools
>Affects Versions: 1.7.4
>Reporter: Petr Dvorak
>Assignee: Andreas Veithen
>Priority: Minor
> Fix For: 1.8.0
>
>
> I am using axis2-wsdl2code-maven-plugin to generate my SOAP service client.
> The plugin itself works correctly and it generates a correct SOAP client, but
> I get following warning in console with every build:
> {code}
> log4j:WARN No appenders could be found for logger
> (org.apache.axiom.locator.DefaultOMMetaFactoryLocator).
> log4j:WARN Please initialize the log4j system properly.
> {code}
> I know I need to configure Log4j properties, but I haven't found any
> documentation / help on how to do this for {{axis2-wsdl2code-maven-plugin}}...
> This is my {{pom.xml}} file:
> {code:xml}
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> powerauth-java-client-axis
> 0.13.0
> powerauth-java-client-axis
> PowerAuth 2.0 Service Client - Axis
>
> io.getlime.security
> powerauth-parent
> 0.13.0
> ../pom.xml
>
>
>
> org.apache.axis2
> axis2
> 1.6.3
>
>
> org.apache.axis2
> axis2-adb
> 1.6.3
>
>
> org.apache.axis2
> axis2-transport-http
> 1.6.3
>
>
> org.apache.axis2
> axis2-transport-local
> 1.6.3
>
>
> org.apache.ws.commons.axiom
> axiom-api
> 1.2.20
>
>
> org.apache.ws.commons.axiom
> axiom-impl
> 1.2.20
>
>
> org.apache.ws.security
> wss4j
> 1.6.19
>
>
> wsdl4j
> wsdl4j
>
>
>
>
>
>
> org.apache.axis2
> axis2-wsdl2code-maven-plugin
> 1.6.4
>
>
>
> wsdl2code
>
>
>
> io.getlime.powerauth.soap
>
> ${basedir}/src/main/resources/soap/wsdl/service.wsdl
>
>
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-3919) Temp folder being filled with files. Running out of disk space.
[ https://issues.apache.org/jira/browse/AXIS2-3919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506026#comment-16506026 ] Alexis Krier commented on AXIS2-3919: - Same thing here, I 've had the same problem with axis 1.6.2, then I've updated to 1.7.8 and I do not see any temp folder or file created > Temp folder being filled with files. Running out of disk space. > --- > > Key: AXIS2-3919 > URL: https://issues.apache.org/jira/browse/AXIS2-3919 > Project: Axis2 > Issue Type: Bug > Components: kernel, modules >Affects Versions: 1.0, 1.1, 1.1.1, 1.2, 1.3, 1.4, 1.7.3 > Environment: Windows XP, Linux >Reporter: Sujay Chauhan >Priority: Major > > Hi > We are seeing an issue and it is holding us up from moving to production as > our production servers would run out of disk space. > This is in regards to a client that we are trying to implement using > axis2-1.4 and rampart-1.3. > We have a folder structure > clientProjectFolder > --otherFolders > -- > -- > --axis2 > --conf > --axis2.xml >--modules > --rampart1.3.mar > our axis2.xml file contains the global module > In our client code, we make use of the fileSytemConfigurator to configure the > client stub before making the call to our service. > Every time we are calling the service, files are added to the TEMP folder > (see below) > C:\TEMP\_axis2>dir > Directory of C:\TEMP\_axis2 > 07/16/2008 08:36 AM . > 07/16/2008 08:36 AM .. > 07/16/2008 08:36 AM 2,704 axis2473rampart-1.3.mar >1 File(s) 2,704 bytes >2 Dir(s) 103,722,340,352 bytes free > The same issue is being duplicated on our prod servers which are not windows > based but linux based. the files get put in /tmp/_axis2 folder. > Any advice on if there is a workaround for this? > Thanks, > Sujay -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5919) Java classes generated from WSDL with custom faults are missing parameters when calling toOM method (axis2-codegen with axis2-jaxbri)
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edi Obradovic updated AXIS2-5919:
-
Description:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axis2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions used:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
Classpath with all versions can be found in WSDL2Java call
*Note: *Migrating code from axis2 1.4 version
was:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axi2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
> Java classes generated from WSDL with custom faults are missing parameters
> when calling toOM method (axis2-codegen with axis2-jaxbri)
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.7
>Reporter: Edi Obradovic
>Priority: Blocker
> Attachments: HelloService.wsdl,
> HelloServiceMessageReceiverInOut.java, WSDL2Java call.txt
>
>
> We are currently unable to use newer version of axis2 because the Java
> classes generated by axis2-codegen and axis2-jaxbri have missing parameter
> errors.
> When you generate Java classes from WSDL that uses custom faults you get
> errors in the newly generated classes: "The method toOM(TestFaultStruct,
> boolean, QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> The error happens because:
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
> msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME," select="@localname"/>");
> org.apache.axis2.AxisFault f = createAxisFault(e);
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
> }
> throw f;
> }
>
[jira] [Updated] (AXIS2-5919) Java classes generated from WSDL with custom faults are missing parameters when calling toOM method (axis2-codegen with axis2-jaxbri)
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edi Obradovic updated AXIS2-5919:
-
Description:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axis2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
+The error happens because:+
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions used:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
Classpath with all versions can be found in [WSDL2Java
call|https://issues.apache.org/jira/secure/attachment/12927036/WSDL2Java%20call.txt]
*Note:* Migrating code from axis2 1.4 version
was:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axis2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions used:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
Classpath with all versions can be found in [WSDL2Java
call|https://issues.apache.org/jira/secure/attachment/12927036/WSDL2Java%20call.txt]
*Note: *Migrating code from axis2 1.4 version
> Java classes generated from WSDL with custom faults are missing parameters
> when calling toOM method (axis2-codegen with axis2-jaxbri)
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.7
>Reporter: Edi Obradovic
>Priority: Blocker
> Attachments: HelloService.wsdl,
> HelloServiceMessageReceiverInOut.java, WSDL2Java call.txt
>
>
> We are currently unable to use newer version of axis2 because the Java
> classes generated by axis2-codegen and axis2-jaxbri have missing parameter
> errors.
> When you generate Java classes from WSDL that uses custom faults you get
> errors in the newly generated classes: "The method toOM(TestFaultStruct,
> boolean, QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> +The error happens because:+
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
>
[jira] [Updated] (AXIS2-5919) Java classes generated from WSDL with custom faults are missing parameters when calling toOM method (axis2-codegen with axis2-jaxbri)
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edi Obradovic updated AXIS2-5919:
-
Description:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axis2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions used:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
Classpath with all versions can be found in [WSDL2Java
call|https://issues.apache.org/jira/secure/attachment/12927036/WSDL2Java%20call.txt]
*Note: *Migrating code from axis2 1.4 version
was:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axis2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions used:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
Classpath with all versions can be found in WSDL2Java call
*Note: *Migrating code from axis2 1.4 version
> Java classes generated from WSDL with custom faults are missing parameters
> when calling toOM method (axis2-codegen with axis2-jaxbri)
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.7
>Reporter: Edi Obradovic
>Priority: Blocker
> Attachments: HelloService.wsdl,
> HelloServiceMessageReceiverInOut.java, WSDL2Java call.txt
>
>
> We are currently unable to use newer version of axis2 because the Java
> classes generated by axis2-codegen and axis2-jaxbri have missing parameter
> errors.
> When you generate Java classes from WSDL that uses custom faults you get
> errors in the newly generated classes: "The method toOM(TestFaultStruct,
> boolean, QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> The error happens because:
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
> msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME," select="@localname"/>");
> org.apache.axis2.AxisFault
[jira] [Updated] (AXIS2-5919) Java classes generated from WSDL with custom faults are missing parameters when calling toOM method (axis2-codegen with axis2-jaxbri)
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edi Obradovic updated AXIS2-5919:
-
Description:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axi2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
was:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axi2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
> Java classes generated from WSDL with custom faults are missing parameters
> when calling toOM method (axis2-codegen with axis2-jaxbri)
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.7
>Reporter: Edi Obradovic
>Priority: Blocker
> Attachments: HelloService.wsdl,
> HelloServiceMessageReceiverInOut.java, WSDL2Java call.txt
>
>
> We are currently unable to use newer version of axis2 because the Java
> classes generated by axis2-codegen and axi2-jaxbri have missing parameter
> errors.
> When you generate Java classes from WSDL that uses custom faults you get
> errors in the newly generated classes: "The method toOM(TestFaultStruct,
> boolean, QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> The error happens because:
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
> msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME," select="@localname"/>");
> org.apache.axis2.AxisFault f = createAxisFault(e);
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
> }
> throw f;
> }
>
> {code}
> You can find the WSDL test file and generated class in the attachment.
> Java call for WSDL2Java is
[jira] [Updated] (AXIS2-5919) Java classes generated from WSDL with custom faults are missing parameters when calling toOM method (axis2-codegen with axis2-jaxbri)
[
https://issues.apache.org/jira/browse/AXIS2-5919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edi Obradovic updated AXIS2-5919:
-
Description:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen and axi2-jaxbri have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
(axis2-jaxbri) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Versions:
axis2-jaxbri: 1.7.7
axis2-codegen: 1.7.7
was:
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
Summary: Java classes generated from WSDL with custom faults are
missing parameters when calling toOM method (axis2-codegen with axis2-jaxbri)
(was: Java classes generated from WSDL with custom faults are missing
parameters when calling toOM method)
> Java classes generated from WSDL with custom faults are missing parameters
> when calling toOM method (axis2-codegen with axis2-jaxbri)
> -
>
> Key: AXIS2-5919
> URL: https://issues.apache.org/jira/browse/AXIS2-5919
> Project: Axis2
> Issue Type: Bug
> Components: codegen
>Affects Versions: 1.7.7
>Reporter: Edi Obradovic
>Priority: Blocker
> Attachments: HelloService.wsdl,
> HelloServiceMessageReceiverInOut.java, WSDL2Java call.txt
>
>
> We are currently unable to use newer version of axis2 because the Java
> classes generated by axis2-codegen and axi2-jaxbri have missing parameter
> errors.
> When you generate Java classes from WSDL that uses custom faults you get
> errors in the newly generated classes: "The method toOM(TestFaultStruct,
> boolean, QName) in the type is not applicable for the arguments
> (TestFaultStruct, boolean)". The reason you get that is because the QName
> parameter is missing when calling toOM in faults.
> The error happens because:
> - all toOM methods code is generated using JaxbRIDatabindingTemplate.xsl
> (axis2-jaxbri) and they all have QName parameter defined
> - all custom faults code is generated using MessageReceiverTemplate.xsl
> (axis2-codegen) and if you look at the xsl code you can see that QName
> parameter is not there:
> {code:xml}
>
> } catch ( select="@name"/> e) {
>
> msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME," select="@localname"/>");
> org.apache.axis2.AxisFault f = createAxisFault(e);
> if (e.getFaultMessage() != null){
> f.setDetail(toOM(e.getFaultMessage(),false));
>
[jira] [Created] (AXIS2-5919) Java classes generated from WSDL with custom faults are missing parameters when calling toOM method
Edi Obradovic created AXIS2-5919:
Summary: Java classes generated from WSDL with custom faults are
missing parameters when calling toOM method
Key: AXIS2-5919
URL: https://issues.apache.org/jira/browse/AXIS2-5919
Project: Axis2
Issue Type: Bug
Components: codegen
Affects Versions: 1.7.7
Reporter: Edi Obradovic
Attachments: HelloService.wsdl, HelloServiceMessageReceiverInOut.java,
WSDL2Java call.txt
We are currently unable to use newer version of axis2 because the Java classes
generated by axis2-codegen have missing parameter errors.
When you generate Java classes from WSDL that uses custom faults you get errors
in the newly generated classes: "The method toOM(TestFaultStruct, boolean,
QName) in the type is not applicable for the arguments
(TestFaultStruct, boolean)". The reason you get that is because the QName
parameter is missing when calling toOM in faults.
The error happens because:
- all toOM methods code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and they all have QName parameter defined
- all custom faults code is generated using MessageReceiverTemplate.xsl
(axis2-codegen) and if you look at the xsl code you can see that QName
parameter is not there:
{code:xml}
} catch ( e) {
msgContext.setProperty(org.apache.axis2.Constants.FAULT_NAME,"");
org.apache.axis2.AxisFault f = createAxisFault(e);
if (e.getFaultMessage() != null){
f.setDetail(toOM(e.getFaultMessage(),false));
}
throw f;
}
{code}
You can find the WSDL test file and generated class in the attachment.
Java call for WSDL2Java is also in the attachment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
