date:20070503


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

Samisa Abeysinghe resolved AXIS2C-582.
--

Resolution: Fixed

use double quotes in the given install path - that fixes the problem

 Building axis2c fails when OpenSSL is installed into a directory with spaces 
 (on Windows)
 -

 Key: AXIS2C-582
 URL: https://issues.apache.org/jira/browse/AXIS2C-582
 Project: Axis2-C
  Issue Type: Bug
  Components: build system (Windows)
 Environment: Windows XP
Reporter: Evanthika Amarasiri

 Below are the steps to reproduce the issue
 1. Installed OpenSSL in to the directory C:\Program Files\OpenSSL
 2. Enabled SSL in the configure.in file
 3. Executed the command nmake all
 4. Got the following issue while building
 
 Generating Code...
 LINK : fatal error LNK1181: cannot open input file 'Files\OpenSSL\lib\VC.obj'
 NMAKE : fatal error U1077: 'C:\Program Files\Microsoft Visual Studio 
 8\VC\BIN\link.exe' : return code '0x49d'
 Stop.
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (AXIS2C-535) Axis2/C adds rampart handlers when they are not engaged.

2007-05-03 Thread Malinda Kaushalye Kapuruge (JIRA)


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

Malinda Kaushalye Kapuruge reassigned AXIS2C-535:
-

Assignee: Malinda Kaushalye Kapuruge

 Axis2/C adds rampart handlers when they are not engaged.
 

 Key: AXIS2C-535
 URL: https://issues.apache.org/jira/browse/AXIS2C-535
 Project: Axis2-C
  Issue Type: Bug
Affects Versions: Current (Nightly)
Reporter: Manjula Peiris
 Assigned To: Malinda Kaushalye Kapuruge
Priority: Critical
 Attachments: patch.txt


 If we run normal Axis2/C samples after building rampart they fail. This is 
 because Axis2/C engine adds rampart handlers to its phases even  the module 
 is not engaged in the axis2.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (AXIS2C-535) Axis2/C adds rampart handlers when they are not engaged.

2007-05-03 Thread Malinda Kaushalye Kapuruge (JIRA)


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

Malinda Kaushalye Kapuruge closed AXIS2C-535.
-


 Axis2/C adds rampart handlers when they are not engaged.
 

 Key: AXIS2C-535
 URL: https://issues.apache.org/jira/browse/AXIS2C-535
 Project: Axis2-C
  Issue Type: Bug
Affects Versions: Current (Nightly)
Reporter: Manjula Peiris
 Assigned To: Malinda Kaushalye Kapuruge
Priority: Critical
 Attachments: patch.txt


 If we run normal Axis2/C samples after building rampart they fail. This is 
 because Axis2/C engine adds rampart handlers to its phases even  the module 
 is not engaged in the axis2.xml.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (AXIS2C-224) Calculator server sample need to be changed


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

Samisa Abeysinghe resolved AXIS2C-224.
--

Resolution: Won't Fix

Dynamic client has been dropped form 1.0.0

 Calculator server sample need to be changed
 ---

 Key: AXIS2C-224
 URL: https://issues.apache.org/jira/browse/AXIS2C-224
 Project: Axis2-C
  Issue Type: Improvement
  Components: samples
Affects Versions: Current (Nightly)
Reporter: Damitha Kumarage

 Calculator server sample need to be changed so that it serves both wsdl1 and 
 wsdl2
 dynamic client requests done by dynamic client sample

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (AXIS2C-515) the sample dynamic_client segfault on Linux: double free or corruption


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

Samisa Abeysinghe resolved AXIS2C-515.
--

Resolution: Won't Fix

Dynamic client has been removed form 1.0.0

 the sample dynamic_client segfault on Linux: double free or corruption
 --

 Key: AXIS2C-515
 URL: https://issues.apache.org/jira/browse/AXIS2C-515
 Project: Axis2-C
  Issue Type: Bug
  Components: xml/om
 Environment: Linux
Reporter: Dushshantha Chandradasa

 The sample dynamic_client segfaults with the message:
 *** glibc detected *** ./dynamic_client: double free or corruption (!prev): 
 0x0065ed50 ***
 === Backtrace: =
 /lib64/libc.so.6[0x2b7c278a837e]
 /lib64/libc.so.6(__libc_free+0x6c)[0x2b7c278a999c]
 /usr/lib64/libxml2.so.2(xmlBufferFree+0x2e)[0x2b7c272dcfae]
 /root/axis2Test/c/deploy/lib/libaxis2_parser.so.0(axis2_libxml2_writer_wrapper_free+0x30)[0x2b7c26d339d0]
 /root/axis2Test/c/deploy/lib/libaxis2_axiom.so.0(axiom_output_free+0x88)[0x2b7c26c185d8]
 ./dynamic_client[0x401293]
 /lib64/libc.so.6(__libc_start_main+0xf4)[0x2b7c2785a154]
 ...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release

2007-05-03 Thread Dinesh Premalal

+1 

thanks,
Dinesh
-- 
Dinesh Premalal
[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255 955C

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (AXIS2C-599) compile errors


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

Samisa Abeysinghe resolved AXIS2C-599.
--

Resolution: Fixed
  Assignee: Samisa Abeysinghe

Removed duplication

 compile errors
 --

 Key: AXIS2C-599
 URL: https://issues.apache.org/jira/browse/AXIS2C-599
 Project: Axis2-C
  Issue Type: Bug
 Environment: Microsoft Visual Studio 7.1 on Windows XP
Reporter: Jim S
 Assigned To: Samisa Abeysinghe

 I am getting compile errors attempting to compile the source code from Final 
 version 1.0.0
 If I comment out the second occurrence of this variable the source 
 compilation works properly
 This is because the same variable is being defined more than once.in 
 axutil_error.h
 Line 561:
 const axis2_char_t* axutil_error_messages[AXIS2_ERROR_LAST + 1];
 Line 579
const axis2_char_t* axutil_error_messages[AXIS2_ERROR_LAST + 1];
   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release

2007-05-03 Thread Dushshantha Chandradasa


tested and reviewed on windows. Works fine. Here's my +1

regards,
Dushshantha

On 5/3/07, Dinesh Premalal [EMAIL PROTECTED] wrote:


+1

thanks,
Dinesh
--
Dinesh Premalal
[EMAIL PROTECTED]
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257  0229 4F44 266E A255 955C

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (AXIS2C-510) Integrate security policy with rampart

2007-05-03 Thread Malinda Kaushalye Kapuruge (JIRA)


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

Malinda Kaushalye Kapuruge reassigned AXIS2C-510:
-

Assignee: Malinda Kaushalye Kapuruge

 Integrate security policy with rampart
 --

 Key: AXIS2C-510
 URL: https://issues.apache.org/jira/browse/AXIS2C-510
 Project: Axis2-C
  Issue Type: New Feature
  Components: rampart
Affects Versions: 1.0.0
 Environment: Any
Reporter: Malinda Kaushalye Kapuruge
 Assigned To: Malinda Kaushalye Kapuruge
 Fix For: 1.0.0


 Rampart should support security policy. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (AXIS2C-510) Integrate security policy with rampart

2007-05-03 Thread Malinda Kaushalye Kapuruge (JIRA)


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

Malinda Kaushalye Kapuruge closed AXIS2C-510.
-


 Integrate security policy with rampart
 --

 Key: AXIS2C-510
 URL: https://issues.apache.org/jira/browse/AXIS2C-510
 Project: Axis2-C
  Issue Type: New Feature
  Components: rampart
Affects Versions: 1.0.0
 Environment: Any
Reporter: Malinda Kaushalye Kapuruge
 Assigned To: Malinda Kaushalye Kapuruge
 Fix For: 1.0.0


 Rampart should support security policy. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release

2007-05-03 Thread Sanjaya Ratnaweera


Tested and reviewed on Linux. Here is my +1.

Thanks

   ~sanjaya

Samisa Abeysinghe wrote:

Hi Devs,

  After fixing the issues found with the initial release artifacts, I 
have re-packaged and uploaded the Apache Axis2/C 1.0.0 release

artifacts at
http://people.apache.org/~samisa/release/1.0.0/final/

  The key used to sign the release artifacts can be found at
http://www.apache.org/dist/ws/axis2/c/KEYS


  Please test, review and vote on these latest release artifacts for 
Apache Axis2/C 1.0.0 release.


  I have tested and reviewed them and here is my vote: +1

Thanks,
Samisa...







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

empty Values in Soap document produces an error

2007-05-03 Thread lars.schumacher

Hi ,   

I have a problem with my webservice. He receive an Soap Document, with
the following structure You find it at the end of the Mail(for example).
If AXIS reads the password of the Auth object, occurs an error and the
Auth object won't prepared. The problem is that the text_value is emty
and AXIS don't understand this. I have change my Source Code of the
axiom_element_get_text Method to:   if(om_element-text_value == NULL )
om_element-text_value = ;  It works, but i don't know have it effect
of the rest of AXIS2C. Can someone check it this okay. If yes, can it
included in the source code of AXIS2? The same problem is by
axutil_array_list_size. My example is after the SOAP Document. 

soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing;
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wsse
curity-secext-1.0.xsd xmlns:wsu=http://docs.oasis-
open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd 
soap:Header
wsa:Action / 
wsa:MessageIDurn:uuid:7b21bdf8-6f69-44a1-b44c-cde2d1ffa8ff/wsa:Messag
eID 
wsa:ReplyTo 
wsa:Addresshttp://schemas.xmlsoap.org/ws/2004/08/addressing/role/anony
mous/wsa:Address 
/wsa:ReplyTo 
wsa:Tohttp://localhost:9090/axis2/services/ttwebservicesaxis/wsa:To 
 wsse:Security 
wsu:Timestamp wsu:Id=Timestamp-5156341c-db2d-4e83-a0d7-01f48a1eecf7 
wsu:Created2007-05-03T08:40:48Z/wsu:Created 
wsu:Expires2007-05-03T08:45:48Z/wsu:Expires 
/wsu:Timestamp 
/wsse:Security 
/soap:Header 
soap:Body 
GenerateUUID xmlns=urn:ttwebservices 
auth 
userIdbill/userId 
password / 
hostname xsi:nil=true / 
/auth 
/GenerateUUID 
/soap:Body 
/soap:Envelope

AXIS2_EXTERN int AXIS2_CALL 
axutil_array_list_size(struct axutil_array_list *array_list, 
const axutil_env_t *env)
{
AXIS2_ENV_CHECK(env, AXIS2_FAILURE);
if(array_list == NULL)
  return 0;
return array_list-size;
}

Regards Lars

Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release

2007-05-03 Thread Chris Darroch

Samisa Abeysinghe wrote:

Please test, review and vote on these latest release artifacts for 
 Apache Axis2/C 1.0.0 release.

   Compiles, tests, and installs like a charm -- thank you!  I've
run axis2_http_server and pinged the sample clients off it.  I also
quickly tried mod_axis2 with httpd 2.2.3 and the samples worked there
too.  So, +1 from me, and thanks again,

Chris.

-- 
GPG Key ID: 366A375B
GPG Key Fingerprint: 485E 5041 17E1 E2BB C263  E4DE C8E3 FA36 366A 375B


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [Vote 2] [Axis2] Vote for Apache Axis2/C 1.0.0 Release

2007-05-03 Thread Dumindu Pallewela


Tested both linux/win32 sources for SSL client. It works fine.

+1 for the release.

Thanks,
Dumindu.


Samisa Abeysinghe wrote:

Hi Devs,

  After fixing the issues found with the initial release artifacts, I 
have re-packaged and uploaded the Apache Axis2/C 1.0.0 release

artifacts at
http://people.apache.org/~samisa/release/1.0.0/final/

  The key used to sign the release artifacts can be found at
http://www.apache.org/dist/ws/axis2/c/KEYS


  Please test, review and vote on these latest release artifacts for 
Apache Axis2/C 1.0.0 release.


  I have tested and reviewed them and here is my vote: +1

Thanks,
Samisa...







-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2631) WSDL2Java: WSDLProcessingException: Encoded use is not supported?

