Reminder for Release Managers: archiving old releases
All, Please note that release managers are expected to archive old releases. In practice this means: 1. Before the release, change the site sources so that the download links for old releases point to archive.apache.org instead of the mirrors. If applicable, also change the status of the release indicated on the download page from "Mirrored" to "Archived". 2. After the release (once the new version of the site has been published), remove the old releases from the dist area (Once INFRA-6205 is completed, this will be https://dist.apache.org/repos/dist/release/axis). Note that projects are expected to have a single mirrored release par active branch of each project. Andreas - 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-tabpanel&focusedCommentId=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] [Commented] (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:comment-tabpanel&focusedCommentId=13649121#comment-13649121 ] Shameera Rathnayaka commented on AXIS2-5515: Hi Andreas, Yes , agree on your points, it is not an good idea to provide custom ObjectSuppliers to access XML data in runtime. This instantiate problem arise with Java UUID objects, as an alternative we can handle java UUID as same as what we does with java Enum, Map , List etc , but before that need to realized, should we support UUID in that way? > 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
[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-tabpanel&focusedCommentId=13649149#comment-13649149
]
Shameera Rathnayaka commented on AXIS2-5395:
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] [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-tabpanel&focusedCommentId=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] [Commented] (AXIS2-5393) org.apache.axis2.databinding.ADBException: Unexpected subelement SendAndCommitResult > error on good response
[ https://issues.apache.org/jira/browse/AXIS2-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649262#comment-13649262 ] Kishanthan Thangarajah commented on AXIS2-5393: --- What is the command that you used here to generate the code? I just had a quick look, by generating server side skeleton for the wsdl using adb data-binding, and generating a sample response for both the operations (TransactionInfo, SendAndCommit). I did not get into any issue as described. The responses are getting parsed fine by the service implementation. Here i'm attaching the service archive, which will send some mock responses for reference. Also since all the schema elements here are defined as exactly one type, the requests and responses also should adhere to that. So anything else that should be taken into consideration? > org.apache.axis2.databinding.ADBException: Unexpected subelement > SendAndCommitResult > error on good response > -- > > Key: AXIS2-5393 > URL: https://issues.apache.org/jira/browse/AXIS2-5393 > Project: Axis2 > Issue Type: Bug > Components: codegen, databinding >Affects Versions: 1.5.1, 1.6.1, 1.6.2 > Environment: OS: Linux > JDK: jdk1.6.0_21 > Apache: apache-tomcat-5.5.23 > Axis2 versions: 1.5.1, 1.6.2, 1.6.1 >Reporter: pdna >Priority: Critical > Attachments: firstdata-wsdl-webservice-stubs-new.jar, Service.aar, > ServiceStub.java > > > I've been getting the following error for all three versions of Axis2 listed > above: > > org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: > Unexpected subelement SendAndCommitResult > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub.fromOM(ServiceStub.java:9478) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub.sendAndCommit(ServiceStub.java:469) > at > com.printra.ccproc.FirstDataWSDLChargerTestNew.charge(FirstDataWSDLChargerTestNew.java:368) > at com.printra.ccproc.MultiCharger.charge(MultiCharger.java:31) > at com.printra.ccproc.test_charger.test_charge(test_charger.java:61) > at com.printra.ccproc.test_charger.main(test_charger.java:31) > Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: > Unexpected subelement SendAndCommitResult > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub$TransactionResult$Factory.parse(ServiceStub.java:4533) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub$SendAndCommitResponse$Factory.parse(ServiceStub.java:4938) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub.fromOM(ServiceStub.java:9472) > ... 5 more > Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement > SendAndCommitResult > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub$TransactionResult$Factory.parse(ServiceStub.java:3398) > ... 7 more > > I believe this is a problem with the way the code (that Axis2 generated via > Java2WSDL) parses the response. The XML of the response looks as expected, > i.e. the subelement SendAndCommitResponse is supposed to be there, where it > is. The WSDL is from First Data ( > https://api.globalgatewaye4.firstdata.com/transaction/wsdl) and is presumed > to be solid. -- 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-5393) org.apache.axis2.databinding.ADBException: Unexpected subelement SendAndCommitResult > error on good response
[ https://issues.apache.org/jira/browse/AXIS2-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishanthan Thangarajah updated AXIS2-5393: -- Attachment: Service.aar > org.apache.axis2.databinding.ADBException: Unexpected subelement > SendAndCommitResult > error on good response > -- > > Key: AXIS2-5393 > URL: https://issues.apache.org/jira/browse/AXIS2-5393 > Project: Axis2 > Issue Type: Bug > Components: codegen, databinding >Affects Versions: 1.5.1, 1.6.1, 1.6.2 > Environment: OS: Linux > JDK: jdk1.6.0_21 > Apache: apache-tomcat-5.5.23 > Axis2 versions: 1.5.1, 1.6.2, 1.6.1 >Reporter: pdna >Priority: Critical > Attachments: firstdata-wsdl-webservice-stubs-new.jar, Service.aar, > ServiceStub.java > > > I've been getting the following error for all three versions of Axis2 listed > above: > > org.apache.axis2.AxisFault: org.apache.axis2.databinding.ADBException: > Unexpected subelement SendAndCommitResult > at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub.fromOM(ServiceStub.java:9478) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub.sendAndCommit(ServiceStub.java:469) > at > com.printra.ccproc.FirstDataWSDLChargerTestNew.charge(FirstDataWSDLChargerTestNew.java:368) > at com.printra.ccproc.MultiCharger.charge(MultiCharger.java:31) > at com.printra.ccproc.test_charger.test_charge(test_charger.java:61) > at com.printra.ccproc.test_charger.main(test_charger.java:31) > Caused by: java.lang.Exception: org.apache.axis2.databinding.ADBException: > Unexpected subelement SendAndCommitResult > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub$TransactionResult$Factory.parse(ServiceStub.java:4533) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub$SendAndCommitResponse$Factory.parse(ServiceStub.java:4938) > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub.fromOM(ServiceStub.java:9472) > ... 5 more > Caused by: org.apache.axis2.databinding.ADBException: Unexpected subelement > SendAndCommitResult > at > com.e_xact.secure2.vplug_in.transaction.rpc_enc_test.ServiceStub$TransactionResult$Factory.parse(ServiceStub.java:3398) > ... 7 more > > I believe this is a problem with the way the code (that Axis2 generated via > Java2WSDL) parses the response. The XML of the response looks as expected, > i.e. the subelement SendAndCommitResponse is supposed to be there, where it > is. The WSDL is from First Data ( > https://api.globalgatewaye4.firstdata.com/transaction/wsdl) and is presumed > to be solid. -- 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-5489) Encoding GET parameters with '+' character in generated REST clients with WSDL2Java
[
https://issues.apache.org/jira/browse/AXIS2-5489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649264#comment-13649264
]
Kishanthan Thangarajah commented on AXIS2-5489:
---
First, the patch will get reviewed by the developers. The next planned release
is 1.6.3, so if this patch is applied before that, then it will be available
with that release.
> Encoding GET parameters with '+' character in generated REST clients with
> WSDL2Java
> ---
>
> Key: AXIS2-5489
> URL: https://issues.apache.org/jira/browse/AXIS2-5489
> Project: Axis2
> Issue Type: Bug
> Components: kernel, transports
>Affects Versions: 1.6.2
> Environment: Ubuntu
>Reporter: Miguel Ángel Francisco Fernández
>Priority: Blocker
> Labels: +, GET, REST, encode,
> Fix For: 1.6.2
>
> Attachments: AXIS2-5489.patch, axis2-kernel-1.6.2.jar
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Using the wsdl2java tool to generate a Java client to access a REST web
> service described with a WSDL 2.0, the generated client does not encode the
> symbol '+' in GET parameters.
> For example, if I have an URL "/get_url", and I set the parameter "param" to
> "x+x", the symbol "+" is not encoded, and therefore it is interpreted as a
> space on the server ("x x"). If I try to send the parameter encoded, i.e.,
> "%2B", then "%252B" is received in the server.
> Therefore, it is not possible to send the '+' symbol in a GET parameter.
> I guess that it is caused by the definition of the field
> LEGAL_CHARACTERS_IN_QUERY in the interface
> org.apache.axis2.description.WSDL2Constants, which is set to
> "-._~!$'()*+,;=:@/?"
--
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-tabpanel&focusedCommentId=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
