Re: [VOTE] Release Axis2 1.7.4
+1 Thanks, Shameera. On Sat, Oct 22, 2016 at 2:05 AM Sagara Gunathunga < sagara.gunathu...@gmail.com> wrote: > > +1 > > Thanks ! > > On Sat, Oct 22, 2016 at 4:19 AM, Andreas Veithen < > andreas.veit...@gmail.com> wrote: > > This is a vote to release Apache Axis2 1.7.4. > > SVN tag: http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.4/ > Maven artifacts: > https://repository.apache.org/content/repositories/orgapacheaxis2-1010/ > Distributions: > https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/1.7.4/ > Site: http://axis.apache.org/axis2/java/core-staging/ > > Here is my +1. > > Andreas > > - > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > > > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/ > LinkedIn - http://www.linkedin.com/in/ssagara > -- Shameera Rathnayaka
Re: [VOTE] Release Axis2 1.7.3
+1 Thanks. Shameera. On Fri, Jun 3, 2016 at 10:36 AM Sagara Gunathunga < sagara.gunathu...@gmail.com> wrote: > +1 > > Thanks ! > > On Mon, May 30, 2016 at 10:44 PM, Andreas Veithen < > andreas.veit...@gmail.com> wrote: > >> This is a vote to release Apache Axis2 1.7.3. >> >> SVN tag: >> http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.3/ >> Maven artifacts: >> https://repository.apache.org/content/repositories/orgapacheaxis2-1009 >> Distributions: >> https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/1.7.3/ >> Site: http://axis.apache.org/axis2/java/core-staging/ >> >> Here is my +1. >> >> Andreas >> >> - >> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >> For additional commands, e-mail: java-dev-h...@axis.apache.org >> >> > > > -- > Sagara Gunathunga > > Blog - http://ssagara.blogspot.com > Web - http://people.apache.org/~sagara/ > LinkedIn - http://www.linkedin.com/in/ssagara > -- Shameera Rathnayaka
Re: [VOTE] Release Axis2 1.7.2
+1 Thanks, Shameera. On Tue, May 3, 2016 at 12:08 PM Kishanthan Thangarajah < kshanth2...@gmail.com> wrote: > +1 > > Thanks, > Kishanthan. > > On Tue, May 3, 2016 at 1:09 AM, Andreas Veithen > <andreas.veit...@gmail.com> wrote: > > This is a vote to release Apache Axis2 1.7.2. > > > > SVN tag: > http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.2/ > > Maven artifacts: > > https://repository.apache.org/content/repositories/orgapacheaxis2-1008 > > Distributions: > https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/1.7.2/ > > Site: http://axis.apache.org/axis2/java/core-staging/ > > > > Here is my +1. > > > > Andreas > > > > - > > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > > For additional commands, e-mail: java-dev-h...@axis.apache.org > > > > - > To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org > For additional commands, e-mail: java-dev-h...@axis.apache.org > > -- Shameera Rathnayaka
Re: [VOTE] Release Axis2 1.7.1
+1 Thanks, Shameera On Mon, Feb 22, 2016 at 12:07 AM Thilina Gunarathne <cset...@gmail.com> wrote: > +1 > > thanks, > Thilina > > On Sun, Feb 21, 2016 at 11:18 PM, Sagara Gunathunga < > sagara.gunathu...@gmail.com> wrote: > >> +1 >> >> Thanks ! >> >> On Sun, Feb 21, 2016 at 4:50 AM, Andreas Veithen < >> andreas.veit...@gmail.com> wrote: >> >>> This is a vote to release Apache Axis2 1.7.1. >>> >>> SVN tag: >>> http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.1/ >>> Maven artifacts: >>> https://repository.apache.org/content/repositories/orgapacheaxis2-1007 >>> Distributions: >>> https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/1.7.1/ >>> Site: http://axis.apache.org/axis2/java/core-staging/ >>> >>> Here is my +1. >>> >>> Andreas >>> >>> - >>> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >>> For additional commands, e-mail: java-dev-h...@axis.apache.org >>> >>> >> >> >> -- >> Sagara Gunathunga >> >> Blog - http://ssagara.blogspot.com >> Web - http://people.apache.org/~sagara/ >> LinkedIn - http://www.linkedin.com/in/ssagara >> > > > > -- > https://www.cs.indiana.edu/~tgunarat/ > http://www.linkedin.com/in/thilina > http://thilina.gunarathne.org > -- Shameera Rathnayaka
Re: [VOTE] Release Axis2 and Rampart 1.7.0
+1 Shameera On Tue, Jan 19, 2016 at 6:39 AM Upul Godage <upulg@gmail.com> wrote: > +1 > > Thanks > > Upul > > On Tue, Jan 19, 2016 at 9:40 AM, Andreas Veithen < > andreas.veit...@gmail.com> wrote: > >> This is a combined vote for the release of Axis2 and Rampart 1.7.0. >> >> ** SVN tags: >> >> http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.7.0/ >> http://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.7.0/ >> >> ** Maven artifacts: >> >> https://repository.apache.org/content/repositories/orgapacheaxis2-1006 >> >> ** Distributions: >> >> https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/1.7.0/ >> https://dist.apache.org/repos/dist/dev/axis/axis2/java/rampart/1.7.0/ >> >> ** Sites: >> >> http://axis.apache.org/axis2/java/core-staging/ >> http://axis.apache.org/axis2/java/rampart-staging/ >> >> >> Andreas >> >> - >> To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org >> For additional commands, e-mail: java-dev-h...@axis.apache.org >> >> > > > -- > http://upulgodage.com > -- Shameera Rathnayaka
[jira] [Resolved] (AXIS2-5702) Axis2 trunk build with java 8(JDK 1.8)
[ https://issues.apache.org/jira/browse/AXIS2-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5702. Resolution: Fixed Yes, build works for me as well with jdk1.8.0_45. Axis2 trunk build with java 8(JDK 1.8) -- Key: AXIS2-5702 URL: https://issues.apache.org/jira/browse/AXIS2-5702 Project: Axis2 Issue Type: Wish Reporter: Shameera Rathnayaka There are set of build issues with jdk 1.8 including JAXWS issues, osgi issues Javax wsdl generation issues, JiBX issues etc Some of them can be resolved quickly but issues with JiBX need to wait for a new release with BCEL 6.0 which has a fix for java 8 https://issues.apache.org/jira/browse/BCEL-173, According to this https://github.com/jibx/jibx/issues/3 couldn't expect any near future releases for JiBX. One option is to move to JAXB instead of JiBX. This required to replace axis2 jibx module with JAXB code. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-5703) Code generation issues with jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka reassigned AXIS2-5703: -- Assignee: Shameera Rathnayaka Code generation issues with jdk 1.8 Key: AXIS2-5703 URL: https://issues.apache.org/jira/browse/AXIS2-5703 Project: Axis2 Issue Type: Sub-task Components: jaxws Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 Build fails almost all code generation parts due to the new XML security properties in JAXB 1.5, introduced in Java 8. This can be resolve by setting javax.xml.accessExternalSchema=all . -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5700) Fault Handler not reached when soap envelope contains empty namespace
[
https://issues.apache.org/jira/browse/AXIS2-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621047#comment-14621047
]
Shameera Rathnayaka commented on AXIS2-5700:
According to the SOAP spec , Envelop should be under
http://schemas.xmlsoap.org/soap/envelope/; namespace identifier. Hence your
sample soap envelop is wrong. See
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383494
Fault Handler not reached when soap envelope contains empty namespace
-
Key: AXIS2-5700
URL: https://issues.apache.org/jira/browse/AXIS2-5700
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.6.2
Environment: Windows 7 Professional. Java 6+, Tomcat, JBoss.
Reporter: Randall Vasquez
A customer has a requirement that our application be secure. One of the
issues brought up was component names being leaked in error messages which
may assist hackers by providing info they may use in future attacks.
To resolve this issue we attempted to use a simple custom handler that checks
for a fault and replaces the message with something more generic.
The axis2.xml file was then modified to include the handler within the
InFaultFlow and OutFaultFlows in the appropriate section as defined by the
axis2.xml.
However when a namespace is empty in the soap message or there is an issue in
the envelope at the root element
example:
Envelope xmlns:soapenv=
...otherwise well constructed soap message
/Envelope
the AxisServlet throws an AxisFault exception bypassing the handlers
and leaking info
example result:
soapenv:Envelope
...
faultstringcom.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character
(NULL, unicode 0) encountered: not valid in any content
at [row,col {unknown-source}]: [1,313]/faultstring
..
/soapenv:Envelope
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5706) Webapp build failure with jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5706. Resolution: Fixed Webapp build failure with jdk 1.8 - Key: AXIS2-5706 URL: https://issues.apache.org/jira/browse/AXIS2-5706 Project: Axis2 Issue Type: Sub-task Reporter: Eranda Sooriyabandara Attachments: axis2_webapp.patch Build fail with the following log [INFO] --- maven-jetty-jspc-plugin:6.1.26:jspc (default) @ axis2-webapp --- Compiling axis2-web/admin.jsp,axis2-web/viewServiceContext.jsp,axis2-web/LeftFrame.jsp,axis2-web/upload.jsp,axis2-web/index.jsp,axis2-web/HappyAxis.jsp,axis2-web/viewServiceGroupContext.jsp,axis2-web/listModules.jsp,axis2-web/listFaultyService.jsp,axis2-web/engagingtoanoperation.jsp,axis2-web/engagingglobally.jsp,axis2-web/deleteService.jsp,axis2-web/include/link-footer.jsp,axis2-web/include/adminheader.jsp,axis2-web/include/adminfooter.jsp,axis2-web/include/httpbase.jsp,axis2-web/error.jsp,axis2-web/ActivateService.jsp,axis2-web/listServices.jsp,axis2-web/EngageToServiceGroup.jsp,axis2-web/SelectService.jsp,axis2-web/listSingleService.jsp,axis2-web/InActivateService.jsp,axis2-web/ViewServiceHandlers.jsp,axis2-web/ViewGlobalHandlers.jsp,axis2-web/disengage.jsp,axis2-web/listGroupService.jsp,axis2-web/Login.jsp,axis2-web/ListServiceGroup.jsp,axis2-web/TopFrame.jsp,axis2-web/ServiceParaEdit.jsp,axis2-web/globalModules.jsp,axis2-web/listService.jsp,axis2-web/viewphases.jsp,axis2-web/errorModule.jsp,axis2-web/engagingtoaservice.jsp,axis2-web/Error/error500.jsp,axis2-web/Error/error404.jsp,axis2-web/MainFrame.jsp,axis2-web/ViewContexts.jsp Includes=**/*.jsp, **/*.jspx Excludes=null [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.913 s [INFO] Finished at: 2015-07-08T07:08:15-04:00 [INFO] Final Memory: 29M/307M [INFO] [ERROR] Failed to execute goal org.mortbay.jetty:maven-jetty-jspc-plugin:6.1.26:jspc (default) on project axis2-webapp: Failure processing jsps - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the fol -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Comment Edited] (AXIS2-5700) Fault Handler not reached when soap envelope contains empty namespace
[
https://issues.apache.org/jira/browse/AXIS2-5700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14621047#comment-14621047
]
Shameera Rathnayaka edited comment on AXIS2-5700 at 7/9/15 6:47 PM:
According to the SOAP spec , Envelop should be under
http://schemas.xmlsoap.org/soap/envelope/; namespace identifier. Hence your
sample soap envelop is wrong. See
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383494
For soap12 , Envelop namespace is http://www.w3.org/2003/05/soap-envelope; ,
spec http://www.w3.org/TR/soap12/#soapenvelope
was (Author: shameera):
According to the SOAP spec , Envelop should be under
http://schemas.xmlsoap.org/soap/envelope/; namespace identifier. Hence your
sample soap envelop is wrong. See
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383494
Fault Handler not reached when soap envelope contains empty namespace
-
Key: AXIS2-5700
URL: https://issues.apache.org/jira/browse/AXIS2-5700
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.6.2
Environment: Windows 7 Professional. Java 6+, Tomcat, JBoss.
Reporter: Randall Vasquez
A customer has a requirement that our application be secure. One of the
issues brought up was component names being leaked in error messages which
may assist hackers by providing info they may use in future attacks.
To resolve this issue we attempted to use a simple custom handler that checks
for a fault and replaces the message with something more generic.
The axis2.xml file was then modified to include the handler within the
InFaultFlow and OutFaultFlows in the appropriate section as defined by the
axis2.xml.
However when a namespace is empty in the soap message or there is an issue in
the envelope at the root element
example:
Envelope xmlns:soapenv=
...otherwise well constructed soap message
/Envelope
the AxisServlet throws an AxisFault exception bypassing the handlers
and leaking info
example result:
soapenv:Envelope
...
faultstringcom.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character
(NULL, unicode 0) encountered: not valid in any content
at [row,col {unknown-source}]: [1,313]/faultstring
..
/soapenv:Envelope
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5703) Code generation issues with jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5703. Resolution: Fixed Code generation issues with jdk 1.8 Key: AXIS2-5703 URL: https://issues.apache.org/jira/browse/AXIS2-5703 Project: Axis2 Issue Type: Sub-task Components: jaxws Reporter: Shameera Rathnayaka Fix For: 1.7.0 Build fails almost all code generation parts due to the new XML security properties in JAXB 1.5, introduced in Java 8. This can be resolve by setting javax.xml.accessExternalSchema=all . -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Reopened] (AXIS2-5703) Code generation issues with jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka reopened AXIS2-5703: Code generation issues with jdk 1.8 Key: AXIS2-5703 URL: https://issues.apache.org/jira/browse/AXIS2-5703 Project: Axis2 Issue Type: Sub-task Components: jaxws Reporter: Shameera Rathnayaka Fix For: 1.7.0 Build fails almost all code generation parts due to the new XML security properties in JAXB 1.5, introduced in Java 8. This can be resolve by setting javax.xml.accessExternalSchema=all . -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5705) Axis2 osgi module build failed with Jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5705. Resolution: Fixed Fix Version/s: 1.7.0 Axis2 osgi module build failed with Jdk 1.8 --- Key: AXIS2-5705 URL: https://issues.apache.org/jira/browse/AXIS2-5705 Project: Axis2 Issue Type: Sub-task Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Fix For: 1.7.0 [INFO] --- maven-bundle-plugin:2.1.0:bundle (default-bundle) @ org.apache.axis2.osgi --- [ERROR] Error building bundle org.apache.axis2:org.apache.axis2.osgi:bundle:1.7.0-SNAPSHOT : Unresolved references to [com.ibm.wsdl, org.apache.http.auth.params] by class(es) on the Bundle-Classpath[Jar:dot]: [org/apache/axis2/util/XMLUtils.class, org/apache/axis2/wsdl/util/WSDLWrapperReloadImpl.class, org/apache/axis2/transport/http/impl/httpclient4/HTTPSenderImpl.class] [ERROR] Error(s) found in bundle configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5703) Code generation issues with jdk 1.8
[ https://issues.apache.org/jira/browse/AXIS2-5703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5703. Resolution: Fixed Code generation issues with jdk 1.8 Key: AXIS2-5703 URL: https://issues.apache.org/jira/browse/AXIS2-5703 Project: Axis2 Issue Type: Sub-task Components: jaxws Reporter: Shameera Rathnayaka Fix For: 1.7.0 Build fails almost all code generation parts due to the new XML security properties in JAXB 1.5, introduced in Java 8. This can be resolve by setting javax.xml.accessExternalSchema=all . -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5702) Axis2 trunk build with java 8(JDK 1.8)
[ https://issues.apache.org/jira/browse/AXIS2-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617474#comment-14617474 ] Shameera Rathnayaka commented on AXIS2-5702: Yes, I saw this as well, I couldn't dig deep to find the root cause for this. could you able to find anything? Axis2 trunk build with java 8(JDK 1.8) -- Key: AXIS2-5702 URL: https://issues.apache.org/jira/browse/AXIS2-5702 Project: Axis2 Issue Type: Wish Reporter: Shameera Rathnayaka There are set of build issues with jdk 1.8 including JAXWS issues, osgi issues Javax wsdl generation issues, JiBX issues etc Some of them can be resolved quickly but issues with JiBX need to wait for a new release with BCEL 6.0 which has a fix for java 8 https://issues.apache.org/jira/browse/BCEL-173, According to this https://github.com/jibx/jibx/issues/3 couldn't expect any near future releases for JiBX. One option is to move to JAXB instead of JiBX. This required to replace axis2 jibx module with JAXB code. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5702) Axis2 trunk build with java 8(JDK 1.8)
[ https://issues.apache.org/jira/browse/AXIS2-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14617549#comment-14617549 ] Shameera Rathnayaka commented on AXIS2-5702: Hi Andreas, I could able to fix this, root cause was, in ExtensionTypesTest class was getting operation by index, but the order of operations are different with jdk 1.7 and jdk 1.8. I changed it to get operation by operation name and it works for both jdks. for more info check commit r1689760. Thanks, Shameera. Axis2 trunk build with java 8(JDK 1.8) -- Key: AXIS2-5702 URL: https://issues.apache.org/jira/browse/AXIS2-5702 Project: Axis2 Issue Type: Wish Reporter: Shameera Rathnayaka There are set of build issues with jdk 1.8 including JAXWS issues, osgi issues Javax wsdl generation issues, JiBX issues etc Some of them can be resolved quickly but issues with JiBX need to wait for a new release with BCEL 6.0 which has a fix for java 8 https://issues.apache.org/jira/browse/BCEL-173, According to this https://github.com/jibx/jibx/issues/3 couldn't expect any near future releases for JiBX. One option is to move to JAXB instead of JiBX. This required to replace axis2 jibx module with JAXB code. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: Axis2 Build On Different Platforms
Hi Eranda, Now the webapp and osgi-test modules are not building with jdk1.8 , would you like to have a look on that? Regards, Shameera. On Tue, Jul 7, 2015 at 9:32 PM Eranda Sooriyabandara eranda.sooriyaband...@gmail.com wrote: Then I can give a hand to Shameera on building. thanks Eranda On Tue, Jul 7, 2015 at 4:07 PM, Andreas Veithen andreas.veit...@gmail.com wrote: This isn't about taking advantage of JDK 8 features. Our CI builds use Java 7 anyway (and if the infra team fixes the current problem with Java 6, I will probably switch then back to that version). The purpose is to allow users to build the source code using a wider range of Java versions. Andreas On Tue, Jul 7, 2015 at 4:00 AM, Eranda Sooriyabandara eranda.sooriyaband...@gmail.com wrote: I am not discouraging on fixing the build failures on jdk 8 but just building on jdk 8 does not mean that Axis2 take the full advantage of jdk 8 or compatible jdk 8. Isn't it best if we can stick to jdk 7 for the oncoming release and later do a migration as a team effort. thanks Eranda On Mon, Jul 6, 2015 at 7:03 PM, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Andreas, This is due to jaxb security property change with jdk 8. I could able to fix this by setting javax.xml.accessExternalSchema=all in few places where we use ant java task and run JAXWS code generation Tests. Then i got osgi bundle issue and could able fix that too. There are few other issues with integration test i am woking on that. Thanks, Shameera. On Sat, Jul 4, 2015 at 11:50 AM Andreas Veithen andreas.veit...@gmail.com wrote: On Fri, Jul 3, 2015 at 4:31 AM, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Hiranya/Deepal, I could able to build axis2 trunk with Mac OS X + Jdk1.7 with test after increasing the premgen. FYI trunk build failed with jdk1.8 with test compilation failures in jaxws module. A quick search with the error message shows that there are lots of projects that have a similar problem (including CXF). Can you do some research to figure out how others have solved this? Thanks, Shameera. On Thu, Jul 2, 2015 at 9:32 PM Hiranya Jayathilaka hiranya...@gmail.com wrote: I was able to build on Linux+JDK 1.6 too. The error Andun pointed out is actually a Maven problem. I got the same error when running Maven 3.3 on JDK 1.6. Apparently that's not a supported combination. If you use Maven 3.2, things work fine. I think it's safe to assume that Axis2 builds fine on Linux. Andun, can you try to build on Windows with a larger permgen space, and see if everything's ok? Thanks, Hiranya On Thu, Jul 2, 2015 at 5:48 PM, Deepal Jayasinghe deep...@gmail.com wrote: I think it should be safer to assume 1.7, it is hard to support old JDKs. (Yes, I too got things working with 1.7+Ubuntu with heap size increase.) Deepal On Thu, Jul 2, 2015 at 5:42 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: I was able to build the trunk on Linux+JDK 1.7 with all the tests passing. There were initially some problems with Maven running out of permgen space, but once I increased that limit (to 512MB), things went smoothly. I have a feeling you will see similar results on Windows+JDK 1.7 if you set the permgen space limit to a higher value. Deepal, what is the lowest JDK compatibility level we should have? 1.6 or 1.7? Thanks, Hiranya On Thu, Jul 2, 2015 at 3:28 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: Hi Andun, Thanks for looking into this problem. Have you found any root causes/solutions? Some more comments in-line: On Thu, Jul 2, 2015 at 12:50 AM, Andun Sameera andun...@gmail.com wrote: Hi Devs, I tried testing $subject. The build is successful without tests in Linux with JDK 1.7. The build is failed with tests in Linux with JDK 1.7. This is somewhat troublesome. I'll see if I can reproduce this. Btw, isn't this the same setup used in Jenkins? In Windows with JDK 1.6 cases a UnsupportedClassVersionError In Windows with JDK 1.7 build failed due to out of of memory issues in Maven. Can you try this with Maven Permgen space increased? Thanks, Hiranya In Windows with JDK 1.8 build fails due to test failures as well as dependency misses These are the logs, JDK 1.6.0_45,Windows 8.1 64 bit With Tests/Without Test - Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615
Re: Axis2 Build On Different Platforms
Hi Andreas, This is due to jaxb security property change with jdk 8. I could able to fix this by setting javax.xml.accessExternalSchema=all in few places where we use ant java task and run JAXWS code generation Tests. Then i got osgi bundle issue and could able fix that too. There are few other issues with integration test i am woking on that. Thanks, Shameera. On Sat, Jul 4, 2015 at 11:50 AM Andreas Veithen andreas.veit...@gmail.com wrote: On Fri, Jul 3, 2015 at 4:31 AM, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi Hiranya/Deepal, I could able to build axis2 trunk with Mac OS X + Jdk1.7 with test after increasing the premgen. FYI trunk build failed with jdk1.8 with test compilation failures in jaxws module. A quick search with the error message shows that there are lots of projects that have a similar problem (including CXF). Can you do some research to figure out how others have solved this? Thanks, Shameera. On Thu, Jul 2, 2015 at 9:32 PM Hiranya Jayathilaka hiranya...@gmail.com wrote: I was able to build on Linux+JDK 1.6 too. The error Andun pointed out is actually a Maven problem. I got the same error when running Maven 3.3 on JDK 1.6. Apparently that's not a supported combination. If you use Maven 3.2, things work fine. I think it's safe to assume that Axis2 builds fine on Linux. Andun, can you try to build on Windows with a larger permgen space, and see if everything's ok? Thanks, Hiranya On Thu, Jul 2, 2015 at 5:48 PM, Deepal Jayasinghe deep...@gmail.com wrote: I think it should be safer to assume 1.7, it is hard to support old JDKs. (Yes, I too got things working with 1.7+Ubuntu with heap size increase.) Deepal On Thu, Jul 2, 2015 at 5:42 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: I was able to build the trunk on Linux+JDK 1.7 with all the tests passing. There were initially some problems with Maven running out of permgen space, but once I increased that limit (to 512MB), things went smoothly. I have a feeling you will see similar results on Windows+JDK 1.7 if you set the permgen space limit to a higher value. Deepal, what is the lowest JDK compatibility level we should have? 1.6 or 1.7? Thanks, Hiranya On Thu, Jul 2, 2015 at 3:28 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: Hi Andun, Thanks for looking into this problem. Have you found any root causes/solutions? Some more comments in-line: On Thu, Jul 2, 2015 at 12:50 AM, Andun Sameera andun...@gmail.com wrote: Hi Devs, I tried testing $subject. The build is successful without tests in Linux with JDK 1.7. The build is failed with tests in Linux with JDK 1.7. This is somewhat troublesome. I'll see if I can reproduce this. Btw, isn't this the same setup used in Jenkins? In Windows with JDK 1.6 cases a UnsupportedClassVersionError In Windows with JDK 1.7 build failed due to out of of memory issues in Maven. Can you try this with Maven Permgen space increased? Thanks, Hiranya In Windows with JDK 1.8 build fails due to test failures as well as dependency misses These are the logs, JDK 1.6.0_45,Windows 8.1 64 bit With Tests/Without Test - Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at org.codehaus.plexus.classworlds.launcher.Launcher.getMainClass(Launcher.java:144) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:266) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415
[jira] [Created] (AXIS2-5702) Axis2 trunk build with java 8(JDK 1.8)
Shameera Rathnayaka created AXIS2-5702: -- Summary: Axis2 trunk build with java 8(JDK 1.8) Key: AXIS2-5702 URL: https://issues.apache.org/jira/browse/AXIS2-5702 Project: Axis2 Issue Type: Wish Affects Versions: 1.7.0, 1.6.4 Reporter: Shameera Rathnayaka There are set of build issues with jdk 1.8 including JAXWS issues, osgi issues Javax wsdl generation issues, JiBX issues etc Some of them can be resolved quickly but issues with JiBX need to wait for a new release with BCEL 6.0 which has a fix for java 8 https://issues.apache.org/jira/browse/BCEL-173, According to this https://github.com/jibx/jibx/issues/3 couldn't expect any near future releases for JiBX. One option is to move to JAXB instead of JiBX. This required to replace axis2 jibx module with JAXB code. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5704) JiBX doesn't works with Jdk 1.8
Shameera Rathnayaka created AXIS2-5704: -- Summary: JiBX doesn't works with Jdk 1.8 Key: AXIS2-5704 URL: https://issues.apache.org/jira/browse/AXIS2-5704 Project: Axis2 Issue Type: Sub-task Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Getting following build failure, from more details check this https://github.com/jibx/jibx/issues/3 . One option is to replace JiBX module with JAXB which is default comes with java 8. [INFO] --- maven-antrun-plugin:1.2:run (compile) @ axis2-jibx --- [INFO] Executing tasks [java] Error running binding compiler [java] java.lang.IllegalStateException: Error loading class java.lang.CharSequence: Error reading path java/lang/CharSequence.class for class java.lang.CharSequence [java] at org.jibx.binding.classes.ClassCache$ClassCacheLocator.getClassInfo(ClassCache.java:264) [java] at org.jibx.binding.model.ClassHierarchyContext.accumulateInterfaces(ClassHierarchyContext.java:96) [java] at org.jibx.binding.model.ClassHierarchyContext.addTypedComponent(ClassHierarchyContext.java:121) [java] at org.jibx.binding.model.DefinitionContext.addFormat(DefinitionContext.java:469) [java] at org.jibx.binding.model.BindingElement.defineBaseFormat(BindingElement.java:774) [java] at org.jibx.binding.model.BindingElement.runValidation(BindingElement.java:793) [java] at org.jibx.binding.model.BindingElement.validateBinding(BindingElement.java:885) [java] at org.jibx.binding.Utility.validateBinding(Utility.java:246) [java] at org.jibx.binding.Utility.loadBinding(Utility.java:288) [java] at org.jibx.binding.Utility.loadFileBinding(Utility.java:431) [java] at org.jibx.binding.Compile.compile(Compile.java:212) [java] at org.jibx.binding.Compile.main(Compile.java:374) -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5705) Axis2 osgi module build failed with Jdk 1.8
Shameera Rathnayaka created AXIS2-5705: -- Summary: Axis2 osgi module build failed with Jdk 1.8 Key: AXIS2-5705 URL: https://issues.apache.org/jira/browse/AXIS2-5705 Project: Axis2 Issue Type: Sub-task Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka [INFO] --- maven-bundle-plugin:2.1.0:bundle (default-bundle) @ org.apache.axis2.osgi --- [ERROR] Error building bundle org.apache.axis2:org.apache.axis2.osgi:bundle:1.7.0-SNAPSHOT : Unresolved references to [com.ibm.wsdl, org.apache.http.auth.params] by class(es) on the Bundle-Classpath[Jar:dot]: [org/apache/axis2/util/XMLUtils.class, org/apache/axis2/wsdl/util/WSDLWrapperReloadImpl.class, org/apache/axis2/transport/http/impl/httpclient4/HTTPSenderImpl.class] [ERROR] Error(s) found in bundle configuration -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: Axis2 Build On Different Platforms
Hi Hiranya/Deepal, I could able to build axis2 trunk with Mac OS X + Jdk1.7 with test after increasing the premgen. FYI trunk build failed with jdk1.8 with test compilation failures in jaxws module. Thanks, Shameera. On Thu, Jul 2, 2015 at 9:32 PM Hiranya Jayathilaka hiranya...@gmail.com wrote: I was able to build on Linux+JDK 1.6 too. The error Andun pointed out is actually a Maven problem. I got the same error when running Maven 3.3 on JDK 1.6. Apparently that's not a supported combination. If you use Maven 3.2, things work fine. I think it's safe to assume that Axis2 builds fine on Linux. Andun, can you try to build on Windows with a larger permgen space, and see if everything's ok? Thanks, Hiranya On Thu, Jul 2, 2015 at 5:48 PM, Deepal Jayasinghe deep...@gmail.com wrote: I think it should be safer to assume 1.7, it is hard to support old JDKs. (Yes, I too got things working with 1.7+Ubuntu with heap size increase.) Deepal On Thu, Jul 2, 2015 at 5:42 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: I was able to build the trunk on Linux+JDK 1.7 with all the tests passing. There were initially some problems with Maven running out of permgen space, but once I increased that limit (to 512MB), things went smoothly. I have a feeling you will see similar results on Windows+JDK 1.7 if you set the permgen space limit to a higher value. Deepal, what is the lowest JDK compatibility level we should have? 1.6 or 1.7? Thanks, Hiranya On Thu, Jul 2, 2015 at 3:28 PM, Hiranya Jayathilaka hiranya...@gmail.com wrote: Hi Andun, Thanks for looking into this problem. Have you found any root causes/solutions? Some more comments in-line: On Thu, Jul 2, 2015 at 12:50 AM, Andun Sameera andun...@gmail.com wrote: Hi Devs, I tried testing $subject. - The build is successful without tests in Linux with JDK 1.7. - The build is failed with tests in Linux with JDK 1.7. This is somewhat troublesome. I'll see if I can reproduce this. Btw, isn't this the same setup used in Jenkins? - - In Windows with JDK 1.6 cases a UnsupportedClassVersionError - In Windows with JDK 1.7 build failed due to out of of memory issues in Maven. Can you try this with Maven Permgen space increased? Thanks, Hiranya - In Windows with JDK 1.8 build fails due to test failures as well as dependency misses These are the logs, JDK 1.6.0_45,Windows 8.1 64 bit With Tests/Without Test - Exception in thread main java.lang.UnsupportedClassVersionError: org/apache/maven/cli/MavenCli : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(ClassRealm.java:401) at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:42) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:254) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239) at org.codehaus.plexus.classworlds.launcher.Launcher.getMainClass(Launcher.java:144) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:266) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) JDK 1.7.0_13,Windows 8.1 64 bit With Tests - [ERROR] PermGen space - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryError C:\Program Files (x86)\Java\jdk1.7.0_51;C:\Users\Andun S L Gunwardana\AppData\Roaming\npm;%ANDROID_PLATFORM_TOOLS%;%ANDROID_TOOLS%;%OPENCV_DIR%\x64\vc12\bin;%M2_HOME%\bin C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\iCLS
Re: [VOTE] Release Axis2 1.6.3
+1 Thanks, Shameera. On Mon, Jun 29, 2015 at 8:34 AM, Kishanthan Thangarajah kshanth2...@gmail.com wrote: +1, Thanks, On Sun, Jun 28, 2015 at 5:35 AM, Andreas Veithen andreas.veit...@gmail.com wrote: Here is the vote for the Axis2 1.6.3 release. SVN tag: https://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.6.3/ Maven artifacts: https://repository.apache.org/content/repositories/orgapacheaxis2-1000/ Distributions: https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/1.6.3/ Site: http://axis.apache.org/axis2/java/core-staging/ Here is my +1. Andreas - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Closed] (AXIS2-5515) ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO.
[ https://issues.apache.org/jira/browse/AXIS2-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka closed AXIS2-5515. -- Resolution: Won't Fix According to the last reply, this will not be supported, because this will cause lot of issues. ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO. -- Key: AXIS2-5515 URL: https://issues.apache.org/jira/browse/AXIS2-5515 Project: Axis2 Issue Type: Improvement Components: kernel Affects Versions: 1.6.2, 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 Attachments: ObjectSupplier.patch Currently ObjectSupplier interface doesn't provide a way to instantiate Objects in runtime which doesn't has nullary constructor. it only define one method which takes only class object as method parameter. There is no way to instantiate a non POJO in runtime. Even we doesn't need to provide such a feature with DefaultObjectSupplier , it is good to provide a API to do that. Then user can provide their own implementation this. Adding new method(Object getObject(Class clazz , OMElement beanElement) throws AxisFault;) to ObjectSupplier would provide this. We don't need to implement this method in our DeafaultObjectSuppler. One use case for this is Java.util.UUID , this class doesn't has nullary constructor which only has UUID(long mostSigBits, long leastSigBits) , in such a case user can writer their own implementation of ObjectSupplier and use it. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Closed] (AXIS2-5513) Decouple google-gson from JSON xml stream basae approach using JSR 353(Java api to JSON processing)
[ https://issues.apache.org/jira/browse/AXIS2-5513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka closed AXIS2-5513. -- Resolution: Later JSR 353-Java API doesn't provide enough data to make this change. In processing we need to know every token in JSON which is not available with above spec.Hence I am moving this to later. Decouple google-gson from JSON xml stream basae approach using JSR 353(Java api to JSON processing) --- Key: AXIS2-5513 URL: https://issues.apache.org/jira/browse/AXIS2-5513 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: gson, json, jsr-353 Fix For: 1.7.0 Currently newly added JSON XML Stream API base approach, tightly couple with google-gson. Decoupling google-gson from this would make more extensible to use other JSON Stream APIs(like Jakson). Here we can use factory method pattern to create JSON XMLStreamReaders/writers . And we can provide an api(this will be JSR 353-Java API for JSON processing) to implement Gson, Jakson or any other Json Stream support api to write the logic under that. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
[ https://issues.apache.org/jira/browse/AXIS2-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5416. Resolution: Fixed Add Native approach and XML Stream API base approach Documentations --- Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: Documentation, json Fix For: 1.7.0 Attachments: JSONDucumentation.patch Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: [Axis2] Build failure
Hi Deepal,
I too got test failures with JDK 1.7 and got build success with JDK 1.6. Do
we have documented this ? if not isn't it better to do that ?
Thanks,
Shameera.
On Mon, Mar 31, 2014 at 6:48 AM, Deepal jayasinghe deep...@gmail.comwrote:
Found the problem, I was using JDK1.7 and seems like build has some
issues with it. Downgraded (set the JAVA_HOME) to and problem went away.
Deepal
Date: Sun, 30 Mar 2014 11:45:01 -0700
From: deep...@gmail.com
To: java-dev@axis.apache.org
Subject: [Axis2] Build failure
I am getting following build error, is that only for me?
Failed tests:
SchemaDataLocatorTest.testOutputInlineForm:79-XMLSchemaTest.assertSimilarXML:
66 XML similar org.custommonkey.xmlunit.Diff
[different] Expected attribute value 'echoStringArray' but was
'echoString' - co
mparing xs:element name=echoStringArray... at
/schema[1]/element[1]/@name to
xs:element name=echoString... at /schema[1]/element[1]/@name
MGpackage org.apache.axis2.sample.echo;
public class EchoImpl {
public EchoImpl() {
}
public java.lang.String echoString(java.lang.String in) {
return in;
}
public java.lang.String[] echoStringArray(java.lang.String[] in) {
return in;
}
}
MG
MG referencing META-INF/services.xml
service name=
description
This is a testing service , to test the system is working or not
/description
parameter
name=ServiceClassorg.apache.axis2.sample.echo.EchoImpl/parameter
operation name=echoStringArray
message label=In
parameter name=messageINmessageIN/parameter
/message
message label=Out
parameter name=messageOutmessageOut/parameter
/message
/operation
/service
MG
MGthe binding in WSDL
binding name=Axis2SampleDocLitPortBinding
type=tns:Axis2SampleDocLitPortType
soap:binding style=document transport=
http://schemas.xmlsoap.org/soap/http/
operation name=echoStringArray
soap:operation soapAction=echoStringArray style=document/
input
soap:body use=literal namespace=
http://userguide.axis2.apache.org/Axis2SampleDocLit/
/input
output
soap:body use=literal namespace=
http://userguide.axis2.apache.org/Axis2SampleDocLit/
/output
/operation
MGit looks as if your default namespace is
http://userguide.axis2.apache.org/Axis2SampleDocLit
which is in same location as Flight MH370
MGwhat happens when you switch your default namespace to your own XSD?
MGMartin
DefaultSchemaGeneratorTest.testExtendedPOJO:541-testClass:115-XMLSchemaTest.
assertSimilarXML:66 XML similar org.custommonkey.xmlunit.Diff
[different] Expected attribute value 'setSss' but was 'getSss' -
comparing xs:e
lement name=setSss... at /schema[1]/element[1]/@name to xs:element
name=get
Sss... at /schema[1]/element[1]/@name
DefaultSchemaGeneratorTest.testAbstractPOJO:545-testClass:115-XMLSchemaTest.
assertSimilarXML:66 XML similar org.custommonkey.xmlunit.Diff
[different] Expected attribute value 'setS' but was 'getI' - comparing
xs:eleme
nt name=setS... at /schema[1]/element[1]/@name to xs:element
name=getI...
at /schema[1]/element[1]/@name
DefaultSchemaGeneratorTest.testConcretePOJO:549-testClass:115-XMLSchemaTest.
assertSimilarXML:66 XML similar org.custommonkey.xmlunit.Diff
[different] Expected attribute value 'setS' but was 'isBool' - comparing
xs:ele
ment name=setS... at /schema[1]/element[1]/@name to xs:element
name=isBool
... at /schema[1]/element[1]/@name
DocLitBareSchemaGeneratorTestDefaultSchemaGeneratorTest.testExtendedPOJO:541-
DefaultSchemaGeneratorTest.testClass:115-XMLSchemaTest.assertSimilarXML:66
XML
similar org.custommonkey.xmlunit.Diff
[different] Expected attribute value 'sss' but was 'getSssResult' -
comparing x
s:element name=sss... at /schema[1]/element[1]/@name to xs:element
name=get
SssResult... at /schema[1]/element[1]/@name
DocLitBareSchemaGeneratorTestDefaultSchemaGeneratorTest.testAbstractPOJO:545-
DefaultSchemaGeneratorTest.testClass:115-XMLSchemaTest.assertSimilarXML:66
XML
similar org.custommonkey.xmlunit.Diff
[different] Expected attribute value 's' but was 'getIResult' -
comparing xs:el
ement name=s... at /schema[1]/element[1]/@name to xs:element
name=getIResul
t... at /schema[1]/element[1]/@name
Thanks
Deepal
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Resolved] (AXIS2-5635) rg.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing
[ https://issues.apache.org/jira/browse/AXIS2-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-5635. Resolution: Not A Problem Hi Mahendra, By default addressing module has been added as global module, therefore startup time engine try to engage the module but it is not in AXIS2_HOME/repository/modules/addressing-1.6.0.mar location. It seems axis2 engine can't find addressing module in that location. If you deliberately removed that module then removed module ref=addressing/ in axis2.xml file which means you don't need ws-addresssing. Cheers, Shameera. rg.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing Key: AXIS2-5635 URL: https://issues.apache.org/jira/browse/AXIS2-5635 Project: Axis2 Issue Type: Bug Components: Addressing Affects Versions: 1.6.0 Environment: Websphere 7.0 Axis2 1.6 Reporter: Mahendra Priority: Critical Original Estimate: 0.2h Remaining Estimate: 0.2h Folks any help here : The following is the error message we are getting rg.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing We have done everything possible from changing the AXIS2.XML settings child first parent last etc. However when we are launching our application we are getting the following error message in our environment . This works fine on a local laptop however in a clusterred environment AXIS its not working . Any Points -- This message was sent by Atlassian JIRA (v6.2#6252) - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: Upcoming Axis2 releases?
Hi Andrew, You are more than welcome to provide fixes for codebase or docs or both :), Please open a JIRA then and there for such fixes and attach your patch to the JIRA itself. And when you submit patches first provide it for current trunk ( 1.7.0-SNAPSHOT) and then we can push the same patch to 1.6.3 branch and this might require slightly modification for the original patch. Better add test cases too when ever possible to test your fix. Cheers, Shameera. On Sun, Mar 16, 2014 at 1:00 PM, Deepal jayasinghe deep...@gmail.comwrote: Hi Andrew, Do not worry about the JIRA thing. I think we need to do a release soon, I really wanted to push a release but did not want do it without proper testing. Let's try to get something out in next few months. Deepal Hi, Axis2 folks, First off, sorry for spamming the list with Jira activity earlier. I didn't realize that Jira sent notifications for all activity to the whole list. (When I've used it elsewhere it did more selective notifications and/or digests.) Are the Axis2 1.6.3 or 1.7.0 versions likely to make it to release in the foreseeable future? Looks like there've been no releases for two years, so it's a bit hard to gauge the activity level of this project. I've started working with Axis2 for one of my projects, and I'd like to make some basic contributions to the parts I'm using. Stuff along the lines of minor issues in the doco, fixes for the minor bugs I put in JIRA today, updating broken links in the site pages. Would this be useful, and likely to see release at some point? If so, would it be better to work on 1.6.3 or 1.7.0? Cheers, Andrew Janke - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
Re: Getting know the intention of Null key/values testing in ContextPropertiesExternalizeTest.java test case
Hi Vimesh, This is a critical change, doing this allow concurrent access to Message context is a good, but this will introduce a limitation to message context properties because concurrent map doesn't support null keys and values. we need to find out which one is the most require. And need to consider user point of view as well (CCed user mailing list ). If you are providing a patch make sure to pass all test cases, in your case change failing test case to not to support null keys and values. Thanks, Shameera. On Thu, Feb 6, 2014 at 11:54 AM, Vimesh Gihan Samarawickrama vimesh...@gmail.com wrote: Hi Deepal, So is it required to have the ability to store null key/values in the properties map in AbstractContext.java? If not is it ok to change it into ConcurrentHashMap which does not allow to put null key/values. Thanks On Thu, Feb 6, 2014 at 11:17 AM, Deepal jayasinghe deep...@gmail.comwrote: Hi Vimesh, Open a JIRA issue and attach a patch, one of us should be able to fix the issue. Deepal Hi, I am using axis2-1.6.1 and here is my question. We can modify HashMap into ConcurrentHashMap in /modules/kernel/src/org/apache/axis2/context/AbstractContext.java in order to access that map concurrently. But there is a test case called ContextPropertiesExternalizeTest.java which puts null key/values to the map. But since modified ConcurrentHashMap does not allow to put null key/values it leads to fail. So could you please let me know the intention of testing with null key/values there. Thanks -- Vimesh Gihan Samarawickrama Undergraduate Department of Computer Science Engineering University of Moratuwa Sri Lanka -- Vimesh Gihan Samarawickrama Undergraduate Department of Computer Science Engineering University of Moratuwa Sri Lanka -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
Re: Retiring Sandesha2 from 1.7.0 release
+1 Thanks, Shameera. On Sat, Feb 1, 2014 at 2:32 PM, Andreas Veithen andreas.veit...@gmail.comwrote: +1 Andreas On Sunday, January 26, 2014, Sagara Gunathunga sagara.gunathu...@gmail.com wrote: I believe this is the right time to bring this discussion due to following reasons. 1. For many years I never see any user mail that indicate real use of Sandesha2, It's a question to me whether anyone still expecting newer versions of Sandesha2. 2. In my POV RM is not popular and not widely used as other WS technologies. Further some of the main users of Sandesha2 such as Synapse already decided to drop RM support. 3. From many years no one actively develop Sandesha2 code base and current situation is pathetic as test cases failing from time to time and no one have time/experience to fix them. Going forward retiring Sandesha2 will help to keep health of Axis TLP hence here is my +1. Having said if someone willing to actively develop and maintain Sandesha2 project in near future I'm more than happy to withdraw my proposal Thanks ! -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Commented] (AXIS2-5602) RequestURIBasedServiceDispatcher#findService is returning wrong axis service
[
https://issues.apache.org/jira/browse/AXIS2-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735952#comment-13735952
]
Shameera Rathnayaka commented on AXIS2-5602:
Hi Jayant,
Not only the service, endpoint may have operation name as well after the
service name (see
org.apache.axis2.dispatchers.RequestURIBasedOperationDispatcher) . With your
patch operation name also set as part of service name.
Thanks,
Shameera.
RequestURIBasedServiceDispatcher#findService is returning wrong axis service
Key: AXIS2-5602
URL: https://issues.apache.org/jira/browse/AXIS2-5602
Project: Axis2
Issue Type: Bug
Affects Versions: 1.6.2
Reporter: Jayant Vaish
Priority: Blocker
Attachments: AXIS_5602.patch
I am having two services deployed on axis2-1.6.2 having following
axisServiceName:
1. Service1/Start/WFmagic_cksXMrobEd2Fe4Kb1Aqw9Q
2. Service1/Start
Passing messageContext in
org.apache.axis2.dispatchers.RequestURIBasedServiceDispatcher.findService(MessageContext)
has following epr address:
EndpointReference toEPR = messageContext.getTo();
toEPR.getAddress() is
http://localhost:8080/axis2/services/Service1/Start/WFmagic_cksXMrobEd2Fe4Kb1Aqw9Q
So, expected axis service returned by
org.apache.axis2.dispatchers.RequestURIBasedServiceDispatcher.findService(MessageContext)
should be : Service1/Start/WFmagic_cksXMrobEd2Fe4Kb1Aqw9Q
But I am getting Service1/Start which is wrong !!!
Further looking into the code found the following snippet which seems to be
the culprit:
org.apache.axis2.dispatchers.RequestURIBasedServiceDispatcher.java
while (axisService == null count parts.length
count Constants.MAX_HIERARCHICAL_DEPTH) {
serviceName = count == 0 ? serviceName + parts[count] :
serviceName + / + parts[count];
axisService = registry.getService(serviceName);
count++;
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: axis2 deploy error
Hi, It should be http://services.abc.com/services/Version?wsdl in your case. Thanks, Shameera. On Tue, Jun 4, 2013 at 2:31 PM, gzxyong gzxy...@126.com wrote: ** Axis2 team: Excuse me,my english is poor. My axis2 deploy in top-level domain(www.abc.com) is Ok , but deploy in second-level(services.abc.com) domain ,it has some error. http://services.abc.com/axis2-web/HappyAxis.jsp is ok. http://services.abc.com/axis2-admin/ is ok. http://services.abc.com/services/listServices is ok ,I can see my services list , and my service status is active. But I clicked my service (http://services.abc.com/services/Version=?wsdl) ,errors was happened. Error: Http status 404 : Requested resource not found! =20 please help me,what's wrong with this. Thanks! -- gzxyong -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
Re: Re: axis2 deploy error
If http://services.abc.com/services/listServices works. then axis2 has deployed correctly it working. Can you see the Version service in that list? If it is there you can see it's WSDL by clicking on that. Cheers, Shameera. On Tue, Jun 4, 2013 at 6:20 PM, gzxyong gzxy...@126.com wrote: ** Hi,Thanks your answer. http://services.abc.com/services/Version?wsdl This service(Version) is axis2 sample,I think,it's no problem. My web server is tomcat,The project deployed in top-level domain(only one domain www.abc.com) ,It's ok. But I deploy it in second-level domain(services.abc.com),It has some errors. I don't know what's wrony with it. Thanks -- gzxyong *From:* Shameera Rathnayaka shameerai...@gmail.com *Date:* 2013-06-04 19:38 *To:* java-dev java-dev@axis.apache.org; gzxyong gzxy...@126.com *Subject:* Re: axis2 deploy error Hi, It should be http://services.abc.com/services/Version?wsdl in your case. Thanks, Shameera. On Tue, Jun 4, 2013 at 2:31 PM, gzxyong gzxy...@126.com wrote: ** Axis2 team: Excuse me,my english is poor. My axis2 deploy in top-level domain(www.abc.com) is Ok , but deploy in second-level(services.abc.com) domain ,it has some error. http://services.abc.com/axis2-web/HappyAxis.jsp is ok. http://services.abc.com/axis2-admin/ is ok. http://services.abc.com/services/listServices is ok ,I can see my services list , and my service status is active. But I clicked my service (http://services.abc.com/services/Version=?wsdl) ,errors was happened. Error: Http status 404 : Requested resource not found! =20 please help me,what's wrong with this. Thanks! -- gzxyong -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/ -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Commented] (AXIS2-5576) Missing build.xml in Axis2-1.6.2 Source Distribution
[ https://issues.apache.org/jira/browse/AXIS2-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672645#comment-13672645 ] Shameera Rathnayaka commented on AXIS2-5576: Hi Lewis , Thanks for you contribution. Applied patch in r1488761. As your patch had removed only the content of build.xml I deleted build.xml in r1488765. Cheers, Shameera. Missing build.xml in Axis2-1.6.2 Source Distribution Key: AXIS2-5576 URL: https://issues.apache.org/jira/browse/AXIS2-5576 Project: Axis2 Issue Type: Bug Components: documentation Affects Versions: 1.6.2 Reporter: Lewis John McGibbney Fix For: 1.7.0 Attachments: AVIS2-5576.v2.patch, AXIS2-5576.patch As mentioned here [0], I noticed that the Maven seesmbly descriptor does not include build.xml within the generated Source Distributions. The patch aims to include it (however someone will need to verify) and also includes some better documentation within README.txt [0] http://www.mail-archive.com/java-dev%40axis.apache.org/msg13085.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5577) axis2 caches the wsdl file when accessed by http or https
[
https://issues.apache.org/jira/browse/AXIS2-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668923#comment-13668923
]
Shameera Rathnayaka commented on AXIS2-5577:
Hi Yadong,
As long as you provide either https or http link to the same wsdl you will end
up getting same code.This is correct, You have to change the location of
binding part of your wsdl to get http and https binding accordingly.
wsdl:port name=VersionHttpSoap11Endpoint binding=ns:VersionSoap11Binding
soap:address
location=http://localhost:8080/axis2/services/Version.VersionHttpSoap11Endpoint//
/wsdl:port
Thanks,
Shameera.
axis2 caches the wsdl file when accessed by http or https
--
Key: AXIS2-5577
URL: https://issues.apache.org/jira/browse/AXIS2-5577
Project: Axis2
Issue Type: Bug
Environment: win7, jdk 1.7.09 axis2-1.6.2
Reporter: yadong
I used the following command to generate the client code for my webservice,
but I got the same code for http and https.
C:\share\axis2-1.6.2\binwsdl2java.bat -or --noBuildXML -p test.webservice -o
. -uri https://localhost:8080/axis2/services/Version?wsdl
C:\share\axis2-1.6.2\binwsdl2java.bat -or --noBuildXML -p test.webservice -o
. -uri http://localhost:8080/axis2/services/Version?wsdl
when I run the https:.?wsdl first,
the http:..?wsdl will get the same output stub java files.
and the address is as following(https??why,):
generated source file for http and https （they are the same
one） ---
/**
* Default Constructor
*/
public VersionStub(org.apache.axis2.context.ConfigurationContext
configurationContext) throws org.apache.axis2.AxisFault {
this(configurationContext,https://localhost:8443/axis2/services/Version.VersionHttpsSoap12Endpoint/;
);
}
/**
* Default Constructor
*/
public VersionStub() throws org.apache.axis2.AxisFault {
this(https://localhost:8443/axis2/services/Version.VersionHttpsSoap12Endpoint/;
);
}
- end of generated source file --
and I found that the wsdl file is the same one, when I used the https or http
to access the same web services's wsdl
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: Missing build.xml in Axis2-1.6.2 Source Distribution
], however it is not in my Source Distribution. Is there something incorrect with the release procedure that the build.xml is not included in the generated release artifact? I apologize in advance if I am missing something out here. Thanks Lewis [0] http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.6.2/README.txt [1] http://svn.apache.org/repos/asf/axis/axis2/java/core/tags/v1.6.2/build.xml -- Lewis -- Lewis -- *Lewis* -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
Re: svn commit: r1479332 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Yes, it is not a good idea to make changes which violate the Axis2 basic principals for the sake of user friendly messages.Actually I did above changes based on Specifications. But we need to address architectural issues when supporting the specifications. Thanks all for guiding me to the right direction. I have reverted the commit and moved changes to MessageReceiver level. New changes committed to the trunk and merged to 1.6.3 as well. I think it would be good to add these changes to ADB generated MessageRecievers too. Will work on that. Thanks, Shameera. On Mon, May 6, 2013 at 12:50 PM, Sagara Gunathunga sagara.gunathu...@gmail.com wrote: On Sun, May 5, 2013 at 8:52 PM, Deepal jayasinghe deep...@gmail.comwrote: On 5/5/2013 11:16 AM, Shameera Rathnayaka wrote: On Sun, May 5, 2013 at 8:32 PM, Deepal jayasinghe deep...@gmail.comwrote: Good point, if that is the cases then it violates the whole point of deferred building. Because we prefer to build the full message only at the MessageReceiver. At which point does this get called ? Soon after builder build the document. and before AxisEngine.receive(...) get called. If you do that, then we are going back to 'Axis1', one of the major design decisions of Axis2 was to build the SOAP message when absolutely necessary. For example build it at MR level. For that reason, I am sorry but I have to -1 this commit. If you investigate Axis2 JAX-WS performance issues one problem caused is it violated deferred building principle in several places and now it's hard to change the design. Providing user friendly messages is a good features but we can't loose our fundamental design principal for that I also think there should be a better way to improve error messages than early building message hence I also -1 for above commit. Thanks ! Deepal -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Commented] (AXIS2-5516) ReST request always returns blank response
[ https://issues.apache.org/jira/browse/AXIS2-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649285#comment-13649285 ] Shameera Rathnayaka commented on AXIS2-5516: Actually this is a bug, sever should return a descriptive fault message if message element is not in IRI style when using REST. I have fixed this( Revision 1479242) ReST request always returns blank response -- Key: AXIS2-5516 URL: https://issues.apache.org/jira/browse/AXIS2-5516 Project: Axis2 Issue Type: Bug Affects Versions: 1.6.1 Environment: Windows + IBM Rational Application Developer (RAD) + Websphere Application Server (WAS) 6.1; IBMi + WAS 6.1 Reporter: J. Allen Labels: rest, wsdl, xmlbeans Attachments: TestService-modified.wsdl, TestServiceSkeleton.java, TestService.wsdl A version 1.1 WSDL was created and the wsdl2java command run to generate code stubs. The WSDL has 1 operation - echo - to return the string in the request. The service class was implemented to return the request string. All ReST requests to the WSDL 1.1 web service return a blank response. SOAP requests work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5395) BigDecimal converted as double in ConverterUtil
[
https://issues.apache.org/jira/browse/AXIS2-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka updated AXIS2-5395:
---
Fix Version/s: 1.7.0
BigDecimal converted as double in ConverterUtil
---
Key: AXIS2-5395
URL: https://issues.apache.org/jira/browse/AXIS2-5395
Project: Axis2
Issue Type: Bug
Components: adb, databinding
Affects Versions: 1.6.1, 1.6.2
Environment: All
Reporter: serenne
Priority: Minor
Fix For: 1.7.0, 1.6.3
Big Decimal are treated as double in
org.apache.axis2.databinding.utils.converterUtil.java as no proto exists
taking a BigDecimal as argument.
This leads to loosing precision in the value in the xml content. We noticed
that since more than one year (as we use 14 digits for some currency change)
so, we use our own patched version :
in org.apache.axis2.databinding.utils.converterUtil.java add a new method :
public static String convertToString(BigDecimal o) {
return o.toPlainString();
}
This solved the problem. Could be enough, but we have to patch again the
Converterutil class at each update to the latest version
So if something like that could be introduced in next versions ... could be
nice !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5395) BigDecimal converted as double in ConverterUtil
[
https://issues.apache.org/jira/browse/AXIS2-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649292#comment-13649292
]
Shameera Rathnayaka commented on AXIS2-5395:
Merged r1343543 to 1.6 branch, (Revision 1479245)
BigDecimal converted as double in ConverterUtil
---
Key: AXIS2-5395
URL: https://issues.apache.org/jira/browse/AXIS2-5395
Project: Axis2
Issue Type: Bug
Components: adb, databinding
Affects Versions: 1.6.1, 1.6.2
Environment: All
Reporter: serenne
Priority: Minor
Fix For: 1.6.3
Big Decimal are treated as double in
org.apache.axis2.databinding.utils.converterUtil.java as no proto exists
taking a BigDecimal as argument.
This leads to loosing precision in the value in the xml content. We noticed
that since more than one year (as we use 14 digits for some currency change)
so, we use our own patched version :
in org.apache.axis2.databinding.utils.converterUtil.java add a new method :
public static String convertToString(BigDecimal o) {
return o.toPlainString();
}
This solved the problem. Could be enough, but we have to patch again the
Converterutil class at each update to the latest version
So if something like that could be introduced in next versions ... could be
nice !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Resolved] (AXIS2-5395) BigDecimal converted as double in ConverterUtil
[
https://issues.apache.org/jira/browse/AXIS2-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka resolved AXIS2-5395.
Resolution: Fixed
BigDecimal converted as double in ConverterUtil
---
Key: AXIS2-5395
URL: https://issues.apache.org/jira/browse/AXIS2-5395
Project: Axis2
Issue Type: Bug
Components: adb, databinding
Affects Versions: 1.6.1, 1.6.2
Environment: All
Reporter: serenne
Priority: Minor
Fix For: 1.7.0, 1.6.3
Big Decimal are treated as double in
org.apache.axis2.databinding.utils.converterUtil.java as no proto exists
taking a BigDecimal as argument.
This leads to loosing precision in the value in the xml content. We noticed
that since more than one year (as we use 14 digits for some currency change)
so, we use our own patched version :
in org.apache.axis2.databinding.utils.converterUtil.java add a new method :
public static String convertToString(BigDecimal o) {
return o.toPlainString();
}
This solved the problem. Could be enough, but we have to patch again the
Converterutil class at each update to the latest version
So if something like that could be introduced in next versions ... could be
nice !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5331) Handling BigDecimals data in ADB
[ https://issues.apache.org/jira/browse/AXIS2-5331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5331: --- Fix Version/s: 1.6.3 Handling BigDecimals data in ADB Key: AXIS2-5331 URL: https://issues.apache.org/jira/browse/AXIS2-5331 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.7.0 Environment: 1.7.0-SNAPSHOT JDK 1.6 Reporter: Denis Weerasiri Labels: patch Fix For: 1.7.0, 1.6.3 Attachments: AXIS2-5330-v1.patch I'm facing the same issue https://issues.apache.org/jira/browse/AXIS2-4036 in 1.7.0-SNAPSHOT. To be backward compatible axis2 adb need to use toPlainString() method provided by BigDecimal API. I have attached a patch with a test case to solve in adb. But what I more concerned is, whether axis2 need to handle serialization and de-serialization of BigDecimals in a configurable manner. Suppose, a java-adb-client need to manage his input and out data in scientific notation (in that case E-3 = 0.000), but axis2-adb always send 0.000. I feel, there should be a configurable way s.t. a client can choose to BigDecimal input/outputs in scientific notation or plain text notation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-4221) Axis2 should throw a meaningful fault if SOAP body is missing
[ https://issues.apache.org/jira/browse/AXIS2-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649303#comment-13649303 ] Shameera Rathnayaka commented on AXIS2-4221: According to the SOAP 1.1 and SOAP 1.2 specification SOAP body is mandatory element for SOAP envelop. Therefore we should validate the SOAP envelop against this and throw a fault message in builder level not in the RPCMessageReceiver. Therefore the patch provided me for this need to improve to that level. [1] http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383494 [2] http://www.w3.org/TR/2007/REC-soap12-part1-20070427/#soapenv Axis2 should throw a meaningful fault if SOAP body is missing - Key: AXIS2-4221 URL: https://issues.apache.org/jira/browse/AXIS2-4221 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.4.1 Reporter: Detelin Yordanov Assignee: Shameera Rathnayaka Attachments: MissingBodyRequestResponse.txt, MIssingBodyStacktrace.txt, trunk.patch Hi guys, Currently Axis2 does not check whether an incoming SOAP message contains a SOAP body (which is mandatory according to the spec). Axiom does not do it either and just returns null if body is missing (see SOAPEnvelope#getBody()). So in the case of missing body users receive a very uninformative fault: soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Receiver/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USunknown/soapenv:Text /soapenv:Reason soapenv:Detail / /soapenv:Fault I think this should be handled gracefully with an according error message message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: svn commit: r1479332 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Hi Deepal,
I have pointed out the relevant part of specs, Please have a look.
SOAP 1.1 -
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383494
SOAP 1.2 - http://www.w3.org/TR/2007/REC-soap12-part1-20070427/#soapenv
Regards,
Shameera.
On Sun, May 5, 2013 at 8:16 PM, Deepal Jayasinghe dee...@opensource.lkwrote:
Author: shameera
Date: Sun May 5 14:33:41 2013
New Revision: 1479332
URL: http://svn.apache.org/r1479332
Log:
Fixed AXIS2-4221, check for soap body after build soap envelop
Modified:
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Modified:
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
URL:
http://svn.apache.org/viewvc/axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java?rev=1479332r1=1479331r2=1479332view=diff
==
---
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
(original)
+++
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Sun May 5 14:33:41 2013
@@ -169,7 +169,7 @@ public class TransportUtils {
return createSOAPEnvelope(documentElement);
}
-public static SOAPEnvelope createSOAPEnvelope(OMElement
documentElement) {
+public static SOAPEnvelope createSOAPEnvelope(OMElement
documentElement) throws AxisFault {
SOAPEnvelope envelope;
// Check whether we have received a SOAPEnvelope or not
if (documentElement instanceof SOAPEnvelope) {
@@ -183,6 +183,10 @@ public class TransportUtils {
envelope.getBody().addChild(documentElement);
}
}
+//According to both SOAP 1.1 and 1.2 specification SOAP body is
mandatory element for a valid soap envelop
+if (envelope.getBody() == null) {
+throw new AxisFault(soap body element is null, but it is
mandatory for a valid soap envelop);
What do you mean by 'SOAP body element is null' ? did you mean to say it
is missing ?. And I am not 100% sure whether the SOAP body is mandatory
(need to read the spec :)).
Deepal
+}
return envelope;
}
--
Blog - http://blogs.deepal.org/
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
Re: svn commit: r1479332 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
On Sun, May 5, 2013 at 8:32 PM, Deepal jayasinghe deep...@gmail.com wrote:
Good point, if that is the cases then it violates the whole point of
deferred building. Because we prefer to build the full message only at
the MessageReceiver.
At which point does this get called ?
Soon after builder build the document. and before AxisEngine.receive(...)
get called.
Deepal
Normally (if the incoming message is a SOAP message), at the time this
method is called, only the SOAPEnvelope object has been instantiated
by Axiom. Calling SOAPEnvelope#getBody() will force Axiom to build the
entire SOAP header. I'm not sure it is desirable to do that at this
early stage. Probably it is better to do that check in the message
receivers (i.e. where the NullPointerException described in AXIS2-4221
occurs).
Ok, we have this disadvantage then, Implementation done base on we don't
need to
process invalid SOAP envelop. we have to choose which is the post
important. If the
existing features get affected by this changes, I too think bring this to
MessageReceiver.
would be a good solution.
Regards,
Shameera.
On Sun, May 5, 2013 at 4:33 PM, shame...@apache.org wrote:
Author: shameera
Date: Sun May 5 14:33:41 2013
New Revision: 1479332
URL: http://svn.apache.org/r1479332
Log:
Fixed AXIS2-4221, check for soap body after build soap envelop
Modified:
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Modified:
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
URL:
http://svn.apache.org/viewvc/axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java?rev=1479332r1=1479331r2=1479332view=diff
==
---
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
(original)
+++
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Sun May 5 14:33:41 2013
@@ -169,7 +169,7 @@ public class TransportUtils {
return createSOAPEnvelope(documentElement);
}
-public static SOAPEnvelope createSOAPEnvelope(OMElement
documentElement) {
+public static SOAPEnvelope createSOAPEnvelope(OMElement
documentElement) throws AxisFault {
SOAPEnvelope envelope;
// Check whether we have received a SOAPEnvelope or not
if (documentElement instanceof SOAPEnvelope) {
@@ -183,6 +183,10 @@ public class TransportUtils {
envelope.getBody().addChild(documentElement);
}
}
+//According to both SOAP 1.1 and 1.2 specification SOAP body
is mandatory element for a valid soap envelop
+if (envelope.getBody() == null) {
+throw new AxisFault(soap body element is null, but it is
mandatory for a valid soap envelop);
+}
return envelope;
}
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
Re: svn commit: r1479332 - /axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
On Sun, May 5, 2013 at 8:37 PM, Deepal jayasinghe deep...@gmail.com wrote:
Could you please change the message to be SOAP body is missing or
something and SOAP has to be upper case I guess.
sure, will shift the this check to MessageReceiver level and modify the
message.
Regards,
shameera.
Deepal
Hi Deepal,
I have pointed out the relevant part of specs, Please have a look.
SOAP 1.1 -
http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383494
SOAP 1.2 - http://www.w3.org/TR/2007/REC-soap12-part1-20070427/#soapenv
Regards,
Shameera.
On Sun, May 5, 2013 at 8:16 PM, Deepal Jayasinghe dee...@opensource.lkwrote:
Author: shameera
Date: Sun May 5 14:33:41 2013
New Revision: 1479332
URL: http://svn.apache.org/r1479332
Log:
Fixed AXIS2-4221, check for soap body after build soap envelop
Modified:
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Modified:
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
URL:
http://svn.apache.org/viewvc/axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java?rev=1479332r1=1479331r2=1479332view=diff
==
---
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
(original)
+++
axis/axis2/java/core/trunk/modules/kernel/src/org/apache/axis2/transport/TransportUtils.java
Sun May 5 14:33:41 2013
@@ -169,7 +169,7 @@ public class TransportUtils {
return createSOAPEnvelope(documentElement);
}
-public static SOAPEnvelope createSOAPEnvelope(OMElement
documentElement) {
+public static SOAPEnvelope createSOAPEnvelope(OMElement
documentElement) throws AxisFault {
SOAPEnvelope envelope;
// Check whether we have received a SOAPEnvelope or not
if (documentElement instanceof SOAPEnvelope) {
@@ -183,6 +183,10 @@ public class TransportUtils {
envelope.getBody().addChild(documentElement);
}
}
+//According to both SOAP 1.1 and 1.2 specification SOAP body
is mandatory element for a valid soap envelop
+if (envelope.getBody() == null) {
+throw new AxisFault(soap body element is null, but it is
mandatory for a valid soap envelop);
What do you mean by 'SOAP body element is null' ? did you mean to say it
is missing ?. And I am not 100% sure whether the SOAP body is mandatory
(need to read the spec :)).
Deepal
+}
return envelope;
}
--
Blog - http://blogs.deepal.org/
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
--
Best Regards,
Shameera Rathnayaka.
email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Resolved] (AXIS2-4221) Axis2 should throw a meaningful fault if SOAP body is missing
[ https://issues.apache.org/jira/browse/AXIS2-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka resolved AXIS2-4221. Resolution: Fixed Fix Version/s: 1.6.3 1.7.0 applied patch with few modifications(Revision 1479351) Axis2 should throw a meaningful fault if SOAP body is missing - Key: AXIS2-4221 URL: https://issues.apache.org/jira/browse/AXIS2-4221 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.4.1 Reporter: Detelin Yordanov Assignee: Shameera Rathnayaka Fix For: 1.7.0, 1.6.3 Attachments: MissingBodyRequestResponse.txt, MIssingBodyStacktrace.txt, trunk.patch Hi guys, Currently Axis2 does not check whether an incoming SOAP message contains a SOAP body (which is mandatory according to the spec). Axiom does not do it either and just returns null if body is missing (see SOAPEnvelope#getBody()). So in the case of missing body users receive a very uninformative fault: soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Receiver/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USunknown/soapenv:Text /soapenv:Reason soapenv:Detail / /soapenv:Fault I think this should be handled gracefully with an according error message message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5516) ReST request always returns blank response
[ https://issues.apache.org/jira/browse/AXIS2-5516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649112#comment-13649112 ] Shameera Rathnayaka commented on AXIS2-5516: Allen if you are going to use REST then your schema should adhere to IRI style [1] which is a part of wsdl2 definition. Axis2 XFromUrilEncoder try to build the message with IRI style, this is the default builder for Rest requests. If you are not comfortable with changing the schema then what you can do is write your custom builder. [1] http://www.w3.org/TR/2006/CR-wsdl20-adjuncts-20060327/#_operation_iri_style ReST request always returns blank response -- Key: AXIS2-5516 URL: https://issues.apache.org/jira/browse/AXIS2-5516 Project: Axis2 Issue Type: Bug Affects Versions: 1.6.1 Environment: Windows + IBM Rational Application Developer (RAD) + Websphere Application Server (WAS) 6.1; IBMi + WAS 6.1 Reporter: J. Allen Labels: rest, wsdl, xmlbeans Attachments: TestService-modified.wsdl, TestServiceSkeleton.java, TestService.wsdl A version 1.1 WSDL was created and the wsdl2java command run to generate code stubs. The WSDL has 1 operation - echo - to return the string in the request. The service class was implemented to return the request string. All ReST requests to the WSDL 1.1 web service return a blank response. SOAP requests work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Comment Edited] (AXIS2-5395) BigDecimal converted as double in ConverterUtil
[
https://issues.apache.org/jira/browse/AXIS2-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13649149#comment-13649149
]
Shameera Rathnayaka edited comment on AXIS2-5395 at 5/4/13 7:39 PM:
This has been fixed in trunk. AXIS2-5331
was (Author: shameera):
This has been fixed in trunk. AXIS2-5395
BigDecimal converted as double in ConverterUtil
---
Key: AXIS2-5395
URL: https://issues.apache.org/jira/browse/AXIS2-5395
Project: Axis2
Issue Type: Bug
Components: adb, databinding
Affects Versions: 1.6.1, 1.6.2
Environment: All
Reporter: serenne
Priority: Minor
Fix For: 1.6.3
Big Decimal are treated as double in
org.apache.axis2.databinding.utils.converterUtil.java as no proto exists
taking a BigDecimal as argument.
This leads to loosing precision in the value in the xml content. We noticed
that since more than one year (as we use 14 digits for some currency change)
so, we use our own patched version :
in org.apache.axis2.databinding.utils.converterUtil.java add a new method :
public static String convertToString(BigDecimal o) {
return o.toPlainString();
}
This solved the problem. Could be enough, but we have to patch again the
Converterutil class at each update to the latest version
So if something like that could be introduced in next versions ... could be
nice !
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5515) ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO.
Shameera Rathnayaka created AXIS2-5515: -- Summary: ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO. Key: AXIS2-5515 URL: https://issues.apache.org/jira/browse/AXIS2-5515 Project: Axis2 Issue Type: Improvement Components: kernel Affects Versions: 1.6.2, 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 Currently ObjectSupplier interface doesn't provide a way to instantiate Objects in runtime which doesn't has nullary constructor. it only define one method which takes only class object as method parameter. There is no way to instantiate a non POJO in runtime. Even we doesn't need to provide such a feature with DefaultObjectSupplier , it is good to provide a API to do that. Then user can provide their own implementation this. Adding new method(Object getObject(Class clazz , OMElement beanElement) throws AxisFault;) to ObjectSupplier would provide this. We don't need to implement this method in our DeafaultObjectSuppler. One use case for this is Java.util.UUID , this class doesn't has nullary constructor which only has UUID(long mostSigBits, long leastSigBits) , in such a case user can writer their own implementation of ObjectSupplier and use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5515) ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO.
[ https://issues.apache.org/jira/browse/AXIS2-5515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5515: --- Attachment: ObjectSupplier.patch Hi devs, I have attached fix for this. I have declare a method Object getObject(Class clazz , OMElement beanElement) throws AxisFault; to ObjectSupplier , DefaultObjectSupplier doesn't provide logic for this. And i have changed BeanUtil calss to process accrodingly. This patch will not change the default behavior. Thanks, Shameera. ObjectSuplier doesn't provide a way to instantiate object in runtime which is not a POJO. -- Key: AXIS2-5515 URL: https://issues.apache.org/jira/browse/AXIS2-5515 Project: Axis2 Issue Type: Improvement Components: kernel Affects Versions: 1.6.2, 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 Attachments: ObjectSupplier.patch Currently ObjectSupplier interface doesn't provide a way to instantiate Objects in runtime which doesn't has nullary constructor. it only define one method which takes only class object as method parameter. There is no way to instantiate a non POJO in runtime. Even we doesn't need to provide such a feature with DefaultObjectSupplier , it is good to provide a API to do that. Then user can provide their own implementation this. Adding new method(Object getObject(Class clazz , OMElement beanElement) throws AxisFault;) to ObjectSupplier would provide this. We don't need to implement this method in our DeafaultObjectSuppler. One use case for this is Java.util.UUID , this class doesn't has nullary constructor which only has UUID(long mostSigBits, long leastSigBits) , in such a case user can writer their own implementation of ObjectSupplier and use it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
ObjectSupplier Limited to create object instance with nullary Constructor.
Hi devs, According to my inspection, There is no way to create a new instance from a class, which hasn't nullary constructor by an ObjectSupplier. see the getObject method declaration. Object getObject(Class clazz) throws AxisFault; This is an limitation. adding anothe abstact method getObject(Class clazz , Class[] parameters , Object[] initargs) throw AxisFault; to ObjectSupplier would be the solution. DefaultObjectSupplier is the one and only concrete class of this interface.It will implement the logic. Other than that, If we see the services.xsd there is no way to define custom ObjectSuppliers in services.xml but in ServiceBuilder it check for ObjectSupplier in sevice discription this alway return null. String objectSupplierValue = (String) service .getParameterValue(TAG_OBJECT_SUPPLIER); we can define a new element for objectSupplier as last child of service element to fix this. If everyone ok with this , i will open an issue and proceed with this. Thanks, Shameera. -- Best Regards, Shameera Rathnayaka. email: shameera AT apache.org , shameerainfo AT gmail.com Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Updated] (AXIS2-5511) Missing close call on FileInputStream
[ https://issues.apache.org/jira/browse/AXIS2-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5511: --- Attachment: streamClose.patch For the prettify(OMElement , OutputStreanm) case , what we can do is wrap all method content to a try-catch block and if any Exception occure we close the OutputStream and throw new Exception(e) again. With this change truck get build with test without any failure. I have attached a patch for this. Dev please review and commit. Thanks, Shameera. Missing close call on FileInputStream - Key: AXIS2-5511 URL: https://issues.apache.org/jira/browse/AXIS2-5511 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.6.2 Reporter: Erik Vikström Priority: Trivial Attachments: streamClose.patch The prettify(File) method within org.apache.axis2.util.XMLPrettyPrinter creates a FileInputStream but does not close it explicitly. Hence XML files are locked for a while after this feature is being used; the stream is closed implicitly when the FileInputStream instance is garbage collected, but you never now when in time this happens. Since this class is used when running the code-generator, which we are using frequently within our application, this results in that we cannot tidy up files after this task has completed. Current workaround for us was to implement a custom Emitter and avoid running the XML pretty printing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5511) Missing close call on FileInputStream
[ https://issues.apache.org/jira/browse/AXIS2-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636186#comment-13636186 ] Shameera Rathnayaka commented on AXIS2-5511: Hi Erik, This has fixed in trunk, Instead of above line of code trunk has this, FileInputStream fin = new FileInputStream(file); byteArray = IOUtils.toByteArray(fin); fin.close(); Thanks, Shameera. Missing close call on FileInputStream - Key: AXIS2-5511 URL: https://issues.apache.org/jira/browse/AXIS2-5511 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.6.2 Reporter: Erik Vikström Priority: Trivial Attachments: streamClose.patch The prettify(File) method within org.apache.axis2.util.XMLPrettyPrinter creates a FileInputStream but does not close it explicitly. Hence XML files are locked for a while after this feature is being used; the stream is closed implicitly when the FileInputStream instance is garbage collected, but you never now when in time this happens. Since this class is used when running the code-generator, which we are using frequently within our application, this results in that we cannot tidy up files after this task has completed. Current workaround for us was to implement a custom Emitter and avoid running the XML pretty printing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5513) Decouple google-gson from JSON xml stream basae approach using JSR 353(Java api to JSON )processing)
Shameera Rathnayaka created AXIS2-5513: -- Summary: Decouple google-gson from JSON xml stream basae approach using JSR 353(Java api to JSON )processing) Key: AXIS2-5513 URL: https://issues.apache.org/jira/browse/AXIS2-5513 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 Currently newly added JSON XML Stream API base approach, tightly couple with google-gson. Decoupling google-gson from this would make more extensible to use other JSON Stream APIs(like Jakson). Here we can use factory method pattern to create JSON XMLStreamReaders/writers . And we can provide an api(this will be JSR 353-Java API for JSON processing) to implement Gson, Jakson or any other Json Stream support api to write the logic under that. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
Re: Decouple Gson from XML Stream API base JSON approach
Hi devs, I created a JIRA issue[1] for this. And start working on this. Thanks, Shameera. [1] https://issues.apache.org/jira/browse/AXIS2-5513 On Wed, Apr 17, 2013 at 12:04 AM, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi devs, Can i assume nobody has problem with this procedure and ok with using JSR 353 for this implementations? If so i would like to open a new JIRA issue for this and working on this. Regards, Shameera. On Sun, Apr 7, 2013 at 9:37 PM, Shameera Rathnayaka shameerai...@gmail.com wrote: On Sun, Apr 7, 2013 at 12:48 PM, Sagara Gunathunga sagara.gunathu...@gmail.com wrote: On Sat, Apr 6, 2013 at 1:23 PM, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi devs, Currently newly added JSON XML Stream API base approach in trunk, tightly couple with google-gson. I think it is good to have flexibility to use other JSON Stream APIs(like Jakson) with this. Good point but IMHO we should use JSR 353 (Java API for JSON processing ) which being more or less finalized by now for above task. +1 , Yes that would be good to use standard API, Regards, Shameera. [1] - http://jcp.org/en/jsr/detail?id=353 Thanks ! Here we can use factory method pattern to create JSON XMLStreamReaders/writers . And we can provide an api to implement Gson, Jakson or any other Json Stream support api to write the logic under that. we can provide Factory classes to create JSONXMLStreamReaders/Writers with Gson or Jakson or other. Thoughts are welcome. -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/ -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/ -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/ -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Commented] (AXIS2-5511) Missing close call on FileInputStream
[
https://issues.apache.org/jira/browse/AXIS2-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635388#comment-13635388
]
Shameera Rathnayaka commented on AXIS2-5511:
Hi Erik,
I am not sure whether you have mistakenly put affecte version as 1.6.2, I
checked this with 1.6.2 and see try{}catch{}finallly{} blocks are there and
finally block close both input and output streams.
Thanks,
Shameera.
Missing close call on FileInputStream
-
Key: AXIS2-5511
URL: https://issues.apache.org/jira/browse/AXIS2-5511
Project: Axis2
Issue Type: Bug
Components: kernel
Affects Versions: 1.6.2
Reporter: Erik Vikström
Priority: Trivial
The prettify(File) method within org.apache.axis2.util.XMLPrettyPrinter
creates a FileInputStream but does not close it explicitly. Hence XML files
are locked for a while after this feature is being used; the stream is closed
implicitly when the FileInputStream instance is garbage collected, but you
never now when in time this happens.
Since this class is used when running the code-generator, which we are using
frequently within our application, this results in that we cannot tidy up
files after this task has completed.
Current workaround for us was to implement a custom Emitter and avoid running
the XML pretty printing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5458) ConverterTool date conversion without timezone returns Date with day before before 1901
[
https://issues.apache.org/jira/browse/AXIS2-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634031#comment-13634031
]
Shameera Rathnayaka commented on AXIS2-5458:
Hi Manuel,
Could you explain bit more about the issue and provide a small sample which is
enough to reproduce this.
Thanks,
Shameera.
ConverterTool date conversion without timezone returns Date with day before
before 1901
---
Key: AXIS2-5458
URL: https://issues.apache.org/jira/browse/AXIS2-5458
Project: Axis2
Issue Type: Bug
Components: adb
Affects Versions: 1.5.4, 1.6.2
Environment: Diverse linux (at least)
Reporter: Manuel Gallego
GIVEN ConverterUtil.convertToDate(1940-01-01)
THEN resulting date is one day before at 23:00
GIVEN ConverterUtil.convertToDate(1900-01-01Z)
THEN resulting date is one day before at 23:00
-
Test that reproduce the issue:
@Test
public void testCustomConvertToDateTimeZone() {
for (int year = 2012; year 1800; year--) {
for (int month = 12; month 0; month--) {
Date date =
ConverterUtil.convertToDate(createFormattedDate(year, month, 1, ));
assertParsedDateFieldsEquals(year, month, 1,
date);
}
}
}
public void assertParsedDateFieldsEquals(int year, int month, int day,
Date date) {
Assert.assertNotNull(date);
Calendar calendar = Calendar.getInstance();
calendar.setTime(date);
String message = failed conversion +
createFormattedDate(year, month, day) + not equals + date;
Assert.assertEquals(message, year, calendar.get(Calendar.YEAR));
Assert.assertEquals(message, month,
calendar.get(Calendar.MONTH) + 1);
Assert.assertEquals(message, day,
calendar.get(Calendar.DAY_OF_MONTH));
}
public String createFormattedDate(int year, int month, int day, String
suffix) {
return new DecimalFormat().format(year) + - + new
DecimalFormat(00).format(month) + - + new DecimalFormat(00).format(day)
+ suffix;
}
---
The following implementation solves this issue. I'm not 100% sure it works in
all other cases.
Essentially I'm setting the timezone offset for the particular date because
of the historical information that TimeZone may contain..
Another problem I found is that I could not find a way to override the static
method so I had to manually change the wsdl2java generated code.
/**
* Converts a given string into a date. Code from Axis1
DateDeserializer.
*
* @param source
* @return Returns Date.
*/
public static Date convertToDate(String source) {
// the lexical form of the date is '-'? '-' mm '-' dd
zz?
if ((source == null) || source.trim().equals()) {
return null;
}
source = source.trim();
boolean bc = false;
if (source.startsWith(-)) {
source = source.substring(1);
bc = true;
}
int year = 0;
int month = 0;
int day = 0;
Integer timeZoneOffSet = null;
if (source.length() = 10) {
// first 10 numbers must give the year
if ((source.charAt(4) != '-') || (source.charAt(7) !=
'-')) {
throw new RuntimeException(invalid date format
( + source + ) with out - s at correct place );
}
year = Integer.parseInt(source.substring(0, 4));
month = Integer.parseInt(source.substring(5, 7));
day = Integer.parseInt(source.substring(8, 10));
if (source.length() 10) {
String restpart = source.substring(10);
if (restpart.startsWith(Z)) {
// this is a gmt time zone value
timeZoneOffSet = 0;
} else if (restpart.startsWith(+) ||
restpart.startsWith(-) || restpart.startsWith(T)) {
// this is a specific time format string
if (restpart.charAt(3) != ':') {
throw new
Re: Decouple Gson from XML Stream API base JSON approach
On Sun, Apr 7, 2013 at 12:48 PM, Sagara Gunathunga sagara.gunathu...@gmail.com wrote: On Sat, Apr 6, 2013 at 1:23 PM, Shameera Rathnayaka shameerai...@gmail.com wrote: Hi devs, Currently newly added JSON XML Stream API base approach in trunk, tightly couple with google-gson. I think it is good to have flexibility to use other JSON Stream APIs(like Jakson) with this. Good point but IMHO we should use JSR 353 (Java API for JSON processing ) which being more or less finalized by now for above task. +1 , Yes that would be good to use standard API, Regards, Shameera. [1] - http://jcp.org/en/jsr/detail?id=353 Thanks ! Here we can use factory method pattern to create JSON XMLStreamReaders/writers . And we can provide an api to implement Gson, Jakson or any other Json Stream support api to write the logic under that. we can provide Factory classes to create JSONXMLStreamReaders/Writers with Gson or Jakson or other. Thoughts are welcome. -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/ -- Sagara Gunathunga Blog - http://ssagara.blogspot.com Web - http://people.apache.org/~sagara/ LinkedIn - http://www.linkedin.com/in/ssagara -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/
Decouple Gson from XML Stream API base JSON approach
Hi devs, Currently newly added JSON XML Stream API base approach in trunk, tightly couple with google-gson. I think it is good to have flexibility to use other JSON Stream APIs(like Jakson) with this. Here we can use factory method pattern to create JSON XMLStreamReaders/writers . And we can provide an api to implement Gson, Jakson or any other Json Stream support api to write the logic under that. we can provide Factory classes to create JSONXMLStreamReaders/Writers with Gson or Jakson or other. Thoughts are welcome. -- Best Regards, Shameera Rathnayaka. Blog : http://shameerarathnayaka.blogspot.com/
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: regen_jsonRPCIntegration.patch Hi Amila , I have attached a new patch file (regen_jsonRPCIntegration.patch) , Seems previous patch has some error in moving JsonUtil class.Sorry for the inconvenience, Thanks, Shameera. Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: cobertura.png, json_rpc_integration_test.patch, json_rpc_test.patch, Jsontest.patch, missingSchema.patch, regen_jsonRPCIntegration.patch, TestTermination.patch, XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: regen_jsonRPCIntegration.patch Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: cobertura.png, json_rpc_integration_test.patch, json_rpc_test.patch, Jsontest.patch, missingSchema.patch, regen_jsonRPCIntegration.patch, TestTermination.patch, XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: (was: regen_jsonRPCIntegration.patch) Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: cobertura.png, json_rpc_integration_test.patch, json_rpc_test.patch, Jsontest.patch, missingSchema.patch, regen_jsonRPCIntegration.patch, TestTermination.patch, XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: json_rpc_test.patch Hi Amila, I have updated my patch as you feedback and i move org.apache.asix2.json.gson.fartory.JsonUtils class to org.apache.axis2.json.gson.rpc package as only classes in org.apache.axis2.json.gson.rpc use that. Please review and apply. Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: cobertura.png, json_rpc_test.patch, Jsontest.patch, missingSchema.patch, TestTermination.patch, XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-5461) Syntax error in ADBBeanTemplate-bean.xsl
[ https://issues.apache.org/jira/browse/AXIS2-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka reassigned AXIS2-5461: -- Assignee: Shameera Rathnayaka Syntax error in ADBBeanTemplate-bean.xsl Key: AXIS2-5461 URL: https://issues.apache.org/jira/browse/AXIS2-5461 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.7.0 Reporter: Lionel Meroni Assignee: Shameera Rathnayaka Priority: Critical Attachments: datamodel.xsd, MyOperations.wsdl, WSDL2JavaOptions.txt Original Estimate: 10m Remaining Estimate: 10m In the xsl file ADBBeanTemplate-bean.xsl, there is an error at line 481 : throw new java.lang.RuntimeException(Input values do not follow defined XSD restrictions/); The string / has nothing to do here and generate compil error in java. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5427) POJO services with Parameters/return types like ListInteger not working
[
https://issues.apache.org/jira/browse/AXIS2-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka updated AXIS2-5427:
---
Attachment: WrappedGenericListTest.patch
I have added a new patch which has test cases to cover generic wrapper type
list. Please review and commit
POJO services with Parameters/return types like ListInteger not working
-
Key: AXIS2-5427
URL: https://issues.apache.org/jira/browse/AXIS2-5427
Project: Axis2
Issue Type: Bug
Affects Versions: 1.7.0
Reporter: Prabhath Suminda
Assignee: Shameera Rathnayaka
Priority: Blocker
Attachments: List_Integer.zip, Test-1.aar, WrappedGenericList.patch,
WrappedGenericListTest.patch
I developed a simple service which has following service class,
package Test;
import java.util.*;
public class SimpleService {
public ListInteger helloService(ListInteger s){
return s;
}
}
When I deployed this as a AAR file and send following request
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:test=http://Test;
soapenv:Header/
soapenv:Body
test:helloService
!--1 or more repetitions:--
test:s6/test:s
test:s6/test:s
test:s6/test:s
/test:helloService
/soapenv:Body
/soapenv:Envelope
It gives me following response which is wrong,
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
ns:helloServiceResponse xmlns:ns=http://Test;
ns:return xsi:type=axis2ns1:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
ns:return xsi:type=axis2ns2:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
ns:return xsi:type=axis2ns3:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
/ns:helloServiceResponse
/soapenv:Body
/soapenv:Envelope
But this works when type is ListString. I attached the aar file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5427) POJO services with Parameters/return types like ListInteger not working
[
https://issues.apache.org/jira/browse/AXIS2-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka updated AXIS2-5427:
---
Attachment: WrappedGenericList.patch
Not only the ListInteger, all LIstX where X is Long, Double ,Short,
Character or Float are not working with current trunk. I have attached a patch
to fix all of this cases.
Thanks, Shameera.
POJO services with Parameters/return types like ListInteger not working
-
Key: AXIS2-5427
URL: https://issues.apache.org/jira/browse/AXIS2-5427
Project: Axis2
Issue Type: Bug
Affects Versions: 1.7.0
Reporter: Prabhath Suminda
Priority: Blocker
Attachments: List_Integer.zip, Test-1.aar, WrappedGenericList.patch
I developed a simple service which has following service class,
package Test;
import java.util.*;
public class SimpleService {
public ListInteger helloService(ListInteger s){
return s;
}
}
When I deployed this as a AAR file and send following request
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:test=http://Test;
soapenv:Header/
soapenv:Body
test:helloService
!--1 or more repetitions:--
test:s6/test:s
test:s6/test:s
test:s6/test:s
/test:helloService
/soapenv:Body
/soapenv:Envelope
It gives me following response which is wrong,
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
ns:helloServiceResponse xmlns:ns=http://Test;
ns:return xsi:type=axis2ns1:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
ns:return xsi:type=axis2ns2:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
ns:return xsi:type=axis2ns3:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
/ns:helloServiceResponse
/soapenv:Body
/soapenv:Envelope
But this works when type is ListString. I attached the aar file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-5427) POJO services with Parameters/return types like ListInteger not working
[
https://issues.apache.org/jira/browse/AXIS2-5427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shameera Rathnayaka reassigned AXIS2-5427:
--
Assignee: Shameera Rathnayaka
POJO services with Parameters/return types like ListInteger not working
-
Key: AXIS2-5427
URL: https://issues.apache.org/jira/browse/AXIS2-5427
Project: Axis2
Issue Type: Bug
Affects Versions: 1.7.0
Reporter: Prabhath Suminda
Assignee: Shameera Rathnayaka
Priority: Blocker
Attachments: List_Integer.zip, Test-1.aar, WrappedGenericList.patch
I developed a simple service which has following service class,
package Test;
import java.util.*;
public class SimpleService {
public ListInteger helloService(ListInteger s){
return s;
}
}
When I deployed this as a AAR file and send following request
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:test=http://Test;
soapenv:Header/
soapenv:Body
test:helloService
!--1 or more repetitions:--
test:s6/test:s
test:s6/test:s
test:s6/test:s
/test:helloService
/soapenv:Body
/soapenv:Envelope
It gives me following response which is wrong,
soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
soapenv:Body
ns:helloServiceResponse xmlns:ns=http://Test;
ns:return xsi:type=axis2ns1:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
ns:return xsi:type=axis2ns2:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
ns:return xsi:type=axis2ns3:int
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance/
/ns:helloServiceResponse
/soapenv:Body
/soapenv:Envelope
But this works when type is ListString. I attached the aar file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5435) Axis2 BeanUtil doesn't appear to support is/has getter forms for fields.
[ https://issues.apache.org/jira/browse/AXIS2-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492489#comment-13492489 ] Shameera Rathnayaka commented on AXIS2-5435: Hi Thomas/dev, I dig this and found that when we get the BeanInfo class for above pojo class it always expect setters and getters for all types but boolean primitive. So this is not an issue of Axis2 , but we can solve this if setXXX method has referent type as java.lang.Boolean then check whether Beanclass has isXXX method where it return type is java.lang.Boolean . If devs are ok with this, i can provide a patch WDYT?. But i think it is good to keep this as it is because we can stick to the java reflection standards. Thanks, Shameera. Axis2 BeanUtil doesn't appear to support is/has getter forms for fields. - Key: AXIS2-5435 URL: https://issues.apache.org/jira/browse/AXIS2-5435 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.6.2 Environment: Windows 7 64. Java 1.7 Reporter: Thomas Valine Labels: adb, databinding Binding POJO's having boolean getter methods of the form isBool, hasBool doesn't appear to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Assigned] (AXIS2-4221) Axis2 should throw a meaningful fault if SOAP body is missing
[ https://issues.apache.org/jira/browse/AXIS2-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka reassigned AXIS2-4221: -- Assignee: Shameera Rathnayaka Axis2 should throw a meaningful fault if SOAP body is missing - Key: AXIS2-4221 URL: https://issues.apache.org/jira/browse/AXIS2-4221 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.4.1 Reporter: Detelin Yordanov Assignee: Shameera Rathnayaka Attachments: MissingBodyRequestResponse.txt, MIssingBodyStacktrace.txt Hi guys, Currently Axis2 does not check whether an incoming SOAP message contains a SOAP body (which is mandatory according to the spec). Axiom does not do it either and just returns null if body is missing (see SOAPEnvelope#getBody()). So in the case of missing body users receive a very uninformative fault: soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Receiver/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USunknown/soapenv:Text /soapenv:Reason soapenv:Detail / /soapenv:Fault I think this should be handled gracefully with an according error message message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-4221) Axis2 should throw a meaningful fault if SOAP body is missing
[ https://issues.apache.org/jira/browse/AXIS2-4221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-4221: --- Attachment: trunk.patch Hi devs, I have fixed this for current trunk. please review and commit. If it is required i can provide patches for previous versions too. Thanks, Shameera. Axis2 should throw a meaningful fault if SOAP body is missing - Key: AXIS2-4221 URL: https://issues.apache.org/jira/browse/AXIS2-4221 Project: Axis2 Issue Type: Bug Components: kernel Affects Versions: 1.4.1 Reporter: Detelin Yordanov Assignee: Shameera Rathnayaka Attachments: MissingBodyRequestResponse.txt, MIssingBodyStacktrace.txt, trunk.patch Hi guys, Currently Axis2 does not check whether an incoming SOAP message contains a SOAP body (which is mandatory according to the spec). Axiom does not do it either and just returns null if body is missing (see SOAPEnvelope#getBody()). So in the case of missing body users receive a very uninformative fault: soapenv:Fault soapenv:Code soapenv:Valuesoapenv:Receiver/soapenv:Value /soapenv:Code soapenv:Reason soapenv:Text xml:lang=en-USunknown/soapenv:Text /soapenv:Reason soapenv:Detail / /soapenv:Fault I think this should be handled gracefully with an according error message message. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: missingSchema.patch Hi devs, With above jsontest.patch you will get file not found exception in JSONMessageHandler test as mistakenly i haven't add a schema file to the patch. Here i am attaching that. Sorry for any inconvenience. Shameera. Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: Jsontest.patch, missingSchema.patch, XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5440) Tomcat using 100% CPU when application/json (JSONMessageFormatter) is used
[
https://issues.apache.org/jira/browse/AXIS2-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485587#comment-13485587
]
Shameera Rathnayaka commented on AXIS2-5440:
Hi Ladislav,
If it sends GET request then fine.
Here I am referring to your sample code, First does the getAgent works with
application/json ? if not according to your sample jquery client when it sent
listagent request it send empty JSON message( { } ) which cause to
infinite-loop(AXIS2-5125) . Could you please try this with current trunk?
because this is fixed with it.
Thanks,
Shameera.
Tomcat using 100% CPU when application/json (JSONMessageFormatter) is used
--
Key: AXIS2-5440
URL: https://issues.apache.org/jira/browse/AXIS2-5440
Project: Axis2
Issue Type: Bug
Affects Versions: 1.6.0, 1.6.2
Environment: Apache Tomcat/6.0.35 1.6.0_21-b07Sun
Microsystems Inc. Windows 7 6.1 x86
Reporter: Ladislav Lencucha
Labels: JSON
Attachments: axis2.xml, ConsoleServer.aar, ws.zip
I am trying to connect to my webservice using GET + JSON.
I've added JSONMessageFormatter and JSONOMBuilder for application/json
content type.
When I try to call the webservice using jQuery and HTTP GET with content type
application/xml I receive the response almost immediately (note that there
is a jQuery error raised afterwards, because Xml cannot be parsed as JSON).
When I try to call the webservice using the same code but with content type
application/json there is no response and Tomcat uses 100% of CPU (there
are also some messages in log file mentioning that it should have ended).
See my aar file and jQuery example attached. Also see my axis2.xml
configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Comment Edited] (AXIS2-5422) org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
[ https://issues.apache.org/jira/browse/AXIS2-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475024#comment-13475024 ] Shameera Rathnayaka edited comment on AXIS2-5422 at 10/12/12 2:40 PM: -- Hi did you provide globalcentralservices.xsd file with the above wsdl ? both file should be placed same direcotry. was (Author: shameera): Hi did you provided globalcentralservices.xsd file with the above wsdl ? both file should be placed same direcotry. org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL -- Key: AXIS2-5422 URL: https://issues.apache.org/jira/browse/AXIS2-5422 Project: Axis2 Issue Type: Wish Components: codegen, databinding Affects Versions: 1.4.1 Reporter: Maria Rosa Jordán Priority: Critical Hello I'm trying to compile with Ant a project and I have this error E:\dev\apps\workspace\GlobalCentralServices\bin\build.xml:60: org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL. Here below ther is my WSDL file: ?xml version=1.0 encoding=UTF-8? definitions name=GCS targetNamespace=http://www.axa.com/GCS; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:tns=http://www.axa.com/GCS; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:gcs=http://www.axa.com/schemas/GCS; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:wsa=http://www.w3.org/2005/08/addressing; types xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; xsd:import namespace=http://www.axa.com/schemas/GCS; schemaLocation=globalcentralservices.xsd/ /xsd:schema xsd:schema xsd:import namespace=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; schemaLocation=oasis-200401-wss-wssecurity-secext-1.0.xsd/ /xsd:schema /types message name=AuthenticateRequest part name=header element=wsse:Security/ part name=body element=gcs:AuthenticateRequest/ /message message name=AuthenticateResponse part name=header element=wsse:Security/ part name=body element=gcs:AuthenticateResponse/ /message message name=AuthorizeRequest part name=header element=wsse:Security/ part name=body element=gcs:AuthorizeRequest/ /message message name=AuthorizeResponse part name=header element=wsse:Security/ part name=body element=gcs:AuthorizeResponse/ /message message name=ChangePasswordRequest part name=header element=wsse:Security/ part name=body element=gcs:ChangePasswordRequest/ /message message name=ChangePasswordResponse part name=header element=wsse:Security/ part name=body element=gcs:ChangePasswordResponse/ /message message name=CreateAccountRequest part name=header element=wsse:Security/ part name=body element=gcs:CreateAccountRequest/ /message message name=CreateAccountResponse part name=header element=wsse:Security/ part name=body element=gcs:CreateAccountResponse/ /message message name=GCSFault part name=fault element=gcs:GCSFault / /message message name=GetAccountRequest part name=header element=wsse:Security/ part name=body element=gcs:GetAccountRequest/ /message message name=GetAccountResponse part name=header element=wsse:Security/ part name=body element=gcs:GetAccountResponse/ /message message name=GetProposalIdRequest part name=header element=wsse:Security/ part name=body element=gcs:GetProposalIdRequest/ /message message name=GetProposalIdResponse part name=header element=wsse:Security/ part name=body element=gcs:GetProposalIdResponse/ /message message name=GetUserSecretRequest part name=header element=wsse:Security/ part name=body element=gcs:GetUserSecretRequest/ /message message name=GetUserSecretResponse part name=header element=wsse:Security/ part name=body element=gcs:GetUserSecretResponse/ /message message name=IsTokenValidRequest part name=header element=wsse:Security/ part name=body element=gcs:IsTokenValidRequest/ /message message name=IsTokenValidResponse part name=header element=wsse:Security/ part name=body element=gcs:IsTokenValidResponse
[jira] [Commented] (AXIS2-5422) org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
[ https://issues.apache.org/jira/browse/AXIS2-5422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475024#comment-13475024 ] Shameera Rathnayaka commented on AXIS2-5422: Hi did you provided globalcentralservices.xsd file with the above wsdl ? both file should be placed same direcotry. org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL -- Key: AXIS2-5422 URL: https://issues.apache.org/jira/browse/AXIS2-5422 Project: Axis2 Issue Type: Wish Components: codegen, databinding Affects Versions: 1.4.1 Reporter: Maria Rosa Jordán Priority: Critical Hello I'm trying to compile with Ant a project and I have this error E:\dev\apps\workspace\GlobalCentralServices\bin\build.xml:60: org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL. Here below ther is my WSDL file: ?xml version=1.0 encoding=UTF-8? definitions name=GCS targetNamespace=http://www.axa.com/GCS; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:tns=http://www.axa.com/GCS; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:gcs=http://www.axa.com/schemas/GCS; xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; xmlns:wsa=http://www.w3.org/2005/08/addressing; types xsd:schema xmlns:xsd=http://www.w3.org/2001/XMLSchema; xsd:import namespace=http://www.axa.com/schemas/GCS; schemaLocation=globalcentralservices.xsd/ /xsd:schema xsd:schema xsd:import namespace=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; schemaLocation=oasis-200401-wss-wssecurity-secext-1.0.xsd/ /xsd:schema /types message name=AuthenticateRequest part name=header element=wsse:Security/ part name=body element=gcs:AuthenticateRequest/ /message message name=AuthenticateResponse part name=header element=wsse:Security/ part name=body element=gcs:AuthenticateResponse/ /message message name=AuthorizeRequest part name=header element=wsse:Security/ part name=body element=gcs:AuthorizeRequest/ /message message name=AuthorizeResponse part name=header element=wsse:Security/ part name=body element=gcs:AuthorizeResponse/ /message message name=ChangePasswordRequest part name=header element=wsse:Security/ part name=body element=gcs:ChangePasswordRequest/ /message message name=ChangePasswordResponse part name=header element=wsse:Security/ part name=body element=gcs:ChangePasswordResponse/ /message message name=CreateAccountRequest part name=header element=wsse:Security/ part name=body element=gcs:CreateAccountRequest/ /message message name=CreateAccountResponse part name=header element=wsse:Security/ part name=body element=gcs:CreateAccountResponse/ /message message name=GCSFault part name=fault element=gcs:GCSFault / /message message name=GetAccountRequest part name=header element=wsse:Security/ part name=body element=gcs:GetAccountRequest/ /message message name=GetAccountResponse part name=header element=wsse:Security/ part name=body element=gcs:GetAccountResponse/ /message message name=GetProposalIdRequest part name=header element=wsse:Security/ part name=body element=gcs:GetProposalIdRequest/ /message message name=GetProposalIdResponse part name=header element=wsse:Security/ part name=body element=gcs:GetProposalIdResponse/ /message message name=GetUserSecretRequest part name=header element=wsse:Security/ part name=body element=gcs:GetUserSecretRequest/ /message message name=GetUserSecretResponse part name=header element=wsse:Security/ part name=body element=gcs:GetUserSecretResponse/ /message message name=IsTokenValidRequest part name=header element=wsse:Security/ part name=body element=gcs:IsTokenValidRequest/ /message message name=IsTokenValidResponse part name=header element=wsse:Security/ part name=body element=gcs:IsTokenValidResponse/ /message message name=IsUserSecretValidRequest part name=header element=wsse:Security/ part name=body element=gcs:IsUserSecretValidRequest/ /message message name=IsUserSecretValidResponse
[jira] [Commented] (AXIS2-5435) Axis2 BeanUtil doesn't appear to support is/has getter forms for fields.
[ https://issues.apache.org/jira/browse/AXIS2-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474219#comment-13474219 ] Shameera Rathnayaka commented on AXIS2-5435: Hi Thomas, Could you please explain the problem little bit or provide a small sample to regenerate this. Thanks, Shameera. Axis2 BeanUtil doesn't appear to support is/has getter forms for fields. - Key: AXIS2-5435 URL: https://issues.apache.org/jira/browse/AXIS2-5435 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.6.2 Environment: Windows 7 64. Java 1.7 Reporter: Thomas Valine Labels: adb, databinding Binding POJO's having boolean getter methods of the form isBool, hasBool doesn't appear to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5430) How to remove mustUnderstand attribute from SOAP Header
[ https://issues.apache.org/jira/browse/AXIS2-5430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474241#comment-13474241 ] Shameera Rathnayaka commented on AXIS2-5430: Hi Santhosh, This is not an issue at all , So I think better place to ask this is user mailing list :) . Thanks, Shameera. How to remove mustUnderstand attribute from SOAP Header - Key: AXIS2-5430 URL: https://issues.apache.org/jira/browse/AXIS2-5430 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.6.1 Environment: HP Tandem Reporter: Santhosh Labels: mustUnderstand Original Estimate: 193h Remaining Estimate: 193h HI All, can someone help me in removing the mustUnderstand attribute from SOAP header as it is causing a failure while sending the request to servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5435) Axis2 BeanUtil doesn't appear to support is/has getter forms for fields.
[ https://issues.apache.org/jira/browse/AXIS2-5435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13474307#comment-13474307 ] Shameera Rathnayaka commented on AXIS2-5435: HI Thomas, I checked with private Boolean bar; here if we add isBar() method to get the bar(which is a wrapper object not a primitive boolean type) at compile time it is ok. But when we deploy this under the Axis2, it is throw an exception while try to generate the schema for that particular service. Therefore even you drop .aar file to repository/services directory it is not available in service EPR due to this deployment error. But if you use private boolean bar; there is no any exception throws at deployement time so you get the service expose in service EPR. Thanks, Shameera. Axis2 BeanUtil doesn't appear to support is/has getter forms for fields. - Key: AXIS2-5435 URL: https://issues.apache.org/jira/browse/AXIS2-5435 Project: Axis2 Issue Type: Bug Components: adb Affects Versions: 1.6.2 Environment: Windows 7 64. Java 1.7 Reporter: Thomas Valine Labels: adb, databinding Binding POJO's having boolean getter methods of the form isBool, hasBool doesn't appear to work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Summary: Integration test for JSON XML Stream API base approach with ADB skeleton (was: Sample which demostarte how to use XML Stream API base approach with ADB generated skeleton) Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Integration test for JSON XML Stream API base approach with ADB skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: Jsontest.patch Hi devs/ Andreas , Here i have attach patch with, an integration test for JSON XMLStreamAPI , and two isolation tests for XMLNodeGenerator and JSONMessageHandler . Please review and apply Thanks, Shameera Integration test for JSON XML Stream API base approach with ADB skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: Jsontest.patch, XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
[ https://issues.apache.org/jira/browse/AXIS2-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13465872#comment-13465872 ] Shameera Rathnayaka commented on AXIS2-5416: According to the Andreas explanation, I have submitted a new patch for AXIS2-5417 which has an integration test(end-to-end test) for JSON XMLStreamAPI approach and two test classes for XMLNodeGenerator and JSONMessageHandler to cover main functionalities of those classes. Thanks Shameera. Add Native approach and XML Stream API base approach Documentations --- Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: Documentation, json Fix For: 1.7.0 Attachments: JSONDucumentation.patch Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
[ https://issues.apache.org/jira/browse/AXIS2-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13453273#comment-13453273 ] Shameera Rathnayaka commented on AXIS2-5416: Hi dev/Andreas, I think sample is a good description for the users, it explain clearly how to use XML Stream API base approach. Yes there is no any test coverage for few classes. I am working on it and i have already written test cases for JSONMessageHandler and XMLNodeGenerator to cover all functionalities.But when I try to write a test case for JsonRPCMessageReceiver, I couldn't find a way to set ConfigurationContext of ServiceContext. Because it is used to get the service object. As i can see there are only two methods which set ConfigurationContext of the ServiceContext, readExternal(ObjectInput in) and a constructor, which is only accessible within that package. Unfortunately other messageReceivers don't have any test coverage therefore i don't have any code segment to refer. Can somebody help me on this case. Thanks, Shameera. Add Native approach and XML Stream API base approach Documentations --- Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: Documentation, json Fix For: 1.7.0 Attachments: JSONDucumentation.patch Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5417) Sample which demostarte how to use XML Stream API base approach with ADB generated skeleton
Shameera Rathnayaka created AXIS2-5417: -- Summary: Sample which demostarte how to use XML Stream API base approach with ADB generated skeleton Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5417) Sample which demostarte how to use XML Stream API base approach with ADB generated skeleton
[ https://issues.apache.org/jira/browse/AXIS2-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5417: --- Attachment: XML_Stream_API_base_sample.patch Hi devs, I have attached a patch for this, Please review and apply. Thanks, Shameera. Sample which demostarte how to use XML Stream API base approach with ADB generated skeleton --- Key: AXIS2-5417 URL: https://issues.apache.org/jira/browse/AXIS2-5417 Project: Axis2 Issue Type: Task Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: json, sample Fix For: 1.7.0 Attachments: XML_Stream_API_base_sample.patch With new JSON support improvement, Axis2 users can use pure JSON requests to call ADB generated services. Here it uses XML Stream API base approach which was introduced with this new improvement. So it would be good to add a sample which demonstrate this procedure. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
[ https://issues.apache.org/jira/browse/AXIS2-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13451510#comment-13451510 ] Shameera Rathnayaka commented on AXIS2-5416: Hi , You can find a sample which demonstrate the XML Stream API base approach, here AXIS2-5417. Thanks, Shameera. Add Native approach and XML Stream API base approach Documentations --- Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: Documentation, json Fix For: 1.7.0 Attachments: JSONDucumentation.patch Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Commented] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
[ https://issues.apache.org/jira/browse/AXIS2-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13450435#comment-13450435 ] Shameera Rathnayaka commented on AXIS2-5416: Hi devs/Andreas, There is no any unit test which cover this ADB support, There is a sample which demonstrate Native support but not XML Stream API base approach. As I think it is good to write a sample for demonstrate this XML Stream API base approach. Therefore I will write a sample to cover this ADB support too.WDYT? Think above content structure is good enough :) Thanks, Shameera. Add Native approach and XML Stream API base approach Documentations --- Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: Documentation, json Fix For: 1.7.0 Attachments: JSONDucumentation.patch Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5411) Refactor Packages(impl and utils) of JSON module.
[ https://issues.apache.org/jira/browse/AXIS2-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5411: --- Attachment: (was: packageChange.patch) Refactor Packages(impl and utils) of JSON module. - Key: AXIS2-5411 URL: https://issues.apache.org/jira/browse/AXIS2-5411 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Priority: Minor Labels: gson, json Fix For: 1.7.0 Hi devs, Here i would like to suggest few modifications to the package names of JSON module. 1. org.apache.axis2.json.impl -- org.apache.axis2.json.gson as this explain the package content best 2. org.apache.axis2.json.impl.utils --- org.apache.axis2.json.gson.factory as all classes(JsonObject , JSONType, XmlNode classes are used by XmlNodeGenerator and XmlNodeGenerator class is being used by GsonXMLStreamReader/Writer, as well as JsonUtils class is being used by Json message receivers ) under the utils package are doing some works to the major classes like GsonXMLStreamReader/ Writer , JsonRPCMessageReceiver and JsonRPCInOnlyMessageReceiver. Most importantly this modifications won't do any major problems to the users as those are newly added packages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5411) Refactor Packages(impl and utils) of JSON module.
[ https://issues.apache.org/jira/browse/AXIS2-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5411: --- Attachment: sampleChanges.patch packageChange.patch HI devs, Seems earlier patch having some errors , Therefore i updated previous one with two new patches, packageChange.patch and sampleChanges.patch , for all changes. Thanks Shameera. Refactor Packages(impl and utils) of JSON module. - Key: AXIS2-5411 URL: https://issues.apache.org/jira/browse/AXIS2-5411 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Priority: Minor Labels: gson, json Fix For: 1.7.0 Attachments: packageChange.patch, sampleChanges.patch Hi devs, Here i would like to suggest few modifications to the package names of JSON module. 1. org.apache.axis2.json.impl -- org.apache.axis2.json.gson as this explain the package content best 2. org.apache.axis2.json.impl.utils --- org.apache.axis2.json.gson.factory as all classes(JsonObject , JSONType, XmlNode classes are used by XmlNodeGenerator and XmlNodeGenerator class is being used by GsonXMLStreamReader/Writer, as well as JsonUtils class is being used by Json message receivers ) under the utils package are doing some works to the major classes like GsonXMLStreamReader/ Writer , JsonRPCMessageReceiver and JsonRPCInOnlyMessageReceiver. Most importantly this modifications won't do any major problems to the users as those are newly added packages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
Shameera Rathnayaka created AXIS2-5416: -- Summary: Add Native approach and XML Stream API base approach Documentations Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5416) Add Native approach and XML Stream API base approach Documentations
[ https://issues.apache.org/jira/browse/AXIS2-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5416: --- Attachment: JSONDucumentation.patch Hi devs, I have attached a patch with this, after applying this patch. JSON support part of Table of Content, is look like JSON suppport JSON support with Mapped/Badgerfish formats* Pure JSON Support Native Approach XML Stream API Base Approach User Guide * This will link to previous JSON Support page. Thanks, Shameera. Add Native approach and XML Stream API base approach Documentations --- Key: AXIS2-5416 URL: https://issues.apache.org/jira/browse/AXIS2-5416 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: Documentation, json Fix For: 1.7.0 Attachments: JSONDucumentation.patch Now Axis2 can process pure JSON requests with both Native and XML Stream API base approaches. So it is necessary to expose this new improvements to Axis2 users by documentations. One page to explain the overall process with details to understand what is happening with each approach. And another page to explain how to configure and add these new approaches to their own services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5411) Refactor Packages(impl and utils) of JSON module.
[ https://issues.apache.org/jira/browse/AXIS2-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5411: --- Attachment: packageChange.patch Hi devs, You can find a patch with this, Please review and commit. Thanks Shameera. Refactor Packages(impl and utils) of JSON module. - Key: AXIS2-5411 URL: https://issues.apache.org/jira/browse/AXIS2-5411 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Priority: Minor Labels: gson, json Fix For: 1.7.0 Attachments: packageChange.patch Hi devs, Here i would like to suggest few modifications to the package names of JSON module. 1. org.apache.axis2.json.impl -- org.apache.axis2.json.gson as this explain the package content best 2. org.apache.axis2.json.impl.utils --- org.apache.axis2.json.gson.factory as all classes(JsonObject , JSONType, XmlNode classes are used by XmlNodeGenerator and XmlNodeGenerator class is being used by GsonXMLStreamReader/Writer, as well as JsonUtils class is being used by Json message receivers ) under the utils package are doing some works to the major classes like GsonXMLStreamReader/ Writer , JsonRPCMessageReceiver and JsonRPCInOnlyMessageReceiver. Most importantly this modifications won't do any major problems to the users as those are newly added packages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5402) JSON xml stream API based approach stack when request has a null, as a value
Shameera Rathnayaka created AXIS2-5402: -- Summary: JSON xml stream API based approach stack when request has a null, as a value Key: AXIS2-5402 URL: https://issues.apache.org/jira/browse/AXIS2-5402 Project: Axis2 Issue Type: Bug Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 JSON xml stream API based approach stack when request content has a null, as a value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5402) JSON xml stream API based approach stack when request has a null, as a value
[ https://issues.apache.org/jira/browse/AXIS2-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5402: --- Attachment: AXIS2-5402.patch Please find the patch with this, Also I have corrected some text message too. JSON xml stream API based approach stack when request has a null, as a value - Key: AXIS2-5402 URL: https://issues.apache.org/jira/browse/AXIS2-5402 Project: Axis2 Issue Type: Bug Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: gson, json Fix For: 1.7.0 Attachments: AXIS2-5402.patch JSON xml stream API based approach stack when request content has a null, as a value. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5403) Always expect parameter array when using JsonRPCMessageReceiver
Shameera Rathnayaka created AXIS2-5403: -- Summary: Always expect parameter array when using JsonRPCMessageReceiver Key: AXIS2-5403 URL: https://issues.apache.org/jira/browse/AXIS2-5403 Project: Axis2 Issue Type: Bug Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Fix For: 1.7.0 invokeService method in org.apache.axis2.json.impl.utils.JsonUtils class checks num of parameters , if parameter count is more than one, then it expects to be those parameters, values of JSON Array in request, if parameter count is equal to one then it doesn't expect to be that parameter, a value of JSON array. But it is better to expect parameters come as a values of JSON array always, even there is one parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5403) Always expect parameter array when using JsonRPCMessageReceiver
[ https://issues.apache.org/jira/browse/AXIS2-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5403: --- Attachment: AXIS2-5403.patch You can find a patch with this, Please review and commit Thanks, Shameera. Always expect parameter array when using JsonRPCMessageReceiver Key: AXIS2-5403 URL: https://issues.apache.org/jira/browse/AXIS2-5403 Project: Axis2 Issue Type: Bug Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Labels: gson, json Fix For: 1.7.0 Attachments: AXIS2-5403.patch invokeService method in org.apache.axis2.json.impl.utils.JsonUtils class checks num of parameters , if parameter count is more than one, then it expects to be those parameters, values of JSON Array in request, if parameter count is equal to one then it doesn't expect to be that parameter, a value of JSON array. But it is better to expect parameters come as a values of JSON array always, even there is one parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5404) Change schema processing design of org.apache.axis2.json.impl.utils.XmlNodeGenerator to handle anonymous and named complexTypes well.
Shameera Rathnayaka created AXIS2-5404: -- Summary: Change schema processing design of org.apache.axis2.json.impl.utils.XmlNodeGenerator to handle anonymous and named complexTypes well. Key: AXIS2-5404 URL: https://issues.apache.org/jira/browse/AXIS2-5404 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Priority: Minor Fix For: 1.7.0 Change schema processing design of org.apache.axis2.json.impl.utils.XmlNodeGenerator to handle anonymous and named complexTypes well. This will leads to better understanding of XmlSchema processing code base. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5404) Change schema processing design of org.apache.axis2.json.impl.utils.XmlNodeGenerator to handle anonymous and named complexTypes well.
[ https://issues.apache.org/jira/browse/AXIS2-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shameera Rathnayaka updated AXIS2-5404: --- Attachment: AXIS2-5404.patch You can find patch with this, Please review and commit Thanks, Shameera. Change schema processing design of org.apache.axis2.json.impl.utils.XmlNodeGenerator to handle anonymous and named complexTypes well. - Key: AXIS2-5404 URL: https://issues.apache.org/jira/browse/AXIS2-5404 Project: Axis2 Issue Type: Improvement Components: json Affects Versions: 1.7.0 Reporter: Shameera Rathnayaka Assignee: Shameera Rathnayaka Priority: Minor Fix For: 1.7.0 Attachments: AXIS2-5404.patch Change schema processing design of org.apache.axis2.json.impl.utils.XmlNodeGenerator to handle anonymous and named complexTypes well. This will leads to better understanding of XmlSchema processing code base. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Created] (AXIS2-5400) Use better designing approach for handle XmlSchema in XmlNodeGenerator class
Shameera Rathnayaka created AXIS2-5400 Use better designing approach for handle XmlSchema in XmlNodeGenerator class Issue Type: Improvement Affects Versions: 1.7.0 Assignee: Shameera Rathnayaka Components: json Created: 25/Aug/12 14:33 Description: At the moment in XmlNodeGenerator class use several methods in the same class to process and generate xmlNode which is an intermediate representation of operation XmlSchemalist. But for better understanding and designing it can be wrapped to two methods like processSchemaType(XmlSchemaType xmlSchemaType , XmlNode parentNode , XmlSchema schema) which process Complex and Simpel Types and processElement(XmlSchemaElement element, XmlNode parentNode , XmlSchema schema) which handle xmlSchema elements. Fix Versions: 1.7.0 Project: Axis2 Labels: json gson Priority: Major Reporter: Shameera Rathnayaka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
[jira] [Updated] (AXIS2-5400) Use better designing approach for handle XmlSchema in XmlNodeGenerator class
Shameera Rathnayaka updated AXIS2-5400 Use better designing approach for handle XmlSchema in XmlNodeGenerator class I have attached a patch(AXIS2-5400.patch) with this. Please review and commit Thanks, Shameera. Change By: Shameera Rathnayaka (25/Aug/12 14:46) Attachment: AXIS2-5400.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