2007-05-03 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi commented on AXIS2-2631:
-

Axis2 does not support encoding. Could you send and recieve messages (soap 
encoded) correctly with the Axis2 1.1.1?

 WSDL2Java: WSDLProcessingException: Encoded use is not supported?
 -

 Key: AXIS2-2631
 URL: https://issues.apache.org/jira/browse/AXIS2-2631
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.2
 Environment: Windows XP
Reporter: wolverine
Priority: Minor

 I encounter the following error when tried to generate web service
 client using Axis2 1.2 and XMLBeans:
 WSDL2Java -uri Dummy.wsdl -p com.test.dummy -d xmlbeans -s
 Using AXIS2_HOME:   C:\axis2-1.2
 Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_11
 May 2, 2007 11:37:18 AM
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder
 populateService
 SEVERE: 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
 Encoded use is not supported
 Exception in thread main
 org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing
 WSDL
   at 
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:137)
   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 Caused by: org.apache.axis2.AxisFault: Encoded use is not supported
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:298)
   at 
 org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:100)
   at 
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:131)
   ... 2 more
 Caused by: 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
 Encoded use is not supported
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getPartsListFromSoapBody(WSDL11ToAxisServiceBuilder.java:1543)
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToAxisServiceBuilder.java:1294)
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxisServiceBuilder.java:1198)
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:252)
   ... 4 more
 Note that the same command and WSDL file was working fine with Axis2 1.1.1.
 The following is the complete WSDL file:
 ?xml version='1.0' encoding='UTF-8' ? 
 !-- Generated 10/01/05 by Microsoft SOAP Toolkit WSDL File Generator -- 
 definitions  name ='CPA'   targetNamespace = 'http://myns/wsdl/'
xmlns:wsdlns='http://myns/wsdl/' 
xmlns:typens='http://mynsi.org/type' 
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' 
xmlns:xsd='http://www.w3.org/2001/XMLSchema' 
xmlns:stk='http://schemas.microsoft.com/soap-toolkit/wsdl-extension'
xmlns='http://schemas.xmlsoap.org/wsdl/' 
   types
 schema targetNamespace='http://mynsi.org/type'
   xmlns='http://www.w3.org/2001/XMLSchema'
   xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
   xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
   elementFormDefault='qualified'
 /schema
   /types
   message name='clsCPA.deliverMTMessage'
 part name='ApplicationId' type='xsd:short'/
 part name='Login' type='xsd:string'/
 part name='Password' type='xsd:string'/
 part name='MessageTerminatingID' type='xsd:double'/
 part name='MessageOriginatingLinkID' type='xsd:double'/
 part name='ChargeMSISDN' type='xsd:string'/
 part name='ReceiverMSISDN' type='xsd:string'/
 part name='ShortCode' type='xsd:string'/
 part name='MessageCount' type='xsd:short'/
 part name='DateTime' type='xsd:string'/
 part name='MessageScheduleFlag' type='xsd:short'/
 part name='MessageScheduleTime' type='xsd:string'/
 part name='BillType' type='xsd:short'/
 part name='BillServiceId' type='xsd:int'/
 part name='BillPrice' type='xsd:short'/
 part name='IsFlash' type='xsd:short'/
 part name='MessageContentType' type='xsd:string'/
 part name='MessageType' type='xsd:string'/
 part name='Message' type='xsd:anyType'/
 part name='MessageExpiryTime' type='xsd:short'/
   /message
   message name='clsCPA.deliverMTMessageResponse'
 part name='Result' type='xsd:string'/
   /message
   message name='clsCPA.DeliverChineseMessage'
 part name='ApplicationId' type='xsd:short'/
 part name='Login' type='xsd:string'/
 part name='Password' type='xsd:string'/
 part name='MessageTerminatingID' type='xsd:double'/
 part name='MessageOriginatingLinkID'

[jira] Created: (AXIS2-2632) Issues in ws.apache.org/axis2 site

2007-05-03 Thread Charitha Kankanamge (JIRA)

Issues in ws.apache.org/axis2 site
--

 Key: AXIS2-2632
 URL: https://issues.apache.org/jira/browse/AXIS2-2632
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples, build,site
Affects Versions: 1.2
 Environment: FireFox
Reporter: Charitha Kankanamge


Following issues were encountered in axis2 web site.

1. Blank pages appear when issuing following urls

http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html 
http://ws.apache.org/axis2/tools/1_2/eclipse/wsdl2java-plugin.html
http://ws.apache.org/axis2/tools/1_2/eclipse/servicearchiver-plugin.html
http://ws.apache.org/axis2/tools/1_2/idea/Idea_plug-in_userguide.html
http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-aar-plugin.html
http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-java2wsdl-plugin.html
http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-wsdl2code-plugin.html
http://ws.apache.org/axis2/1_2/api/index.html

2. Architectural Overview image is corrupted in 
http://ws.apache.org/axis2/1_2/adb/adb-howto.html

3. 'html' appears in http://ws.apache.org/axis2/1_2/rest-ws.html page


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-2633) axis2-wsdl2code-maven-plugin missing extension option bindingfile for JiBX

2007-05-03 Thread Armin Ehrenfels (JIRA)

axis2-wsdl2code-maven-plugin missing extension option bindingfile for JiBX


 Key: AXIS2-2633
 URL: https://issues.apache.org/jira/browse/AXIS2-2633
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2
 Environment: all platforms
Reporter: Armin Ehrenfels


axis2-wsdl2code-maven-plugin doesn't support extension options such as 
-Ebindingfile for JiBX.

SUGGESTION:
1. in the plugin configuration, introducing an additional option 
extensionOptions, similar to namespaceURIs, like this:
 
extensionOptions
   extensionOption
   namexxx/name
  valueyyy/value
  /extensionOption
  ...
/extensionOptions 

2. in the mojo, for each extension option adding the name/value pair to 
optionsMap. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-2634) When several requests are processed simultaneously, parent nodes are mixed

2007-05-03 Thread Eugeny Tretiakov (JIRA)

When several requests are processed simultaneously, parent nodes are mixed
--

 Key: AXIS2-2634
 URL: https://issues.apache.org/jira/browse/AXIS2-2634
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
Affects Versions: 1.1.1
Reporter: Eugeny Tretiakov


Problem description:
2 simultaneous requests (SOAP-Envelopes) are sent to 2 different
web-services. Expected responses are:
First:
 aaaResponse
res1/res
 /aaaResponse
Second:
 bbbResponse
result2/result
 /bbbResponse
Instead we get responses like:
First:
 bbbResponse
res1/res
 /bbbResponse
Second:
 aaaResponse
result2/result
 /aaaResponse
===
Fix description:
Class org.apache.axis2.rpc.receivers.RPCMessageReceiver;
Global variable of the class -  private Method method
was moved into the method invokeBusinessLogic

