Jenkins build became unstable: sandesha2-trunk #648

2012-03-19 Thread Apache Jenkins Server 
See 


-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5217) Maven plug-in to run Axis2 simple HTTP server.

2012-03-19 Thread Hudson (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/AXIS2-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232506#comment-13232506
 ] 

Hudson commented on AXIS2-5217:
---

Integrated in Axis2 #1313 (See [https://builds.apache.org/job/Axis2/1313/])
AXIS2-5217
PluginDescriptor#getClassRealm() return type is not compatible among Maven2 and 
Maven3. Due to above issue this plug-in not work in Maven3. I have modified 
code to use Maven3 API hence will not work with Maven 2. 

We need to define Maven3 as a pre- requirement for the plug-in or need to find 
workaround  that works for both Maven versions. (Revision 1302297)

 Result = SUCCESS
sagara : 
Files : 
* /axis/axis2/java/core/trunk/modules/tool/simple-server-maven-plugin/pom.xml
* 
/axis/axis2/java/core/trunk/modules/tool/simple-server-maven-plugin/src/main/java/org/apache/axis2/maven2/server/SimpleHttpServerMojo.java


> Maven plug-in to run Axis2 simple HTTP server. 
> ---
>
> Key: AXIS2-5217
> URL: https://issues.apache.org/jira/browse/AXIS2-5217
> Project: Axis2
>  Issue Type: Improvement
>  Components: Tools
>Reporter: Sagara Gunathunga 
>Assignee: Sagara Gunathunga 
> Fix For: 1.7.0
>
>
> Original proposal available here 
> http://axis.markmail.org/thread/tjd7vcd2fjred474.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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

Jenkins build is back to stable : axis2-transports-trunk #721

2012-03-19 Thread Apache Jenkins Server 
See 


-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Jenkins build is back to stable : sandesha2-trunk ยป Sandesha2 - Test Suite #649

2012-03-19 Thread Apache Jenkins Server 
See 



-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Jenkins build is back to stable : sandesha2-trunk #649

2012-03-19 Thread Apache Jenkins Server 
See 


-
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

[jira] [Commented] (AXIS2-5270) [GSOC 2012] Improve Json support in Axis2 with google-gson

2012-03-19 Thread Shameera Rathnayaka (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/AXIS2-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232543#comment-13232543
 ] 

Shameera Rathnayaka commented on AXIS2-5270:


Hi devs ,

I have tried a few performance tests with current SOAP procedure vs implemented 
Json procedure with java bench tool. Here is the summarized results of what i 
received. I have attached the sample service jsonTestService.aar ( This is the 
same service which is  attached with my first reply but have done few minor 
modifications) used for this test.

Note: i have restarted axis2 server before run each test, to avoid effect of 
caching.

1.  Send 1000 requests to the echoUser method in the service with same user 
object which has exactly the same fields in both procedure. 

Json Implementation 
SOAP

Server Software:Simple-Server/1.1   
Simple-Server/1.1
Document Path:  http://localhost:8080/axis2/services/   
http://localhost:8080/axis2/services/
JsonTestService/echoUser
  
JsonTestService.JsonTestServiceHttpSoap11Endpoint/
Document Length:231 bytes   
795 bytes
Concurrency Level:  1   
   1
Time taken for tests:   2.648290 seconds
   3.551833 seconds
Complete requests:  1000
   1000
Total transferred:  472000 bytes
   1659000 bytes