Besides the class org.apache.axis2.rpc.receivers.RPCUtil was changed (the
problem was in processResponse methods: it receives Method method parameter
while it uses only method name.

After applying the changes the classes look as follows:
=
после изменений классы приняли вид:
/*
* Copyright 2004,2005 The Apache Software Foundation.
*
* Licensed under the Apache License, Version 2.0 (the License);
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
*  http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/

/*
* Reflection based RPCMessageReceiver , request will be processed by looking at 
the method signature
* of the invocation method
*/
package org.apache.axis2.rpc.receivers;

import org.apache.axiom.om.OMElement;
import org.apache.axiom.om.OMNamespace;
import org.apache.axiom.soap.SOAPEnvelope;
import org.apache.axiom.soap.SOAPFactory;
import org.apache.axis2.AxisFault;
import org.apache.axis2.context.MessageContext;
import org.apache.axis2.description.AxisMessage;
import org.apache.axis2.description.AxisOperation;
import org.apache.axis2.description.AxisService;
import org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver;
import org.apache.axis2.wsdl.WSDLConstants;

import javax.xml.namespace.QName;
import java.lang.reflect.InvocationTargetException;
import java.lang.reflect.Method;

public class RPCMessageReceiver extends AbstractInOutSyncMessageReceiver {


/**
 * reflect and get the Java method
 * - for each i'th param in the java method
 * - get the first child's i'th child
 * -if the elem has an xsi:type attr then find the deserializer for it
 * - if not found,
 * lookup deser for th i'th param (java type)
 * - error if not found
 * - deserialize  save in an object array
 * - end for
 * p/
 * - invoke method and get the return value
 * p/
 * - look up serializer for return value based on the value and type
 * p/
 * - create response msg and add return value as grand child of soap:body
 *
 * @param inMessage
 * @param outMessage
 * @throws AxisFault
 */


public void invokeBusinessLogic(MessageContext inMessage, MessageContext 
outMessage) throws AxisFault {
Method method = null;
try {

// get the implementation class for the Web Service
Object obj = getTheImplementationObject(inMessage);

Class ImplClass = obj.getClass();

AxisOperation op = 
inMessage.getOperationContext().getAxisOperation();
AxisService service = inMessage.getAxisService();
OMElement methodElement = inMessage.getEnvelope().getBody()
.getFirstElement();
AxisMessage inAxisMessage = 
op.getMessage(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
String messageNameSpace = null;
QName elementQName;
String methodName = op.getName().getLocalPart();
Method[] methods = ImplClass.getMethods();
for (int i = 0; i  methods.length; i++) {
if (methods[i].getName().equals(methodName)) {
method = methods[i];
break;
}
}

Object resObject = null;
if (inAxisMessage != null) {
if (inAxisMessage.getElementQName() == null) {
// method accept empty SOAPbody
resObject = method.invoke(obj, new Object[0]);
} else {
elementQName = inAxisMessage.getElementQName();

[jira] Commented: (AXIS2-1473) org.apache.axis2.AxisFault: Connection reset - connections are not closing for long time

2007-05-03 Thread Chris (JIRA)


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

Chris commented on AXIS2-1473:
--

I have a work-around for the problem with a change to the 
org.apache.axis2.transport.http.AbstractHTTPSender class in 
axis2-kernel-1.2.jar. 

At the end of the getHttpClient method, before the   return httpClient; 
statement I have inserted the following:


HttpMethodRetryHandler myretryhandler = new HttpMethodRetryHandler() {
  public boolean retryMethod(
  final HttpMethod method, 
  final IOException exception, 
  int executionCount) {
  if (executionCount = 5) {
  // Do not retry if over max retry count
  return false;
  }
  if (exception instanceof SocketException) {
log.warn(retry  + executionCount + after 
SocketException,exception);
//  Retry if the server dropped connection on us
return true;
  }
  
  
  if (exception instanceof NoHttpResponseException) {
  // Retry if the server dropped connection on us
  return true;
  }
  if (!method.isRequestSent()) {
  // Retry if the request has not been sent fully or
  // if it's OK to retry methods that have been sent
  return true;
  }
  
  
  // otherwise do not retry
  return false;
  }
  };
  
  httpClient.getParams().
  setParameter(HttpMethodParams.RETRY_HANDLER, myretryhandler);

I am not familiar with the intenals of axis so I do not know if there is a 
better way of doing this, and do not know how to make it a settable 
configuration parameter. I will attach my changed source file and patched jar 
file for others to try.

 org.apache.axis2.AxisFault: Connection reset - connections are not closing 
 for long time
 

 Key: AXIS2-1473
 URL: https://issues.apache.org/jira/browse/AXIS2-1473
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: client-api, codegen
Affects Versions: nightly
 Environment: Client in Windows XP SP2, jdk 1.5, Axis2 1.1 Nightly 
 build(October 20, 2006), Microsoft SQL Reporting Services 2005 in Windows XP, 
 JVM Heap settings : -Xrs -Xmx700M -Xms512M.., Memory :1 GB
Reporter: GNANASEKARAN VINAYAKAMURTHY
 Assigned To: Deepal Jayasinghe
Priority: Critical
 Attachments: Connection-reset-exeption.txt, netstat-output.doc, 
 reportexecution2005.wsdl, reportservice2005.wsdl, SSRS-Main.zip


 Getting connection reset problem in Axis2 1.1 Nightly, when I try to make web 
 service calls to .Net client (MS Reporting services in XP) again and 
 again But it works fine when called at initial couple of times... I think 
 system breaks, when we make web service call at 5th consecutive time. 
 I am trying to create web application with axis2, where I could show all the 
 reports and folders from MS reporting services.
 Axis2 client and .Net web service server(MS Reporting services) are running 
 on windows platform and I just tried using 'netstat -a' in the system, where 
 my Axis2 client is running and  found that connections made by Axis2 were not 
 closing for long time.. I think Axis2 is not closing the socket 
 connections after end of web service calls in client side.
 I have also attached the following with this,
 1. Netstat output
 2. Exception stack trace
 3. wsdl files
 4. Source code
 Please let me know about how could we close connections completely from Axis2 
 or how to fix this?
 Thanks,

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2578) Problems with ADB Client and XMLBeans Service

2007-05-03 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi commented on AXIS2-2578:
-

this is a issue with the xml beans

the parameterDependencies element in the returned xmlbean document like this
  parameterDependencies
nameprimitive0/name
signalDependencies
namesignal0/name
/signalDependencies
signalDependencies
namesignal1/name
/signalDependencies
typeprimitiveType0/type
unitsunits0/units
max2/max
min1/min
/parameterDependencies

here the parameterDependencies element is a parameter type but you actually 
sends the primitiveParameter type. In this case it has to specify the actualy 
type used.

See the return value from adb server.

parameterDependencies xsi:type=:PrimitiveParameter
nameprimitive0/name
signalDependencies
   namesignal0/name
/signalDependencies
signalDependencies
   namesignal1/name
/signalDependencies
typeprimitiveType0/type
unitsunits0/units
max2/max
min1/min
 /parameterDependencies

it specify the actuall type and this can be used to retrieve the correct value 
at the client side.
(ADB also has a problem with printing a : when namespace prefix is null, but 
this works with the adb client fine) 

So it seems to be an xmlbeans problem. 
in your generated xmlbeans Document you have
GetDetailedMonitoringStagesResponseDocument class and it has two methods called 
save and Factory.parse. 
So can you try to save your object structure with the save method and reparse 
with the Factor.parse method and check the second object structure with the 
first .
See whether the polymorphism has worked correctly.

if not please report this bug to xmlbeans. you can generate databinding objects 
directly with the xmlbeans using the scomp command.

 Problems with ADB Client and XMLBeans Service
 -

 Key: AXIS2-2578
 URL: https://issues.apache.org/jira/browse/AXIS2-2578
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
Affects Versions: 1.1.1
 Environment: Windows XP SP2, Java 1.5.0-11, Eclipse Codegenerator 
 plugin 1.2.1
Reporter: Jorge Fernández
 Assigned To: Amila Chinthaka Suriarachchi
 Attachments: API.wsdl, APISkeleton.java, APISkeletonXmlBeans.java, 
 Client.java, ClientXmlBeans.java


 This JIRA is related with the message from the mailing list Issue with ADB 
 and parsing a response message (namespaces)
 I couldn't reproduce the problem I described in that email but when I fixed 
 that problem I found another one and this is which I'm reporting.
 First, some introduction.
 In my response message there is an array of  Stages which have one or more 
 Configurations. Each Configuration has AbstractParameters and 
 PrimitiveParameters (that inherit from Parameter). Also each Parameter may 
 depend on other so the class Parameter has an array of Parameter called 
 dependencies.
 My problem happens only if I have ADB at client side and XMLBeans at service 
 side. Any other combination works perfectly. (I attach the wsdl and client 
 and service for both databindings).
 When my ADB client parses the response message, it enters Stage.Factory.parse 
 method, then it enters, Configuration.Factory.parse method. Next, 
 AbstractParameter.Factory.parse method (because the first parameter is 
 abstract) and later it want to parse the dependencies of this parameter so it 
 enters Parameter.Factory.parse method. Here, there is a PrimitiveParameter 
 with no dependencies on oher parameters so it enters Signal.Factory.parse 
 method for getting signal dependencies. It returns ok
 Finally, the problem comes out when after getting SignalDependencies from 
 this PrimitiveParameter, it gets the Type element which is in the Parameter 
 class and now there is the gain element that is part of PrimitiveParameter 
 and not of his parent. so it throws an exception because it didn't expect it.
 Hope this explanation could be useful but if not, the wsdl could be.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe,

[jira] Updated: (AXIS2-1473) org.apache.axis2.AxisFault: Connection reset - connections are not closing for long time

2007-05-03 Thread Chris (JIRA)

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

Chris updated AXIS2-1473:
-

Attachment: axis2-kernel-1.2.jar

kernel jar patched with my code changes to AbstractHTTPSender.

org.apache.axis2.AxisFault: Connection reset - connections are not closing
for long time

Key: AXIS2-1473
URL: https://issues.apache.org/jira/browse/AXIS2-1473
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: client-api, codegen
Affects Versions: nightly
Environment: Client in Windows XP SP2, jdk 1.5, Axis2 1.1 Nightly
build(October 20, 2006), Microsoft SQL Reporting Services 2005 in Windows XP,
JVM Heap settings : -Xrs -Xmx700M -Xms512M.., Memory :1 GB
Reporter: GNANASEKARAN VINAYAKAMURTHY
Assigned To: Deepal Jayasinghe
Priority: Critical
Attachments: AbstractHTTPSender.java, axis2-kernel-1.2.jar,
Connection-reset-exeption.txt, netstat-output.doc, reportexecution2005.wsdl,
reportservice2005.wsdl, SSRS-Main.zip

Getting connection reset problem in Axis2 1.1 Nightly, when I try to make web
service calls to .Net client (MS Reporting services in XP) again and
again But it works fine when called at initial couple of times... I think
system breaks, when we make web service call at 5th consecutive time.
I am trying to create web application with axis2, where I could show all the
reports and folders from MS reporting services.
Axis2 client and .Net web service server(MS Reporting services) are running
on windows platform and I just tried using 'netstat -a' in the system, where
my Axis2 client is running and found that connections made by Axis2 were not
closing for long time.. I think Axis2 is not closing the socket
connections after end of web service calls in client side.
I have also attached the following with this,
1. Netstat output
2. Exception stack trace
3. wsdl files
4. Source code
Please let me know about how could we close connections completely from Axis2
or how to fix this?
Thanks,

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS-2658) OctetStreamDataSource with an arbitrary content type

2007-05-03 Thread Akitoshi Yoshida (JIRA)

OctetStreamDataSource with an arbitrary content type


 Key: AXIS-2658
 URL: https://issues.apache.org/jira/browse/AXIS-2658
 Project: Axis
  Issue Type: Improvement
  Components: Basic Architecture
Affects Versions: 1.4
 Environment: JDK 1.4.2
Windows XP
Reporter: Akitoshi Yoshida
Priority: Minor
 Fix For: 1.4


We would like to have a message ( org.apache.axis.Message ) that we can 
serialize (i.e., using its writeTo(OutputStream) method)  more than once. 

We noticed that when attachments are instantiated with the 
org.apache.axis.attachments.ManagedMemoryDataSource class, they will be removed 
after serialization in the writeContentToStream(java.io.OutputStream os) method 
of org.apache.axis.attachments.AttachmentsImpl class. When this message is 
serialized again, it results in an IOException (not thrown but logged) saying 
that the resource is deleted.

If the org.apache.axis.attachments.OctetStreamDataSource class can be changed 
to take a variable content type, we can use this data source class to replace 
those attachments in a handler.

This will look like:
...
private String contentType;
...

public OctetStreamDataSource(String name, OctetStream data) {
this(name, CONTENT_TYPE, data);
}

public OctetStreamDataSource(String name, String contentType, OctetStream 
data) {
this.name = name;
this.contentType = contentType; 
this.data = data == null ? null : data.getBytes();
os = new ByteArrayOutputStream();
} // ctor

...
public String getContentType() {
return contentType;
} // getContentType


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS-2658) OctetStreamDataSource with an arbitrary content type

2007-05-03 Thread Akitoshi Yoshida (JIRA)


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

Akitoshi Yoshida updated AXIS-2658:
---

Attachment: OctetStreamDataSource.zip

 OctetStreamDataSource with an arbitrary content type
 

 Key: AXIS-2658
 URL: https://issues.apache.org/jira/browse/AXIS-2658
 Project: Axis
  Issue Type: Improvement
  Components: Basic Architecture
Affects Versions: 1.4
 Environment: JDK 1.4.2
 Windows XP
Reporter: Akitoshi Yoshida
Priority: Minor
 Fix For: 1.4

 Attachments: OctetStreamDataSource.zip


 We would like to have a message ( org.apache.axis.Message ) that we can 
 serialize (i.e., using its writeTo(OutputStream) method)  more than once. 
 We noticed that when attachments are instantiated with the 
 org.apache.axis.attachments.ManagedMemoryDataSource class, they will be 
 removed after serialization in the writeContentToStream(java.io.OutputStream 
 os) method of org.apache.axis.attachments.AttachmentsImpl class. When this 
 message is serialized again, it results in an IOException (not thrown but 
 logged) saying that the resource is deleted.
 If the org.apache.axis.attachments.OctetStreamDataSource class can be changed 
 to take a variable content type, we can use this data source class to replace 
 those attachments in a handler.
 This will look like:
 ...
 private String contentType;
 ...
 public OctetStreamDataSource(String name, OctetStream data) {
 this(name, CONTENT_TYPE, data);
 }
 public OctetStreamDataSource(String name, String contentType, OctetStream 
 data) {
 this.name = name;
 this.contentType = contentType;   
 this.data = data == null ? null : data.getBytes();
 os = new ByteArrayOutputStream();
 } // ctor
 ...
 public String getContentType() {
 return contentType;
 } // getContentType

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2607) MessageContext.getProperty does not work correctly

2007-05-03 Thread Glen Daniels (JIRA)


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

Glen Daniels commented on AXIS2-2607:
-

1) Shouldn't the ContextHierarchyTest be checking this?  When I looked in 
testCompleteHiracy (sic) I didn't see this exact test, so I added a couple of 
lines to confirm that it works, and it seems to (will check in, along with 
spelling fixes).  Did you fix this already?

2) Could you explain more about what you mean, and perhaps include a test case? 
:)


 MessageContext.getProperty does not work correctly 
 ---

 Key: AXIS2-2607
 URL: https://issues.apache.org/jira/browse/AXIS2-2607
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Deepal Jayasinghe
 Assigned To: Deepal Jayasinghe
Priority: Blocker

 When I store some property  in ServiceContext and try to get that from 
 MessageContext it always returns null. When I look at the code I found the 
 issue. AFAIK this is a major issue and I think we need to release 1.2.1 with 
 the fix.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2609) Incorrectly generated stub functions

2007-05-03 Thread Gul Onural (JIRA)

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

Gul Onural commented on AXIS2-2609:
---

This behavior has changed since Axis2 1.1, where I didn't have to
specify empty string in the
body part. Omitting body (no soap:body parts= use=literal/) in the
input worked with Axis2 1.1.

Have you had a chance to test if body parts= works with axis2 1.2?

Gul

Incorrectly generated stub functions
-

Key: AXIS2-2609
URL: https://issues.apache.org/jira/browse/AXIS2-2609
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: codegen
Affects Versions: 1.2
Reporter: Gul Onural
Assigned To: Amila Chinthaka Suriarachchi
Priority: Blocker
Attachments: test.zip

The release 1.2 wsdl2 java generates incorrect stub functions for the
operations that has header part only, no payload.
This was correctly done with version axis2 1.1.1. Something changed in
between the two releases in this area is causing the problem.
For example, operation and message are defined something similar to :
operation name=queryX
input message=queryXRequest/
output message=queryXResponse/
/operation
message name=queryXRequest
part name=header element=id/
/message
The generated stubs contains the id twice :
public com.mycompany.QueryXResponseDocument queryX(
com.mycompany.IdDocument id2,
com.mycompany.IdDocument id3)
throws java.rmi.RemoteException
{
...
}

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2607) MessageContext.getProperty does not work correctly


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

Deepal Jayasinghe commented on AXIS2-2607:
--

Yes , Context hierarchy should do that. Unfortunately with option concept 
everything has gone wrong . That is why that we need to have logic in message 
context to do the right thing , I know we had the correct code but some one has 
removed that , w.o knowing what he is doing. I agree that we need to add test 
cases to test them.

I will add a test case . , so that no one will be able to break that.

 MessageContext.getProperty does not work correctly 
 ---

 Key: AXIS2-2607
 URL: https://issues.apache.org/jira/browse/AXIS2-2607
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Deepal Jayasinghe
 Assigned To: Deepal Jayasinghe
Priority: Blocker

 When I store some property  in ServiceContext and try to get that from 
 MessageContext it always returns null. When I look at the code I found the 
 issue. AFAIK this is a major issue and I think we need to release 1.2.1 with 
 the fix.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

2007-05-03 Thread Sathija Pavuluri

Deepal,

I had earlier posted a question about the codegen issue you mentioned after 
patches for AXIS2-2055 were applied.
I have since built the codegen module with the patch and didnt notice any issue 
and nor were there any issues
building any of other axis2 modules.
So I am still puzzled by what issue the patch may have caused. Would you please 
elaborate on that issue you mentioned the patch had caused. 

Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but they are 
in fact not, because of the patch reversal.

Thanks.
Sathija.



- Original Message 
From: Deepal Jayasinghe [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Friday, April 27, 2007 12:10:41 PM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Yes , there was an issue with the codegen , so I had to revert that.

Thanks
Deepal

Sathija Pavuluri wrote:

 Deepal,

 Noticed that the patches were applied and then reverted on the 1.2 branch?
 Was anything wrong?

 Thanks
 Sathija.


 - Original Message 
 From: Deepal Jayasinghe [EMAIL PROTECTED]
 To: axis-dev@ws.apache.org
 Sent: Friday, April 27, 2007 12:16:05 AM
 Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

 Done , thx very much for your patches.

 Thanks
 Deepal


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



 
 Ahhh...imagining that irresistible new car smell?
 Check out new cars at Yahoo! Autos.
 http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-



-- 
Thanks,
Deepal

The highest tower is built one brick at a time



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Hi Sathija ,

Once I applied your patch , it broke the Axis2 samples. I think Caritha
will be able to answer this better than me , since he is the one who
find the bug :)

Thanks
Deepal

Deepal,

I had earlier posted a question about the codegen issue you mentioned
after patches for AXIS2-2055 were applied.
I have since built the codegen module with the patch and didnt notice
any issue and nor were there any issues
building any of other axis2 modules.
So I am still puzzled by what issue the patch may have caused. Would
you please elaborate on that issue you mentioned the patch had caused.

Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but
they are in fact not, because of the patch reversal.

Thanks.
Sathija.