Requests per second:377.60 [#/sec] (mean)  
281.54 [#/sec] (mean)
Time per request:   2.648 [ms] (mean)   
   3.552 [ms] (mean)
Transfer rate:  87.23 [Kbytes/sec] received
223.83 [Kbytes/sec] received
91.00 kb/s sent 
   243.25 kb/s sent

2. Send 1000 requests to the addUserList method in the service with list of 
1000 users. 

Json Implementation 
SOAP

Server Software:Simple-Server/1.1   
Simple-Server/1.1
Document Path:  http://localhost:8080/axis2/services/   
http://localhost:8080/axis2/services/
JsonTestService/addUserList 
JsonTestService.JsonTestServiceHttpSoap11Endpoint/
Document Length:17 bytes
   276 bytes
Concurrency Level:  1   
   1
Time taken for tests:   7.669473 seconds
   27.230592 seconds
Complete requests:  1000
   1000
Total transferred:  219052000 bytes
401567000 bytes
Requests per second:130.39 [#/sec] (mean)  
36.72 [#/sec] (mean)
Time per request:   7.669 [ms] (mean)   
   27.231 [ms] (mean)
Transfer rate:  2.22 [Kbytes/sec] received  
   10.14 [Kbytes/sec] received
28,559.33 kb/s sent 
   14,736.77 kb/s sent


> [GSOC 2012] Improve Json support in Axis2 with google-gson
> --
>
> Key: AXIS2-5270
> URL: https://issues.apache.org/jira/browse/AXIS2-5270
> Project: Axis2
>  Issue Type: Improvement
>  Components: json
>Affects Versions: 1.7.0
>Reporter: Shameera Rathnayaka
>Assignee: Shameera Rathnayaka
>  Labels: gsoc2012, gson, json
> Fix For: 1.7.0
>
> Attachments: attachments.zip
>
>
> There are two ways that xml string can be converted into JSON string, 
> Badgerfish and Mapped . Current Axis2 with JSON module completely supports 
> Badgerfish convention[1] while partialy supports Mapped convention[1] as 
> Mapped formatted JSON with namespaces are not supported in Axis2. Therefore 
> if the client side java-script code needs to talk with java service which is 
> deployed in Axis2, it should be sent as Badgerfish convention. It is 
> cumbersome to generate Badgerfish convention of JSON string again and again 
> to call services if there is no  xml representation string in clien

[jira] [Updated] (AXIS2-5270) [GSOC 2012] Improve Json support in Axis2 with google-gson

2012-03-19 Thread Shameera Rathnayaka (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shameera Rathnayaka updated AXIS2-5270:
---

Comment: was deleted

(was: Hi devs ,

I have tried a few performance tests with current SOAP procedure vs implemented 
Json procedure with java bench tool. Here is the summarized results of what i 
received. I have attached the sample service jsonTestService.aar ( This is the 
same service which is  attached with my first reply but have done few minor 
modifications) used for this test.

Note: i have restarted axis2 server before run each test, to avoid effect of 
caching.

1.  Send 1000 requests to the echoUser method in the service with same user 
object which has exactly the same fields in both procedure. 

Json Implementation 
SOAP

Server Software:Simple-Server/1.1   
Simple-Server/1.1
Document Path:  http://localhost:8080/axis2/services/   
http://localhost:8080/axis2/services/
JsonTestService/echoUser
  
JsonTestService.JsonTestServiceHttpSoap11Endpoint/
Document Length:231 bytes   
795 bytes
Concurrency Level:  1   
   1
Time taken for tests:   2.648290 seconds
   3.551833 seconds
Complete requests:  1000
   1000
Total transferred:  472000 bytes
   1659000 bytes
Requests per second:377.60 [#/sec] (mean)  
281.54 [#/sec] (mean)
Time per request:   2.648 [ms] (mean)   
   3.552 [ms] (mean)
Transfer rate:  87.23 [Kbytes/sec] received
223.83 [Kbytes/sec] received
91.00 kb/s sent 
   243.25 kb/s sent

2. Send 1000 requests to the addUserList method in the service with list of 
1000 users. 

Json Implementation 
SOAP

Server Software:Simple-Server/1.1   
Simple-Server/1.1
Document Path:  http://localhost:8080/axis2/services/   
http://localhost:8080/axis2/services/
JsonTestService/addUserList 
JsonTestService.JsonTestServiceHttpSoap11Endpoint/
Document Length:17 bytes
   276 bytes
Concurrency Level:  1   
   1
Time taken for tests:   7.669473 seconds
   27.230592 seconds
Complete requests:  1000
   1000
Total transferred:  219052000 bytes
401567000 bytes
Requests per second:130.39 [#/sec] (mean)  
36.72 [#/sec] (mean)
Time per request:   7.669 [ms] (mean)   
   27.231 [ms] (mean)
Transfer rate:  2.22 [Kbytes/sec] received  
   10.14 [Kbytes/sec] received
28,559.33 kb/s sent 
   14,736.77 kb/s sent
)

> [GSOC 2012] Improve Json support in Axis2 with google-gson
> --
>
> Key: AXIS2-5270
> URL: https://issues.apache.org/jira/browse/AXIS2-5270
> Project: Axis2
>  Issue Type: Improvement
>  Components: json
>Affects Versions: 1.7.0
>Reporter: Shameera Rathnayaka
>Assignee: Shameera Rathnayaka
>  Labels: gsoc2012, gson, json
> Fix For: 1.7.0
>
> Attachments: attachments.zip
>
>
> There are two ways that xml string can be converted into JSON string, 
> Badgerfish and Mapped . Current Axis2 with JSON module completely supports 
> Badgerfish convention[1] while partialy supports Mapped convention[1] as 
> Mapped formatted JSON with namespaces are not supported in Axis2. Therefore 
> if the client side java-script code needs to talk with java service which is 
> deployed in Axis2, it should be sent as Badgerfish convention. It is 
> cumbersome to generate Badgerfish convention of JSON string again and again 
> to call services if there is no  xml representation string in client side.
> If java script client can

[jira] [Updated] (AXIS2-5270) [GSOC 2012] Improve Json support in Axis2 with google-gson

2012-03-19 Thread Shameera Rathnayaka (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shameera Rathnayaka updated AXIS2-5270:
---

Attachment: JsonTestService.aar
performance_test.txt

I have tried a few performance tests with current SOAP procedure vs implemented 
Json procedure with java bench tool. Here i have attached performance_test.txt 
file which has the summarized results of what i received. Also I have attached 
the sample service jsonTestService.aar ( This is the same service which is  
attached with my first reply but have done few minor modifications) used for 
this test.

Note: i have restarted axis2 server before run each test, to avoid effect of 
caching.

> [GSOC 2012] Improve Json support in Axis2 with google-gson
> --
>
> Key: AXIS2-5270
> URL: https://issues.apache.org/jira/browse/AXIS2-5270
> Project: Axis2
>  Issue Type: Improvement
>  Components: json
>Affects Versions: 1.7.0
>Reporter: Shameera Rathnayaka
>Assignee: Shameera Rathnayaka
>  Labels: gsoc2012, gson, json
> Fix For: 1.7.0
>
> Attachments: JsonTestService.aar, attachments.zip, 
> performance_test.txt
>
>
> There are two ways that xml string can be converted into JSON string, 
> Badgerfish and Mapped . Current Axis2 with JSON module completely supports 
> Badgerfish convention[1] while partialy supports Mapped convention[1] as 
> Mapped formatted JSON with namespaces are not supported in Axis2. Therefore 
> if the client side java-script code needs to talk with java service which is 
> deployed in Axis2, it should be sent as Badgerfish convention. It is 
> cumbersome to generate Badgerfish convention of JSON string again and again 
> to call services if there is no  xml representation string in client side.
> If java script client can send JSON object to relevant java service in Axis2, 
> defining service and operation in request url, without doing any 
> modifications to JSON objects, then it would be very helpful for Java-Script 
> users at client side.
> According to the thread in the mailing list, which discussed $subject we have 
> two approaches. i have summarized those two approaches as below. 
> 1. Store json inputstream in message context at the message builder while 
> putting dummy SOAPEnvelop to the message context, and using google-gson 
> process it inside the message receiver 
> 2. Preserve the requirement that a message must have a well defined SOAP 
> infoset and use a trivial representation similar (or identical) to what we 
> use for plain text. This has the advantage that it is more in line with the 
> rest of the Axis2 architecture, 
> or 
>another option is to write an xmlstream reader/writer implementation to 
> parse the json stream. And provide that xml stream implementation to Axiom. 
> [1]http://wso2.org/library/768

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-5270) [GSOC 2012] Improve Json support in Axis2 with google-gson

2012-03-19 Thread Sagara Gunathunga (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/AXIS2-5270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232565#comment-13232565
 ] 

Sagara Gunathunga  commented on AXIS2-5270:
---

These are some comments according to my last post. 

1.) It would be great if you can use a dedicated Boolean flag to decide the 
particular message will process by JosnRPCMessageReceiver or fullback to use 
RPCMessageReceiver instead of INPUT_STREAM property because this make your 
design clean and well defined. I would like to see following flow. 

In JosnRPCMessageReceiver check above flag and decide further processing.

In RPCMessageReceiver add the same check and if it's true return a fault 
instead of further processing. This case can occur when user enable 
JSONBuilder/JSONFormatter in axis2.xml but haven't define 
JosnRPCMessageReceiver MRs in services.xml file. With this improvement your MR 
modification become consistent.

2.) I don't think we can drop the support for other transports hence IMO we 
need to create first element of SOAP envelope in order to employ SOAP Body 
based dispatching, I think you can create JsonStreamParser [1] and read first 
element to facilitate to above then you can use same JsonStreamParser instance 
to further unmarshaling. 

[1] - 
http://google-gson.googlecode.com/svn/trunk/gson/docs/javadocs/com/google/gson/JsonStreamParser.html
 

3.) Look likes you have some good numbers with performance but IMO you have to 
test your new JSON implementation with existing JSON implementation for a 
better comparison also use around 50 000 message for testing . 


> [GSOC 2012] Improve Json support in Axis2 with google-gson
> --
>
> Key: AXIS2-5270
> URL: https://issues.apache.org/jira/browse/AXIS2-5270
> Project: Axis2
>  Issue Type: Improvement
>  Components: json
>Affects Versions: 1.7.0
>Reporter: Shameera Rathnayaka
>Assignee: Shameera Rathnayaka
>  Labels: gsoc2012, gson, json
> Fix For: 1.7.0
>
> Attachments: JsonTestService.aar, attachments.zip, 
> performance_test.txt
>
>
> There are two ways that xml string can be converted into JSON string, 
> Badgerfish and Mapped . Current Axis2 with JSON module completely supports 
> Badgerfish convention[1] while partialy supports Mapped convention[1] as 
> Mapped formatted JSON with namespaces are not supported in Axis2. Therefore 
> if the client side java-script code needs to talk with java service which is 
> deployed in Axis2, it should be sent as Badgerfish convention. It is 
> cumbersome to generate Badgerfish convention of JSON string again and again 
> to call services if there is no  xml representation string in client side.
> If java script client can send JSON object to relevant java service in Axis2, 
> defining service and operation in request url, without doing any 
> modifications to JSON objects, then it would be very helpful for Java-Script 
> users at client side.
> According to the thread in the mailing list, which discussed $subject we have 
> two approaches. i have summarized those two approaches as below. 
> 1. Store json inputstream in message context at the message builder while 
> putting dummy SOAPEnvelop to the message context, and using google-gson 
> process it inside the message receiver 
> 2. Preserve the requirement that a message must have a well defined SOAP 
> infoset and use a trivial representation similar (or identical) to what we 
> use for plain text. This has the advantage that it is more in line with the 
> rest of the Axis2 architecture, 
> or 
>another option is to write an xmlstream reader/writer implementation to 
> parse the json stream. And provide that xml stream implementation to Axiom. 
> [1]http://wso2.org/library/768

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-5273) Allows forward-compatibility by ignoring unexpected enumeration values

2012-03-19 Thread Cleber Zarate (Created) (JIRA) 
Allows forward-compatibility by ignoring unexpected enumeration values
--

 Key: AXIS2-5273
 URL: https://issues.apache.org/jira/browse/AXIS2-5273
 Project: Axis2
  Issue Type: Bug
  Components: adb, codegen
Affects Versions: 1.7.0
Reporter: Cleber Zarate
Priority: Minor


[AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
elements. However, to truly be forward-compatibly, generated code should also 
ignore unexpected enumeration values.
Here's the snippet necessary for the adb code generation. I opted to return 
null when an unexpected enumeration is found, as opposed to skip it:

ADBBeanTemplate-bean.xsl line 2135:

// handle unexpected enumeration values properly

log.warn("Unexpected value " + value + " for 
enumeration ");
return enumeration;


if ((enumeration == null) && !((value == null) 
|| (value.equals("" {
throw new java.lang.IllegalArgumentException();
}
return enumeration;



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-5273) Allows forward-compatibility by ignoring unexpected enumeration values

2012-03-19 Thread Cleber Zarate (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cleber Zarate updated AXIS2-5273:
-

Attachment: patch.txt

Patch for ignoring unexpected enumeration values

> Allows forward-compatibility by ignoring unexpected enumeration values
> --
>
> Key: AXIS2-5273
> URL: https://issues.apache.org/jira/browse/AXIS2-5273
> Project: Axis2
>  Issue Type: Bug
>  Components: adb, codegen
>Affects Versions: 1.7.0
>Reporter: Cleber Zarate
>Priority: Minor
>  Labels: adb, adb-codegen, enumeration, restriction
> Attachments: patch.txt
>
>
> [AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
> elements. However, to truly be forward-compatibly, generated code should also 
> ignore unexpected enumeration values.
> Here's the snippet necessary for the adb code generation. I opted to return 
> null when an unexpected enumeration is found, as opposed to skip it:
> ADBBeanTemplate-bean.xsl line 2135:
> // handle unexpected enumeration values properly
> 
> log.warn("Unexpected value " + value + " for 
> enumeration ");
> return enumeration;
> 
> 
> if ((enumeration == null) && !((value == 
> null) || (value.equals("" {
> throw new java.lang.IllegalArgumentException();
> }
> return enumeration;
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-5273) Allows forward-compatibility by ignoring unexpected enumeration values

2012-03-19 Thread Cleber Zarate (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cleber Zarate updated AXIS2-5273:
-

Description: 
[AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
elements. However, to truly be forward-compatible, generated code should also 
ignore unexpected enumeration values.
Here's the snippet necessary for the adb code generation. I opted to return 
null when an unexpected enumeration is found, as opposed to skip it:

ADBBeanTemplate-bean.xsl line 2135:

// handle unexpected enumeration values properly

log.warn("Unexpected value " + value + " for 
enumeration ");
return enumeration;


if ((enumeration == null) && !((value == null) 
|| (value.equals("" {
throw new java.lang.IllegalArgumentException();
}
return enumeration;



  was:
[AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
elements. However, to truly be forward-compatibly, generated code should also 
ignore unexpected enumeration values.
Here's the snippet necessary for the adb code generation. I opted to return 
null when an unexpected enumeration is found, as opposed to skip it:

ADBBeanTemplate-bean.xsl line 2135:

// handle unexpected enumeration values properly

log.warn("Unexpected value " + value + " for 
enumeration ");
return enumeration;


if ((enumeration == null) && !((value == null) 
|| (value.equals("" {
throw new java.lang.IllegalArgumentException();
}
return enumeration;




> Allows forward-compatibility by ignoring unexpected enumeration values
> --
>
> Key: AXIS2-5273
> URL: https://issues.apache.org/jira/browse/AXIS2-5273
> Project: Axis2
>  Issue Type: Bug
>  Components: adb, codegen
>Affects Versions: 1.7.0
>Reporter: Cleber Zarate
>Priority: Minor
>  Labels: adb, adb-codegen, enumeration, restriction
> Attachments: patch.txt
>
>
> [AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
> elements. However, to truly be forward-compatible, generated code should also 
> ignore unexpected enumeration values.
> Here's the snippet necessary for the adb code generation. I opted to return 
> null when an unexpected enumeration is found, as opposed to skip it:
> ADBBeanTemplate-bean.xsl line 2135:
> // handle unexpected enumeration values properly
> 
> log.warn("Unexpected value " + value + " for 
> enumeration ");
> return enumeration;
> 
> 
> if ((enumeration == null) && !((value == 
> null) || (value.equals("" {
> throw new java.lang.IllegalArgumentException();
> }
> return enumeration;
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-5273) Allow forward-compatibility by ignoring unexpected enumeration values

2012-03-19 Thread Cleber Zarate (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cleber Zarate updated AXIS2-5273:
-

Summary: Allow forward-compatibility by ignoring unexpected enumeration 
values  (was: Allows forward-compatibility by ignoring unexpected enumeration 
values)

> Allow forward-compatibility by ignoring unexpected enumeration values
> -
>
> Key: AXIS2-5273
> URL: https://issues.apache.org/jira/browse/AXIS2-5273
> Project: Axis2
>  Issue Type: Bug
>  Components: adb, codegen
>Affects Versions: 1.7.0
>Reporter: Cleber Zarate
>Priority: Minor
>  Labels: adb, adb-codegen, enumeration, restriction
> Attachments: patch.txt
>
>
> [AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
> elements. However, to truly be forward-compatible, generated code should also 
> ignore unexpected enumeration values.
> Here's the snippet necessary for the adb code generation. I opted to return 
> null when an unexpected enumeration is found, as opposed to skip it:
> ADBBeanTemplate-bean.xsl line 2135:
> // handle unexpected enumeration values properly
> 
> log.warn("Unexpected value " + value + " for 
> enumeration ");
> return enumeration;
> 
> 
> if ((enumeration == null) && !((value == 
> null) || (value.equals("" {
> throw new java.lang.IllegalArgumentException();
> }
> return enumeration;
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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-5273) Allow forward-compatibility by ignoring unexpected enumeration values

2012-03-19 Thread Sagara Gunathunga (Commented) (JIRA) 

[ 
https://issues.apache.org/jira/browse/AXIS2-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232683#comment-13232683
 ] 

Sagara Gunathunga  commented on AXIS2-5273:
---

Can you attach a test case or a sample service (source code) you used to test 
this patch ? 

> Allow forward-compatibility by ignoring unexpected enumeration values
> -
>
> Key: AXIS2-5273
> URL: https://issues.apache.org/jira/browse/AXIS2-5273
> Project: Axis2
>  Issue Type: Bug
>  Components: adb, codegen
>Affects Versions: 1.7.0
>Reporter: Cleber Zarate
>Priority: Minor
>  Labels: adb, adb-codegen, enumeration, restriction
> Attachments: patch.txt
>
>
> [AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
> elements. However, to truly be forward-compatible, generated code should also 
> ignore unexpected enumeration values.
> Here's the snippet necessary for the adb code generation. I opted to return 
> null when an unexpected enumeration is found, as opposed to skip it:
> ADBBeanTemplate-bean.xsl line 2135:
> // handle unexpected enumeration values properly
> 
> log.warn("Unexpected value " + value + " for 
> enumeration ");
> return enumeration;
> 
> 
> if ((enumeration == null) && !((value == 
> null) || (value.equals("" {
> throw new java.lang.IllegalArgumentException();
> }
> return enumeration;
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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] [Issue Comment Edited] (AXIS2-5239) Upgrade Axis2 to use xmlschema2

2012-03-19 Thread Prabhath Suminda (Issue Comment Edited) (JIRA) 

[ 
https://issues.apache.org/jira/browse/AXIS2-5239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232710#comment-13232710
 ] 

Prabhath Suminda edited comment on AXIS2-5239 at 3/19/12 4:30 PM:
--

Can you suggest a particular module to start developing test cases as a start?

  
> Upgrade Axis2 to use xmlschema2 
> 
>
> Key: AXIS2-5239
> URL: https://issues.apache.org/jira/browse/AXIS2-5239
> Project: Axis2
>  Issue Type: Improvement
>Reporter: Sagara Gunathunga 
>  Labels: axis-gsoc, gsoc2012
>
> This involves writing some test coverage for existing xmlschema features and 
> porting to new xmlschema2 API.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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

Build failed in Jenkins: axis-trunk #121

2012-03-19 Thread Apache Jenkins Server 
See 

Changes:

[veithen] Allow changing the Java class associated with an XML type in 
maven-wsdl2java-plugin. This feature can be used to enable MTOM in client stubs.

Note that this requires a minor change in the toJava.Emitter, so that the 
BaseTypeMapping can be overridden (in the previous version of the code it was 
always reset to the default BaseTypeMapping implementation).

--
[...truncated 8195 lines...]
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-ws-addr/2.4.4/cxf-rt-ws-addr-2.4.4.jar
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-databinding-jaxb/2.4.4/cxf-rt-databinding-jaxb-2.4.4.jar
 (92 KB at 36.5 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-transports-http-jetty/2.4.4/cxf-rt-transports-http-jetty-2.4.4.jar
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-frontend-simple/2.4.4/cxf-rt-frontend-simple-2.4.4.jar
 (98 KB at 35.4 KB/sec)
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-transports-http/2.4.4/cxf-rt-transports-http-2.4.4.jar
 (203 KB at 82.8 KB/sec)
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-transports-common/2.4.4/cxf-rt-transports-common-2.4.4.jar
 (18 KB at 7.9 KB/sec)
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-ws-addr/2.4.4/cxf-rt-ws-addr-2.4.4.jar
 (85 KB at 37.8 KB/sec)
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-transports-http-jetty/2.4.4/cxf-rt-transports-http-jetty-2.4.4.jar
 (67 KB at 29.3 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ mtomstub-sample ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ 
mtomstub-sample ---
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ 
mtomstub-sample ---
[INFO] [INFO] Compiling 3 source files to 


[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ 
mtomstub-sample ---
[INFO] Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-java2ws/2.4.4/cxf-tools-java2ws-2.4.4.pom

[INFO] --- cxf-java2ws-plugin:2.4.4:java2ws (process-classes) @ mtomstub-sample 
---
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-java2ws/2.4.4/cxf-tools-java2ws-2.4.4.pom
 (8 KB at 23.6 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-core/2.4.4/cxf-tools-wsdlto-core-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-core/2.4.4/cxf-tools-wsdlto-core-2.4.4.pom
 (6 KB at 11.2 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-validator/2.4.4/cxf-tools-validator-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-validator/2.4.4/cxf-tools-validator-2.4.4.pom
 (5 KB at 9.0 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-databinding-jaxb/2.4.4/cxf-tools-wsdlto-databinding-jaxb-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-databinding-jaxb/2.4.4/cxf-tools-wsdlto-databinding-jaxb-2.4.4.pom
 (3 KB at 5.1 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/2.4.4/cxf-tools-wsdlto-frontend-jaxws-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-frontend-jaxws/2.4.4/cxf-tools-wsdlto-frontend-jaxws-2.4.4.pom
 (3 KB at 6.2 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-javascript/2.4.4/cxf-rt-javascript-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-javascript/2.4.4/cxf-rt-javascript-2.4.4.pom
 (6 KB at 12.0 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-transports-local/2.4.4/cxf-rt-transports-local-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-transports-local/2.4.4/cxf-rt-transports-local-2.4.4.pom
 (3 KB at 5.5 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-databinding-aegis/2.4.4/cxf-rt-databinding-aegis-2.4.4.pom
Downloaded: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-rt-databinding-aegis/2.4.4/cxf-rt-databinding-aegis-2.4.4.pom
 (5 KB at 8.7 KB/sec)
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-java2ws/2.4.4/cxf-tools-java2ws-2.4.4.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-core/2.4.4/cxf-tools-wsdlto-core-2.4.4.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-validator/2.4.4/cxf-tools-validator-2.4.4.jar
Downloading: 
http://repo1.maven.org/maven2/org/apache/cxf/cxf-tools-wsdlto-databinding-jaxb/2.4.4/cxf-tools-wsdlto-databinding-jaxb-2.4.4.jar
Downloading: 
http://repo1.maven.org/maven2

[jira] [Updated] (AXIS2-5273) Allow forward-compatibility by ignoring unexpected enumeration values

2012-03-19 Thread Cleber Zarate (Updated) (JIRA) 

 [ 
https://issues.apache.org/jira/browse/AXIS2-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cleber Zarate updated AXIS2-5273:
-

Attachment: favoriteCharacters_service_original_enumeration_values.zip
favoriteCharacters_service_new_enumeration_value.zip
favoriteCharacters_client_beforePatch.zip
favoriteCharacters_client_afterPatch.zip

file favoriteCharacters_service_original_enumeration_values.zip contains a 
simple service that exposes a method that returns an enumeration with 4 values. 
favoriteCharacters_service_new_enumeration_value.zip is a newer version of the 
previous service, which happens to add a new value in the enumeration (now 5 
values total).
File favoriteCharacters_client_beforePatch.zip contains a client project 
generated against the original service WSDL (containing 4 values). When pointed 
to the new service, an IllegalArgumentException is thrown.
File favoriteCharacters_client_afterPatch.zip contains the same client project 
generated against the original service WSDL (4 values), however because of the 
patch, it won't throw any exceptions when pointing to the new service.
The binding will return null when it encounters the unexpected new enumeration 
value.

> Allow forward-compatibility by ignoring unexpected enumeration values
> -
>
> Key: AXIS2-5273
> URL: https://issues.apache.org/jira/browse/AXIS2-5273
> Project: Axis2
>  Issue Type: Bug
>  Components: adb, codegen
>Affects Versions: 1.7.0
>Reporter: Cleber Zarate
>Priority: Minor
>  Labels: adb, adb-codegen, enumeration, restriction
> Attachments: favoriteCharacters_client_afterPatch.zip, 
> favoriteCharacters_client_beforePatch.zip, 
> favoriteCharacters_service_new_enumeration_value.zip, 
> favoriteCharacters_service_original_enumeration_values.zip, patch.txt
>
>
> [AXIS2-4859] has been patched adding the -Eiu option to ignore unexpected 
> elements. However, to truly be forward-compatible, generated code should also 
> ignore unexpected enumeration values.
> Here's the snippet necessary for the adb code generation. I opted to return 
> null when an unexpected enumeration is found, as opposed to skip it:
> ADBBeanTemplate-bean.xsl line 2135:
> // handle unexpected enumeration values properly
> 
> log.warn("Unexpected value " + value + " for 
> enumeration ");
> return enumeration;
> 
> 
> if ((enumeration == null) && !((value == 
> null) || (value.equals("" {
> throw new java.lang.IllegalArgumentException();
> }
> return enumeration;
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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