- Original Message
From: Deepal Jayasinghe [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Friday, April 27, 2007 12:10:41 PM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Yes , there was an issue with the codegen , so I had to revert that.

Thanks
Deepal

Sathija Pavuluri wrote:

Deepal,

Noticed that the patches were applied and then reverted on the 1.2
branch?
Was anything wrong?

Thanks
Sathija.

- Original Message
From: Deepal Jayasinghe [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Friday, April 27, 2007 12:16:05 AM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Done , thx very much for your patches.

Thanks
Deepal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ahhh...imagining that irresistible new car smell?
Check out new cars at Yahoo! Autos.

http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-

--
Thanks,
Deepal

The highest tower is built one brick at a time

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ahhh...imagining that irresistible new car smell?
Check out new cars at Yahoo! Autos.
http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-

--
Thanks,
Deepal

The highest tower is built one brick at a time

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Missing SVN tag for Axis2 1.2

2007-05-03 Thread Alex Boisvert


Guys, just a friendly reminder but we're still missing a SVN tag for 1.2.

thanks,
alex


On 4/30/07, Alex Boisvert [EMAIL PROTECTED] wrote:



Has a SVN tag been created for Axis2 1.2 ?   I do not see one in the usual
place:

[EMAIL PROTECTED]:~/svn/axis2$ svn ls
http://svn.apache.org/repos/asf/webservices/axis2/tags/java
rampart_1_1/
v0.94/
v0.95/
v1.0/
v1.1/
v1.1.1/

thanks,
alex

[axis2] Re: svn commit: r534865 - in /webservices/axis2/trunk/java/modules/kernel/src/org/apache/axis2/client: OperationClient.java ServiceClient.java

2007-05-03 Thread Glen Daniels


[switching over to axis-dev and adding prefix]

Hi folks!

Deepal wrote:
Why do you want to do such a thing ? , does anyone ask for a  feature
like this ?
As I can see you are breaking Axis2 concepts.

Deepal, I'm not sure what you meant by breaking Axis2 concepts either?

Davanum Srinivas wrote:

Is this for the Stub scenario where we automatically save the oc so
that the user can get to it when the invocation is over?


Yes, but also for the DII scenario where you just use a ServiceClient or 
OperationClient directly.  The version Deepal and I put in before was 
specifically for use in stubs, but I found that I needed the same 
functionality in a DII test, so it makes much more sense to implement it 
generically, where it should work for both Stubs and DII.


I actually put it in the wrong place - it shouldn't be in the 
constructor, it should be in execute(), so that it really is last 
operation context executed instead of last operation context created. 
 As such I'm making execute() a final method in the abstract 
OperationClient class, and renaming the abstract method executeImpl(). 
Just made this change, testing it now.  I'll also make sure we have a 
test or two for this.


I didn't find any references to setLastOperationContext() anywhere in 
our source tree, including in the stub generation templates... Did the 
stub-related version of this functionality disappear at some point? 
(perhaps this is why that JIRA got filed)


Thanks,
--Glen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2607) MessageContext.getProperty does not work correctly

2007-05-03 Thread Glen Daniels (JIRA)


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

Glen Daniels commented on AXIS2-2607:
-

Hi Deepal. :)

OK, take a deep breath and please explain what you mean here IN DETAIL.  Your 
description isn't very helpful right now.  Please describe the exact problem 
(what exactly is going wrong, what code are you talking about, how does Options 
affect it) so that we have it archived and everyone can understand it.  Thanks!

 MessageContext.getProperty does not work correctly 
 ---

 Key: AXIS2-2607
 URL: https://issues.apache.org/jira/browse/AXIS2-2607
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Deepal Jayasinghe
 Assigned To: Deepal Jayasinghe
Priority: Blocker

 When I store some property  in ServiceContext and try to get that from 
 MessageContext it always returns null. When I look at the code I found the 
 issue. AFAIK this is a major issue and I think we need to release 1.2.1 with 
 the fix.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

2007-05-03 Thread Davanum Srinivas

Deepal,

Can you please reopen the bugs?

thanks,
dims

On 5/3/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:

Hi Sathija ,

Once I applied your patch , it broke the Axis2 samples. I think Caritha
will be able to answer this better than me , since he is the one who
find the bug :)

Thanks
Deepal

Deepal,

Also, the issues AXIS2-2055 and AXIS2-1899 are marked as resolved, but
they are in fact not, because of the patch reversal.

Thanks.
Sathija.

- Original Message
From: Deepal Jayasinghe [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Friday, April 27, 2007 12:10:41 PM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Yes , there was an issue with the codegen , so I had to revert that.

Thanks
Deepal

Sathija Pavuluri wrote:

Deepal,

Noticed that the patches were applied and then reverted on the 1.2
branch?
Was anything wrong?

Thanks
Sathija.

- Original Message
From: Deepal Jayasinghe [EMAIL PROTECTED]
To: axis-dev@ws.apache.org
Sent: Friday, April 27, 2007 12:16:05 AM
Subject: Re: Patches provided for issues AXIS2-2055 and AXIS2-1899

Done , thx very much for your patches.

Thanks
Deepal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ahhh...imagining that irresistible new car smell?
Check out new cars at Yahoo! Autos.

http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-

--
Thanks,
Deepal

The highest tower is built one brick at a time

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ahhh...imagining that irresistible new car smell?
Check out new cars at Yahoo! Autos.

http://us.rd.yahoo.com/evt=48245/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE1YW1jcXJ2BF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDbmV3LWNhcnM-

--
Thanks,
Deepal

The highest tower is built one brick at a time

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2607) MessageContext.getProperty does not work correctly


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

Deepal Jayasinghe commented on AXIS2-2607:
--

Hi Glen,

I had a written a session aware sample as you can see below [1] , the sample 
worked fine in Axis2 1.1 but when I tried to run the same sample in 1.2 it was 
giving error. The issue I found is in the service side we are not setting up 
the parent correctly so the logic in the AbstartcContext always returns null 
[2].

[1]
public class SampleService4 {

private static String INT_VALUE = value;

public void init(ServiceContext serviceContext) {
System.out.println(I am inside service init method);
//setting a property
serviceContext.setProperty(INT_VALUE, 0);
}

public void destroy(ServiceContext serviceContext) {
System.out.println(I am inside service destroy );
}


public int add(int value) {
MessageContext msgctx = MessageContext.getCurrentMessageContext();
String intValue = (String) msgctx.getProperty(INT_VALUE);
int previousValue =0;
if(intValue!=null){
previousValue = Integer.parseInt(intValue);
}
int currentValue = previousValue + value;
msgctx.getServiceContext().setProperty(INT_VALUE,  + currentValue);
return currentValue;
}
}


[2] -
 public Object getProperty(String key) {
Object obj;

obj = properties == null ? null : properties.get(key);

if ((obj == null)  (parent != null)) {
obj = parent.getProperty(key);
}

return obj;
}

I think setting up the parent will fix the issue. I need to look at SVN history 
to find out the changes b/w 1.1 and 1.2. 


 MessageContext.getProperty does not work correctly 
 ---

 Key: AXIS2-2607
 URL: https://issues.apache.org/jira/browse/AXIS2-2607
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Deepal Jayasinghe
 Assigned To: Deepal Jayasinghe
Priority: Blocker

 When I store some property  in ServiceContext and try to get that from 
 MessageContext it always returns null. When I look at the code I found the 
 issue. AFAIK this is a major issue and I think we need to release 1.2.1 with 
 the fix.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (AXIS2-2634) When several requests are processed simultaneously, parent nodes are mixed


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

Deepal Jayasinghe reassigned AXIS2-2634:


Assignee: Deepal Jayasinghe

 When several requests are processed simultaneously, parent nodes are mixed
 --

 Key: AXIS2-2634
 URL: https://issues.apache.org/jira/browse/AXIS2-2634
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
Affects Versions: 1.1.1
Reporter: Eugeny Tretiakov
 Assigned To: Deepal Jayasinghe

 Problem description:
 2 simultaneous requests (SOAP-Envelopes) are sent to 2 different
 web-services. Expected responses are:
 First:
  aaaResponse
 res1/res
  /aaaResponse
 Second:
  bbbResponse
 result2/result
  /bbbResponse
 Instead we get responses like:
 First:
  bbbResponse
 res1/res
  /bbbResponse
 Second:
  aaaResponse
 result2/result
  /aaaResponse
 ===
 Fix description:
 Class org.apache.axis2.rpc.receivers.RPCMessageReceiver;
 Global variable of the class -  private Method method
 was moved into the method invokeBusinessLogic
 Besides the class org.apache.axis2.rpc.receivers.RPCUtil was changed (the
 problem was in processResponse methods: it receives Method method parameter
 while it uses only method name.
 After applying the changes the classes look as follows:
 =
 после изменений классы приняли вид:
 /*
 * Copyright 2004,2005 The Apache Software Foundation.
 *
 * Licensed under the Apache License, Version 2.0 (the License);
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *  http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an AS IS BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
 /*
 * Reflection based RPCMessageReceiver , request will be processed by looking 
 at the method signature
 * of the invocation method
 */
 package org.apache.axis2.rpc.receivers;
 import org.apache.axiom.om.OMElement;
 import org.apache.axiom.om.OMNamespace;
 import org.apache.axiom.soap.SOAPEnvelope;
 import org.apache.axiom.soap.SOAPFactory;
 import org.apache.axis2.AxisFault;
 import org.apache.axis2.context.MessageContext;
 import org.apache.axis2.description.AxisMessage;
 import org.apache.axis2.description.AxisOperation;
 import org.apache.axis2.description.AxisService;
 import org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver;
 import org.apache.axis2.wsdl.WSDLConstants;
 import javax.xml.namespace.QName;
 import java.lang.reflect.InvocationTargetException;
 import java.lang.reflect.Method;
 public class RPCMessageReceiver extends AbstractInOutSyncMessageReceiver {
 /**
  * reflect and get the Java method
  * - for each i'th param in the java method
  * - get the first child's i'th child
  * -if the elem has an xsi:type attr then find the deserializer for it
  * - if not found,
  * lookup deser for th i'th param (java type)
  * - error if not found
  * - deserialize  save in an object array
  * - end for
  * p/
  * - invoke method and get the return value
  * p/
  * - look up serializer for return value based on the value and type
  * p/
  * - create response msg and add return value as grand child of 
 soap:body
  *
  * @param inMessage
  * @param outMessage
  * @throws AxisFault
  */
 
 public void invokeBusinessLogic(MessageContext inMessage, MessageContext 
 outMessage) throws AxisFault {
 Method method = null;
 try {
 // get the implementation class for the Web Service
 Object obj = getTheImplementationObject(inMessage);
 Class ImplClass = obj.getClass();
 AxisOperation op = 
 inMessage.getOperationContext().getAxisOperation();
 AxisService service = inMessage.getAxisService();
 OMElement methodElement = inMessage.getEnvelope().getBody()
 .getFirstElement();
 AxisMessage inAxisMessage = 
 op.getMessage(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
 String messageNameSpace = null;
 QName elementQName;
 String methodName = op.getName().getLocalPart();
 Method[] methods = ImplClass.getMethods();
 for (int i = 0; i  methods.length; i++) {
 if (methods[i].getName().equals(methodName)) {
 method = methods[i];
 break;
 }

BAD url's in the tools page

2007-05-03 Thread Davanum Srinivas


Deepal,

In the following page:
http://ws.apache.org/axis2/tools/index.html

All the zip's point to 1_1_1 release not 1.2 :(

-- dims

--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (AXIS2-2632) Issues in ws.apache.org/axis2 site


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

Deepal Jayasinghe reassigned AXIS2-2632:


Assignee: Chatra Nakkawita

 Issues in ws.apache.org/axis2 site
 --

 Key: AXIS2-2632
 URL: https://issues.apache.org/jira/browse/AXIS2-2632
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples, build,site
Affects Versions: 1.2
 Environment: FireFox
Reporter: Charitha Kankanamge
 Assigned To: Chatra Nakkawita

 Following issues were encountered in axis2 web site.
 1. Blank pages appear when issuing following urls
 http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html 
 http://ws.apache.org/axis2/tools/1_2/eclipse/wsdl2java-plugin.html
 http://ws.apache.org/axis2/tools/1_2/eclipse/servicearchiver-plugin.html
 http://ws.apache.org/axis2/tools/1_2/idea/Idea_plug-in_userguide.html
 http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-aar-plugin.html
 http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-java2wsdl-plugin.html
 http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-wsdl2code-plugin.html
 http://ws.apache.org/axis2/1_2/api/index.html
 2. Architectural Overview image is corrupted in 
 http://ws.apache.org/axis2/1_2/adb/adb-howto.html
 3. 'html' appears in http://ws.apache.org/axis2/1_2/rest-ws.html page

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (AXIS2-2631) WSDL2Java: WSDLProcessingException: Encoded use is not supported?


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

Deepal Jayasinghe reassigned AXIS2-2631:


Assignee: Amila Chinthaka Suriarachchi

 WSDL2Java: WSDLProcessingException: Encoded use is not supported?
 -

 Key: AXIS2-2631
 URL: https://issues.apache.org/jira/browse/AXIS2-2631
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.2
 Environment: Windows XP
Reporter: wolverine
 Assigned To: Amila Chinthaka Suriarachchi
Priority: Minor

 I encounter the following error when tried to generate web service
 client using Axis2 1.2 and XMLBeans:
 WSDL2Java -uri Dummy.wsdl -p com.test.dummy -d xmlbeans -s
 Using AXIS2_HOME:   C:\axis2-1.2
 Using JAVA_HOME:C:\Program Files\Java\jdk1.5.0_11
 May 2, 2007 11:37:18 AM
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder
 populateService
 SEVERE: 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
 Encoded use is not supported
 Exception in thread main
 org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing
 WSDL
   at 
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:137)
   at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
   at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 Caused by: org.apache.axis2.AxisFault: Encoded use is not supported
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:298)
   at 
 org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateAllServices(WSDL11ToAllAxisServicesBuilder.java:100)
   at 
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGenerationEngine.java:131)
   ... 2 more
 Caused by: 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
 Encoded use is not supported
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.getPartsListFromSoapBody(WSDL11ToAxisServiceBuilder.java:1543)
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.createSchemaForPorttype(WSDL11ToAxisServiceBuilder.java:1294)
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.generateWrapperSchema(WSDL11ToAxisServiceBuilder.java:1198)
   at 
 org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:252)
   ... 4 more
 Note that the same command and WSDL file was working fine with Axis2 1.1.1.
 The following is the complete WSDL file:
 ?xml version='1.0' encoding='UTF-8' ? 
 !-- Generated 10/01/05 by Microsoft SOAP Toolkit WSDL File Generator -- 
 definitions  name ='CPA'   targetNamespace = 'http://myns/wsdl/'
xmlns:wsdlns='http://myns/wsdl/' 
xmlns:typens='http://mynsi.org/type' 
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' 
xmlns:xsd='http://www.w3.org/2001/XMLSchema' 
xmlns:stk='http://schemas.microsoft.com/soap-toolkit/wsdl-extension'
xmlns='http://schemas.xmlsoap.org/wsdl/' 
   types
 schema targetNamespace='http://mynsi.org/type'
   xmlns='http://www.w3.org/2001/XMLSchema'
   xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'
   xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/'
   elementFormDefault='qualified'
 /schema
   /types
   message name='clsCPA.deliverMTMessage'
 part name='ApplicationId' type='xsd:short'/
 part name='Login' type='xsd:string'/
 part name='Password' type='xsd:string'/
 part name='MessageTerminatingID' type='xsd:double'/
 part name='MessageOriginatingLinkID' type='xsd:double'/
 part name='ChargeMSISDN' type='xsd:string'/
 part name='ReceiverMSISDN' type='xsd:string'/
 part name='ShortCode' type='xsd:string'/
 part name='MessageCount' type='xsd:short'/
 part name='DateTime' type='xsd:string'/
 part name='MessageScheduleFlag' type='xsd:short'/
 part name='MessageScheduleTime' type='xsd:string'/
 part name='BillType' type='xsd:short'/
 part name='BillServiceId' type='xsd:int'/
 part name='BillPrice' type='xsd:short'/
 part name='IsFlash' type='xsd:short'/
 part name='MessageContentType' type='xsd:string'/
 part name='MessageType' type='xsd:string'/
 part name='Message' type='xsd:anyType'/
 part name='MessageExpiryTime' type='xsd:short'/
   /message
   message name='clsCPA.deliverMTMessageResponse'
 part name='Result' type='xsd:string'/
   /message
   message name='clsCPA.DeliverChineseMessage'
 part name='ApplicationId' type='xsd:short'/
 part name='Login' type='xsd:string'/
 part name='Password' type='xsd:string'/
 part name='MessageTerminatingID' type='xsd:double'/
 part name='MessageOriginatingLinkID' type='xsd:double'/
 part name='ChargeMSISDN' type='xsd:string'/

[jira] Reopened: (AXIS2-1899) BeanUtil.getOMElement is not working with object hierarchy


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

Deepal Jayasinghe reopened AXIS2-1899:
--


 BeanUtil.getOMElement is not working with object hierarchy
 --

 Key: AXIS2-1899
 URL: https://issues.apache.org/jira/browse/AXIS2-1899
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: databinding
Affects Versions: 1.1
Reporter: pinston
 Assigned To: Deepal Jayasinghe

 Test OK:
 
 public class MyObject {
 private String prop;
  
 public void setProp(String prop) {
 this.prop = prop;
 }
  
 public String getProp() {
 return this.prop;
 }
 }
 MyObject myObject = new MyObject();
 myObject.setProp( test );
 OMElement omElement = BeanUtil.getOMElement(createEmployeeMethod, new 
 Object[] {myObject}, null, false, null);
 = xml: arg0 xmlns=proptest/prop/arg0
 Test Failed :
 
 public class ExtObject extends MyObject {
 }
 ExtObject myObject = new ExtObject ();
 myObject.setProp( test );
 OMElement omElement = BeanUtil.getOMElement(createEmployeeMethod, new 
 Object[] {myObject}, null, false, null);
 generated xml: arg0 xmlns= /
 Why
 --
 I think the correction is in the method BeanUtil.getPullParser in line 83
 JProperty properties [] = jClass.getDeclaredProperties(); should be replaced 
 by JProperty properties [] = jClass.getProperties();
 with this correction everything works fine

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: BAD url's in the tools page

Hi Dims,

Done , but it will take few hrs to update the site.

Thanks
Deepal

Davanum Srinivas wrote:

 Deepal,

 In the following page:
 http://ws.apache.org/axis2/tools/index.html

 All the zip's point to 1_1_1 release not 1.2 :(

 -- dims



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Assigned: (AXIS2-2633) axis2-wsdl2code-maven-plugin missing extension option bindingfile for JiBX

2007-05-03 Thread Jochen Wiedmann (JIRA)


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

Jochen Wiedmann reassigned AXIS2-2633:
--

Assignee: Jochen Wiedmann

 axis2-wsdl2code-maven-plugin missing extension option bindingfile for JiBX
 

 Key: AXIS2-2633
 URL: https://issues.apache.org/jira/browse/AXIS2-2633
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2
 Environment: all platforms
Reporter: Armin Ehrenfels
 Assigned To: Jochen Wiedmann

 axis2-wsdl2code-maven-plugin doesn't support extension options such as 
 -Ebindingfile for JiBX.
 SUGGESTION:
 1. in the plugin configuration, introducing an additional option 
 extensionOptions, similar to namespaceURIs, like this:
  
 extensionOptions
extensionOption
namexxx/name
   valueyyy/value
   /extensionOption
   ...
 /extensionOptions 
 2. in the mojo, for each extension option adding the name/value pair to 
 optionsMap. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[axis2] ContextFactory - get rid of it?

2007-05-03 Thread Glen Daniels


Hi folks!

Recently I was in the midst of writing a test which used ServiceClient 
directly (i.e. not a Stub).  I wanted to get at the last 
OperationContext by using client.getLastOperationContext() but it wasn't 
working... turns out this was because there are (at least) two ways of 
making an OperationContext and associating it with a ServiceContext. 
You could call serviceContext.createOperationContext() (which as it 
happens was the place where the code to cache the lastOperationContext 
lived), OR you could call 
ContextFactory.createOperationContext(AxisOperation, ServiceContext) 
directly, which did NOT have the caching code - and this is what was 
happening when you used the ServiceClient directly (via 
ServiceClient.createClient()).  I took a look into this, and came to the 
following conclusion.


I'd like to get rid of ContextFactory entirely, for a few reasons. 
First it's confusing to have multiple ways of doing things, and that's 
why the above problem occurred.  Second, since contexts depend on each 
other (it doesn't make sense to have a MessageContext without a 
ConfigurationContext, for example), it is a little odd that there are 
currently a bunch of ways to build contexts with inappropriately 
disconnected references.  I think we should be as flexible as possible, 
but it should not be possible to build context hierarchies that aren't 
really usable (i.e. an OperationContext without a ServiceContext). 
Finally, the Factory pattern 
(http://en.wikipedia.org/wiki/Factory_method_pattern) isn't really 
reflected by ContextFactory - it's neither generating potentially 
different versions of a base class interface, nor is it doing a lot of 
setup work for you.  In fact the work it does could (and should) be more 
easily accomplished by simply putting factory methods in the Context 
classes themselves.  I believe this also simplifies the code.


So I'm thinking the context generation should work as follows.  The 
methods which take args should all be protected against nulls.


cc = new ConfigurationContext() // this one you can just make

mc = configContext.createMessageContext()

sgc = configContext.createServiceGroupContext(AxisServiceGroup)

sc = serviceGroupContext.createServiceContext(AxisService)

oc = serviceContext.createOperationContext(AxisOperation)

mc = operationContext.createMessageContext(AxisMessage)

Thoughts?

Thanks,
--Glen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

WS-transaction

2007-05-03 Thread Marcus Vinicius A Silva

Hi,

I'm trying implement Ws-transaction example with Axis 2. But
in my searches i didn't find any sample. I found some APIs to implement
it, like kandula Apache,jax-ws,WS-TX, but i dont't know the best.
Do you know if there is someone that have implemented something using this 
especification.

Best regards,

Marcus Vinicius


Pessoal

alguem já implementou transações atômicos com web
services? Na net vejo muito especificação, mas queria algo mais na
prática. Alguem já trabalhou? Qual API vocês utilizaram?
Vi por alto o kandula, jax-ws e wsit. Alguma recomendação?

Agradecido 

Marcus Vinicius


__
Fale com seus amigos  de graça com o novo Yahoo! Messenger 
http://br.messenger.yahoo.com/

Re: [axis2] ContextFactory - get rid of it?

Hi Glen,

I really like the idea, but one of the reason to introduce that factory
was to support clustering requirements. They wanted to have a single
place of creating all the Contexts , then they have only one place to
worry about. They wanted to have some triggering mechanism when when
creating Contexts that is why we introduced that. All the communications
are happen in the mailing list , I think Chamikra might remember more
than me. I can not exactly remember which mail thread we had that
conversation [1] , [2] or some other.

[1] - http://marc.info/?t=11717471353r=1w=2
[2] - http://marc.info/?w=2r=1s=clustering+prototype+availableq=t


Thanks
Deepal


Glen Daniels wrote:

 Hi folks!

 Recently I was in the midst of writing a test which used ServiceClient
 directly (i.e. not a Stub).  I wanted to get at the last
 OperationContext by using client.getLastOperationContext() but it
 wasn't working... turns out this was because there are (at least) two
 ways of making an OperationContext and associating it with a
 ServiceContext. You could call serviceContext.createOperationContext()
 (which as it happens was the place where the code to cache the
 lastOperationContext lived), OR you could call
 ContextFactory.createOperationContext(AxisOperation, ServiceContext)
 directly, which did NOT have the caching code - and this is what was
 happening when you used the ServiceClient directly (via
 ServiceClient.createClient()).  I took a look into this, and came to
 the following conclusion.

 I'd like to get rid of ContextFactory entirely, for a few reasons.
 First it's confusing to have multiple ways of doing things, and that's
 why the above problem occurred.  Second, since contexts depend on each
 other (it doesn't make sense to have a MessageContext without a
 ConfigurationContext, for example), it is a little odd that there are
 currently a bunch of ways to build contexts with inappropriately
 disconnected references.  I think we should be as flexible as
 possible, but it should not be possible to build context hierarchies
 that aren't really usable (i.e. an OperationContext without a
 ServiceContext). Finally, the Factory pattern
 (http://en.wikipedia.org/wiki/Factory_method_pattern) isn't really
 reflected by ContextFactory - it's neither generating potentially
 different versions of a base class interface, nor is it doing a lot of
 setup work for you.  In fact the work it does could (and should) be
 more easily accomplished by simply putting factory methods in the
 Context classes themselves.  I believe this also simplifies the code.

 So I'm thinking the context generation should work as follows.  The
 methods which take args should all be protected against nulls.

 cc = new ConfigurationContext() // this one you can just make

 mc = configContext.createMessageContext()

 sgc = configContext.createServiceGroupContext(AxisServiceGroup)

 sc = serviceGroupContext.createServiceContext(AxisService)

 oc = serviceContext.createOperationContext(AxisOperation)

 mc = operationContext.createMessageContext(AxisMessage)

 Thoughts?

 Thanks,
 --Glen

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




-- 
Thanks,
Deepal

The highest tower is built one brick at a time



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] ContextFactory - get rid of it?

2007-05-03 Thread Glen Daniels


Deepal Jayasinghe wrote:

I really like the idea, but one of the reason to introduce that factory
was to support clustering requirements. They wanted to have a single
place of creating all the Contexts , then they have only one place to
worry about. They wanted to have some triggering mechanism when when
creating Contexts that is why we introduced that.


Hm... and yet that doesn't seem to happen, because everything right now 
uses ContextFactory directly, and I don't see any hooks in there for 
supporting notifications, just a bunch of static methods.  ?


I'll go read those threads (thanks for the pointers), but I think there 
are perhaps better ways to achieve the goals than a static factory 
class, depending on exactly what the requirements are.  For example:


ConfigurationContext {
public void setContextListener(ContextListener);
}

then every sub-context create method does something like this:

ServiceContext {
  public OperationContext createOpContext(AxisOperation) {
if (myConfigContext.hasContextListener()) {
  // Either ask the listener to get the context itself,
  // or just notify it, etc... then return it.
} else {
  return new OperationContext(AxisOperation, this);
}
  }
}

Thanks,
--Glen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] ContextFactory - get rid of it?


 Hm... and yet that doesn't seem to happen, because everything right
 now uses ContextFactory directly, and I don't see any hooks in there
 for supporting notifications, just a bunch of static methods.  ?

 I'll go read those threads (thanks for the pointers), but I think
 there are perhaps better ways to achieve the goals than a static
 factory class, depending on exactly what the requirements are.  For
 example:

So let's go for those.


Thanks
Deepal


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [axis2] ContextFactory - get rid of it?

2007-05-03 Thread Davanum Srinivas


Let's go for it glen!

-- dims

On 5/3/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote:


 Hm... and yet that doesn't seem to happen, because everything right
 now uses ContextFactory directly, and I don't see any hooks in there
 for supporting notifications, just a bunch of static methods.  ?

 I'll go read those threads (thanks for the pointers), but I think
 there are perhaps better ways to achieve the goals than a static
 factory class, depending on exactly what the requirements are.  For
 example:

So let's go for those.


Thanks
Deepal


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-2635) Exception in XML serialization causes malformed/corrupted response

2007-05-03 Thread Alan Xu (JIRA)

Exception in XML serialization causes malformed/corrupted response
--

 Key: AXIS2-2635
 URL: https://issues.apache.org/jira/browse/AXIS2-2635
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.1.1, 1.2
 Environment: Windows Vista, Tomcat 5.5.20, JDK 1.5.0_10
Reporter: Alan Xu


Hi there,

We have a simple SOAP layer that returns data pulled from the DB using Axis.  
Nothing special here.

In our testing, one of the objects happened to have an invalid XML 1.0 
character (0x10) in its description field.  As it's not an application Fault 
(our application currently doesn't check for it.  It no doubt should, 
obviously), Axis2 wasn't aware of it until it's notified by the Woodstox 
BufferingXMLWriter of an invalid character (through IOException).  Axis2 caught 
the exception (at , and raised an AxisFault.  It then proceeded to send the 
Fault as its own message (envelope) back to the client.  All is well, except 
that Axis2 was in the middle of writing out response provided by the business 
application.  That led to a corrupted byte stream that contained a partial, not 
well-formed envelope, followed immediately by the Fault envelope.  Something to 
the effect of a purging (not flushing) to clear the output stream before 
sending out the Fault message would seem desirable.

It may not be so bad if the client receives such a corrupted stream, and throws 
some sort of error.  The Fault message becomes meaningless, obviously, which 
isn't great either.  But, what's worse is that the Axis2 client 
(ServiceClient.sendReceive) actually was able to parse the corrupted byte 
stream, and somehow considered the Fault message be the content of the last XML 
element that contained the invalid character.  Now, that's really bad.

This may have been logged in JIRA, but I couldn't seem to find it.

-Alan

Stack track of the exception caught by Axis2 during serialization:

 com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x10) in text 
to output
at 
com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:520)
at 
org.apache.axiom.om.impl.llom.OMTextImpl.writeOutput(OMTextImpl.java:209)
at 
org.apache.axiom.om.impl.llom.OMTextImpl.internalSerializeLocal(OMTextImpl.java:368)
at 
org.apache.axiom.om.impl.llom.OMTextImpl.internalSerialize(OMTextImpl.java:197)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:766)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:750)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:766)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:750)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:766)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:564)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.internalSerialize(OMElementImpl.java:750)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.internalSerialize(OMSourcedElementImpl.java:551)
at 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl.serialize(OMSourcedElementImpl.java:592)
at 
org.apache.axiom.om.impl.llom.OMElementImpl.toString(OMElementImpl.java:907)
... 30 more
Caused by: java.io.IOException: Invalid white space character (0x10) in text to 
output
at com.ctc.wstx.sw.XmlWriter.throwInvalidChar(XmlWriter.java:545)
at 
com.ctc.wstx.sw.BufferingXmlWriter.writeCharacters(BufferingXmlWriter.java:453)
at 
com.ctc.wstx.sw.BaseStreamWriter.writeCharacters(BaseStreamWriter.java:518)
... 43 more


This is the call stack from Eclipse debugger:

CoyoteOutputStream.write(byte[], int, int) line: 88 
UTF8Writer.flush() line: 96 
BufferingXmlWriter.flush() line: 214
SimpleNsStreamWriter(BaseStreamWriter).flush() line: 311
MTOMXMLStreamWriter.flush() line: 115   
SOAPEnvelopeImpl(OMNodeImpl).serializeAndConsume(OutputStream, OMOutputFormat) 
line: 419
SOAPMessageFormatter.writeTo(MessageContext, OMOutputFormat, OutputStream, 
boolean) line: 55
CommonsHTTPTransportSender.sendUsingOutputStream(MessageContext, 
OMOutputFormat) line: 275  
CommonsHTTPTransportSender.invoke(MessageContext) line: 203 
AxisEngine.sendFault(MessageContext) line: 533  
AxisServlet.handleFault(MessageContext, OutputStream, AxisFault) line: 393  
AxisServlet.processAxisFault(MessageContext, HttpServletResponse, OutputStream, 
AxisFault) line: 355
AxisServlet.doPost(HttpServletRequest, HttpServletResponse) line: 152   
AxisServlet(HttpServlet).service(HttpServletRequest, HttpServletResponse) line: 
709

[jira] Created: (AXIS2-2636) getResourceAsStream(String) failure for files under WEB-INF/classes

2007-05-03 Thread Alan Xu (JIRA)

getResourceAsStream(String) failure for files under WEB-INF/classes
---

 Key: AXIS2-2636
 URL: https://issues.apache.org/jira/browse/AXIS2-2636
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.2
 Environment: Windows Vista, Tomcat 5.5.20, JDK 1.5.0_10
Reporter: Alan Xu


One of the ways to access resource files is through 
this.getClass().getResourceAsStream(filename).  In our example, this is a 
class that's in the .aar file.  You would place the resources files under 
WEB-INF/classes, and things would just work.  With Axis2, the .aar file is 
placed under WEB-INF/services, but the getResourceAsStream call still works 
properly.

With 1.2 release, however, that call is no longer work.  It appears that there 
have been some retooling of DeploymentClassLoader such that it can only 
resolves files in the .aar file.

A workaround is to instead of using a class in the .aar file for the 
getResourceAsStream(filename) call, you would reference a class located in 
WEB-INF/lib or WEB-INF/classes.

-Alan

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (AXIS2-2636) getResourceAsStream(String) failure for files under WEB-INF/classes

2007-05-03 Thread Davanum Srinivas (JIRA)


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

Davanum Srinivas commented on AXIS2-2636:
-

see http://wso2.org/blog/dims/1131 

 getResourceAsStream(String) failure for files under WEB-INF/classes
 ---

 Key: AXIS2-2636
 URL: https://issues.apache.org/jira/browse/AXIS2-2636
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.2
 Environment: Windows Vista, Tomcat 5.5.20, JDK 1.5.0_10
Reporter: Alan Xu

 One of the ways to access resource files is through 
 this.getClass().getResourceAsStream(filename).  In our example, this is a 
 class that's in the .aar file.  You would place the resources files under 
 WEB-INF/classes, and things would just work.  With Axis2, the .aar file is 
 placed under WEB-INF/services, but the getResourceAsStream call still works 
 properly.
 With 1.2 release, however, that call is no longer work.  It appears that 
 there have been some retooling of DeploymentClassLoader such that it can only 
 resolves files in the .aar file.
 A workaround is to instead of using a class in the .aar file for the 
 getResourceAsStream(filename) call, you would reference a class located in 
 WEB-INF/lib or WEB-INF/classes.
 -Alan

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Work started: (AXIS2-2629) Update the known limitations section of the Axis2 frontpage


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

Work on AXIS2-2629 started by Chatra Nakkawita.

 Update the known limitations section of the Axis2 frontpage
 ---

 Key: AXIS2-2629
 URL: https://issues.apache.org/jira/browse/AXIS2-2629
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Thilina Gunarathne
 Assigned To: Chatra Nakkawita
Priority: Blocker

 Please update the following in the http://ws.apache.org/axis2/index.html
 Known Issues and Limitations
 * ADB does not support unwrapping of response messages(coming in 1.2)
 * JSR 181/183 Annotation support (coming in 1.2)
 * JaxMe and JAXBRI data binding support is experimental
 * Simple Axis Server does not support POX/REST
 * RPC Message Receiver does not validate a request against the schema 
 (AXIS2-1943)
 * Axis2 Idea plugin shows random behavior when XMLBeans is used

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Work started: (AXIS2-2632) Issues in ws.apache.org/axis2 site


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

Work on AXIS2-2632 started by Chatra Nakkawita.

 Issues in ws.apache.org/axis2 site
 --

 Key: AXIS2-2632
 URL: https://issues.apache.org/jira/browse/AXIS2-2632
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples, build,site
Affects Versions: 1.2
 Environment: FireFox
Reporter: Charitha Kankanamge
 Assigned To: Chatra Nakkawita

 Following issues were encountered in axis2 web site.
 1. Blank pages appear when issuing following urls
 http://ws.apache.org/axis2/tools/1_2/CodegenToolReference.html 
 http://ws.apache.org/axis2/tools/1_2/eclipse/wsdl2java-plugin.html
 http://ws.apache.org/axis2/tools/1_2/eclipse/servicearchiver-plugin.html
 http://ws.apache.org/axis2/tools/1_2/idea/Idea_plug-in_userguide.html
 http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-aar-plugin.html
 http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-java2wsdl-plugin.html
 http://ws.apache.org/axis2/tools/1_2/maven-plugins/maven-wsdl2code-plugin.html
 http://ws.apache.org/axis2/1_2/api/index.html
 2. Architectural Overview image is corrupted in 
 http://ws.apache.org/axis2/1_2/adb/adb-howto.html
 3. 'html' appears in http://ws.apache.org/axis2/1_2/rest-ws.html page

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Work started: (AXIS2-2608) Known issues and limitations are not up-to-date in ws.apache.org/axis2 page


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

Work on AXIS2-2608 started by Chatra Nakkawita.

 Known issues and limitations are not up-to-date in ws.apache.org/axis2 page
 ---

 Key: AXIS2-2608
 URL: https://issues.apache.org/jira/browse/AXIS2-2608
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples, build,site
Affects Versions: 1.2
Reporter: Charitha Kankanamge
 Assigned To: Chatra Nakkawita

 Known issues and limitations listed in the ws.apache.org/axis2 page were not 
 updated according to 1.2 release notes. 
 It still contains outdated information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Work started: (AXIS2-2604) Download links for the archived releases are incorrect


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

Work on AXIS2-2604 started by Chatra Nakkawita.

 Download links for the archived releases are incorrect
 --

 Key: AXIS2-2604
 URL: https://issues.apache.org/jira/browse/AXIS2-2604
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Thilina Gunarathne
 Assigned To: Chatra Nakkawita
Priority: Critical

 We need to update those pages to point to the archived locations..
 eg: http://ws.apache.org/axis2/download/1_0/download.cgi

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Closed: (AXIS2-2608) Known issues and limitations are not up-to-date in ws.apache.org/axis2 page


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

Chatra Nakkawita closed AXIS2-2608.
---

Resolution: Duplicate

Duplicate issue in progress- https://issues.apache.org/jira/browse/AXIS2-2629

THanks,
Chatra

 Known issues and limitations are not up-to-date in ws.apache.org/axis2 page
 ---

 Key: AXIS2-2608
 URL: https://issues.apache.org/jira/browse/AXIS2-2608
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples, build,site
Affects Versions: 1.2
Reporter: Charitha Kankanamge
 Assigned To: Chatra Nakkawita

 Known issues and limitations listed in the ws.apache.org/axis2 page were not 
 updated according to 1.2 release notes. 
 It still contains outdated information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (AXIS2-2637) Updated the index.html file

2007-05-03 Thread Marietta Lovendhal (JIRA)

Updated the index.html file
---

 Key: AXIS2-2637
 URL: https://issues.apache.org/jira/browse/AXIS2-2637
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.2
 Environment: Windows XP
Reporter: Marietta Lovendhal
Priority: Minor


Updated the index.html file according to the release note.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (AXIS2-2637) Updated the index.html file

2007-05-03 Thread Marietta Lovendhal (JIRA)


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

Marietta Lovendhal updated AXIS2-2637:
--

Attachment: index.patch

Patch attached

 Updated the index.html file
 ---

 Key: AXIS2-2637
 URL: https://issues.apache.org/jira/browse/AXIS2-2637
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: documentation
Affects Versions: 1.2
 Environment: Windows XP
Reporter: Marietta Lovendhal
Priority: Minor
 Attachments: index.patch


 Updated the index.html file according to the release note.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Resolved: (AXIS2-2629) Update the known limitations section of the Axis2 frontpage