date:20070611


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

Deepal Jayasinghe resolved AXIS2-2772.
--

Resolution: Fixed

fixed in the current SVN

 RPCMessageReceivers' response is invalid in some situations.  
 --

 Key: AXIS2-2772
 URL: https://issues.apache.org/jira/browse/AXIS2-2772
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
 Environment: Any 
Reporter: Saminda Wishwajith Abeyruwan
Assignee: Deepal Jayasinghe
Priority: Critical

 Use case.
 When RPCMessageReceiver is used, 
 If the service has the following method signature,
 public Foo[] getFoos();
 Foo can be either primitive type, primitive type wrapper, or a custom bean. 
 If some one return an empty array (new Foo[0];)
 Following is the resulting response SOAP envelope, 
 ?xml version='1.0' encoding='UTF-8'?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Body
 ns:getFoosResponse xmlns:ns=http://org.apache.axis2/xsd;
 return xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true 
 /
 /ns:getFoosResponse
 /soapenv:Body
 /soapenv:Envelope
 Is it technically correct to send return 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:nil=true /
 if an empty element is return ?
 Thank you
 Saminda 

-- 
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-2790) Having a problem with the JavaScript call (of Google Analytics) on axis2 html after a maven site build

2007-06-11 Thread Chatra Nakkawita (JIRA)

Having a problem with the JavaScript call (of Google Analytics) on axis2 html 
after a maven site build
--

 Key: AXIS2-2790
 URL: https://issues.apache.org/jira/browse/AXIS2-2790
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: documentation, samples, build,site
 Environment: Windows XP/JDK1.5/Firefox 2.x
Reporter: Chatra Nakkawita


The JavaScript call [1] to track a download on click is not correctly displayed 
after a maven build site.

See 
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/xdocs/download/1_2/download.html

Here you will find 
a href=[preferred]/ws/axis2/1_2/axis2-1.2.zip
title=[preferred]/ws/axis2/1_2/axis2-1.2.zip 
onClick=javascript:urchinTracker ('/downloads/axis2-1.2.zip'); zip/a

After a maven site build the JavaScript call will read as :
a href=[preferred]/ws/axis2/1_2/axis2-1.2.zip 
title=[preferred]/ws/axis2/1_2/axis2-1.2.zip 
onclick=javascript:urchinTracker (apos;/downloads/axis2-1.2.zipapos;); 
zip/a

Diff : 
onClick=javascript:urchinTracker ('/downloads/axis2-1.2.zip');  |
onclick=javascript:urchinTracker (apos;/downloads/axis2-1.2.zipapos;); 

Note that the single quotes ( ' ) in the function is converted to apos;

How can we make the call remain as : onClick=javascript:urchinTracker 
('/downloads/axis2-1.2.zip'); 

This is required for the tracking of downloads of Google Analytics [2]

Thanks,
Chatra
[1]http://www.google.com/support/analytics/bin/answer.py?answer=27242topic=7292
[2]http://www.google.com/support/analytics/bin/answer.py?answer=26908


-- 
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-2791) Super class not being generated in WSDL

2007-06-11 Thread Drew Bentley (JIRA)

Super class not being generated in WSDL
---

 Key: AXIS2-2791
 URL: https://issues.apache.org/jira/browse/AXIS2-2791
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
 Environment: AXIS2 under Tomcat on XP
Reporter: Drew Bentley


XSD for inherited classes is not being generated correctly.

Example:
If a Test object extends TestBase the XSD generated is. ns:TestBase does not 
exist in this XSD:
 wsdl:types
xs:schema xmlns:ns=http://pkg/xsd; attributeFormDefault=qualified 
elementFormDefault=qualified targetNamespace=http://pkg/xsd;
  xs:element name=test
xs:complexType
  xs:sequence
xs:element name=input nillable=true type=ns:Test/
  /xs:sequence
/xs:complexType
  /xs:element
  xs:element name=Test type=ns:Test/
  xs:complexType name=Test
xs:complexContent
  xs:extension base=ns:TestBase
xs:sequence
  xs:element name=name nillable=true type=xs:string/
/xs:sequence
  /xs:extension
/xs:complexContent
  /xs:complexType
  xs:element name=testResponse
xs:complexType
  xs:sequence
xs:element name=return nillable=true type=ns:Test/
  /xs:sequence
/xs:complexType
  /xs:element
/xs:schema
  /wsdl:types


-- 
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][continuum] BUILD FAILURE

2007-06-11 Thread davidillsley (Continuum)

Online report : 
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2288
Build statistics:
  State: Failed
  Previous State: Ok
  Started at: Mon, 11 Jun 2007 12:07:26 +
  Finished at: Mon, 11 Jun 2007 12:34:20 +
  Total time: 26m 54s
  Build Trigger: Schedule
  Exit code: 70
  Building machine hostname: ws.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.5.0_09(Sun Microsystems Inc.)

Changes
 chatra  committing Google analytics tracking code and 
javascript calls for the downloads
 /webservices/axis2/trunk/java/xdocs/download/1_2/download.html
   chatra  committing changes to intro
 /webservices/axis2/trunk/java/xdocs/index.html
   deepal  fixing 
https://issues.apache.org/jira/browse/AXIS2-2772
no we do not send a return element if the array size is zero.
 
/webservices/axis2/trunk/java/modules/adb/src/org/apache/axis2/rpc/receivers/RPCUtil.java

/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/rpc/AddressServiceTest.java


Output:

Snipped Output:
onf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/commons-http-enabledRepository/conf
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-enabledRepository
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-enabledRepository/conf
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-enabledRepository/modules
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-enabledRepository/modules
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-fileCache-enabledRepository
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-fileCache-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-fileCache-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/MTOM-fileCache-enabledRepository/modules
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-enabledRepository/modules
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository/conf
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/test-resources/SwA-fileCache-enabledRepository/modules
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/groovyRepo
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/integration/target/groovyRepo/conf
[mkdir] Created

[jira] Updated: (AXIS2-1561) Java2WSDL generates incorrect WSDL


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

Deepal Jayasinghe updated AXIS2-1561:
-

Priority: Blocker  (was: Major)

 Java2WSDL generates incorrect WSDL
 --

 Key: AXIS2-1561
 URL: https://issues.apache.org/jira/browse/AXIS2-1561
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: nightly
Reporter: Manuel Ernstberger
Assignee: Deepal Jayasinghe
Priority: Blocker

 When I generate a WSDL from a Java class with the latest nightly build of 
 Axis2, in the generated WSDL the wsdl:fault element has no name 
 attribute, as it is supposed to be.
 My Java class looks like that:
 public class TestWSImpl implements TestWS {
 public void ping(String text){
 System.out.println(text);
 }
 
 public String echo(String text) {
 System.out.println(text);
 return text;  
 }
 }
 And this is the resulting WSDL:
 wsdl:definitions xmlns:axis2=http://epdm.tsystems.com/xsd; 
 xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; 
 xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; 
 xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; 
 xmlns:ns1=http://epdm.tsystems.com/xsd; 
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
 targetNamespace=http://epdm.tsystems.com/xsd;wsdl:typesxs:schema 
 xmlns:xs=http://www.w3.org/2001/XMLSchema; 
 xmlns:ax21=http://epdm.tsystems.com/xsd; attributeFormDefault=qualified 
 elementFormDefault=qualified targetNamespace=http://epdm.tsystems.com/xsd;
 xs:element name=echoFault
 xs:complexType
 xs:sequence
 xs:element name=echoFault type=xs:anyType /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=echo
 xs:complexType
 xs:sequence
 xs:element name=param0 type=xs:string /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=echoResponse
 xs:complexType
 xs:sequence
 xs:element name=return type=xs:string /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=pingFault
 xs:complexType
 xs:sequence
 xs:element name=pingFault type=xs:anyType /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=ping
 xs:complexType
 xs:sequence
 xs:element name=param0 type=xs:string /
 /xs:sequence
 /xs:complexType
 /xs:element
 /xs:schema/wsdl:typeswsdl:message name=echoMessagewsdl:part 
 name=part1 element=ns1:echo //wsdl:messagewsdl:message 
 name=echoResponseMessagewsdl:part name=part1 element=ns1:echoResponse 
 //wsdl:messagewsdl:message name=echoFaultwsdl:part name=part1 
 element=ns1:echoFault //wsdl:messagewsdl:message 
 name=pingMessagewsdl:part name=part1 element=ns1:ping 
 //wsdl:messagewsdl:message name=pingFaultwsdl:part name=part1 
 element=ns1:pingFault //wsdl:messagewsdl:portType 
 name=TestWSPortTypewsdl:operation name=echowsdl:input 
 message=axis2:echoMessage /wsdl:output 
 message=axis2:echoResponseMessage /wsdl:fault message=axis2:echoFault 
 name=echoFault //wsdl:operationwsdl:operation name=pingwsdl:input 
 message=axis2:pingMessage /wsdl:fault message=axis2:pingFault 
 name=pingFault //wsdl:operation/wsdl:portTypewsdl:binding 
 name=TestWSSOAP11Binding type=axis2:TestWSPortTypesoap:binding 
 transport=http://schemas.xmlsoap.org/soap/http; style=document 
 /wsdl:operation name=echosoap:operation soapAction=urn:echo 
 style=document /wsdl:inputsoap:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:inputwsdl:outputsoap:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:outputwsdl:faultsoap:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:fault/wsdl:operationwsdl:operation name=pingsoap:operation 
 soapAction=urn:ping style=document /wsdl:inputsoap:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:inputwsdl:faultsoap:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:fault/wsdl:operation/wsdl:bindingwsdl:binding 
 name=TestWSSOAP12Binding type=axis2:TestWSPortTypesoap12:binding 
 transport=http://schemas.xmlsoap.org/soap/http; style=document 
 /wsdl:operation name=echosoap12:operation soapAction=urn:echo 
 style=document /wsdl:inputsoap12:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:inputwsdl:outputsoap12:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:outputwsdl:faultsoap12:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:fault/wsdl:operationwsdl:operation name=pingsoap12:operation 
 soapAction=urn:ping style=document /wsdl:inputsoap12:body 
 use=literal namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:inputwsdl:faultsoap12:body use=literal 
 namespace=http://epdm.tsystems.com/xsd; 
 //wsdl:fault/wsdl:operation/wsdl:bindingwsdl:service 
 name=TestWSwsdl:port name=TestWSSOAP11port 
 binding=axis2:TestWSSOAP11Bindingsoap:address

[jira] Resolved: (AXIS2-2775) nullpointer by invoking web service and RPCMessageReceiver problem


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

Deepal Jayasinghe resolved AXIS2-2775.
--

Resolution: Fixed

First you do not need to get the session context as you have done , you can 
just get the session context from the MessageContext.

MessageContext mctx =MessageContext.getCurrentMessageContext(); 
TransportListener listener = mctx.getTransportIn().getReceiver(); 
SessionContext session = listener.getSessionContext(mctx); 
MessageContext.getCurrentMessageContext().setSessionContext(session); 


And other thing is you have only valid session context only if you have deploy 
your service in transport session. So please try to do the following,

First deploy your service in transport session
Get the session context from the messagecontext.
MessageContext.getCurrentMessageContext().getSessionContext(); 



I will resolve the issues , since the error is due to user code. Please try to 
follow the steps that I mentioned and please re-open the issue if the issue is 
still there.

 nullpointer by invoking web service and RPCMessageReceiver problem 
 ---

 Key: AXIS2-2775
 URL: https://issues.apache.org/jira/browse/AXIS2-2775
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
 Environment: window xp
 jdk5
 axis2
 eclipse3.2
Reporter: haha
Assignee: Deepal Jayasinghe

 I have the Problem by invoking the Web Service with axis2,
 Client:
 public void MyConnection(String user, String passwd)throws RemoteException{
 Options options = new Options();
 options.setManageSession(true);
 RPCServiceClient serviceClient = new RPCServiceClient();
 options.setTo(targetEPR);
 options.setAction(urn:MyConnection);
 options.setExceptionToBeThrownOnSOAPFault(false);
 serviceClient.setOptions(options);   
 QName opSet = new QName(http://services.solver.nx.wp.com/xsd;, 
 MyConncetion);
 Object response = serviceClient.invokeBlocking(opSet,new Object[] 
 {user,passwd});
   if(response instanceof AxisFault)
   {
   throw (RemoteException)response;} 
   }
 -
 -Service
  public void MyConnection(String user, String passwd) throws AxisFault
{
 String connString = Const.getCONNECTIONSTRING();
if(connString == null)
 {
throw new AxisFault(Unknown server defined in web.xml.);
 }   
 MessageContext mctx =MessageContext.getCurrentMessageContext();
 TransportListener listener = mctx.getTransportIn().getReceiver();
 SessionContext session = listener.getSessionContext(mctx);
  
 
 MessageContext.getCurrentMessageContext().setSessionContext(session);
 System.out.println(the session is: + session + ;and the 
 sessionpropertiers is: +session.getProperties().size());
 session.getProperties().remove(Const.SESSIONUSER);
 session.getProperties().remove(Const.SESSIONCUSTOMER);
 
   Connection conn;
   try
   {
  Class.forName(Const.DBDRIVERCLASS);
   }
   catch(ClassNotFoundException cnfe)
   {
  terminate();
  throw new AxisFault(Database Driver-class not found.);
   }
   try
   {
  conn = DriverManager.getConnection(connString, user, passwd);
   }
   catch(SQLException sqle)
   {
  terminate();
  throw new AxisFault(Connection as admin could not be 
 established.\n + connString +  User:  + user);
   }
   DBHandler dbHandler = new DBHandler();
   try
   {
  ResultSet result = 
 dbHandler.performSelect(Const.getDBSQLUSERCUST(user), conn);
  if(!result.next())
  {
 conn.close();
 terminate();
 throw new AxisFault(The user is not linked with a customer.);
   }
  session.setProperty(Const.SESSIONUSER, 
 result.getString(Const.DBCOLUSERNAME));
  session.setProperty(Const.SESSIONCUSTOMER, new 
 Integer(result.getInt(Const.DBCOLCUSTID))); 
   }
   catch(SQLException sqle)
   {
  try
  {
 conn.close();
  }
  catch(SQLException sqle2)
  {
 terminate();
 throw new AxisFault(Error while closing the connection.);
  }
  terminate();
  throw new AxisFault(Error while getting user and customer from 
 database.);
   }
   try
   {
  conn.close();
   }
   catch(SQLException sqle)
   {
  terminate();
  throw new AxisFault(Error while closing the connection.);

[Axis2][continuum] BUILD SUCCESSFUL

2007-06-11 Thread davidillsley (Continuum)

Online report : 
http://ws.zones.apache.org:1/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/2290
Build statistics:
  State: Ok
  Previous State: Failed
  Started at: Mon, 11 Jun 2007 13:26:46 +
  Finished at: Mon, 11 Jun 2007 14:02:48 +
  Total time: 36m 2s
  Build Trigger: Schedule
  Exit code: 0
  Building machine hostname: ws.zones.apache.org
  Operating system : SunOS(unknown)
  Java version : 1.5.0_09(Sun Microsystems Inc.)

Changes
 azeez  Few more optimizations


 
/webservices/axis2/trunk/java/modules/clustering/src/org/apache/axis2/clustering/handlers/ReplicationHandler.java

/webservices/axis2/trunk/java/modules/clustering/src/org/apache/axis2/clustering/tribes/AckManager.java

/webservices/axis2/trunk/java/modules/clustering/src/org/apache/axis2/clustering/tribes/ChannelSender.java


Output:

Snipped Output:
ld:start:

multiproject:install-callback:
[echo] Running jar:install for Apache Axis 2.0 - MTOM Policy
java:prepare-filesystem:
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes
Running post goal: java:prepare-filesystem

java:compile:
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF
[echo] Compiling to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes
[javac] Compiling 2 source files to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes

java:jar-resources:
Copying 2 files to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes/META-INF

test:test:
java:prepare-filesystem:
Running post goal: java:prepare-filesystem

java:compile:
[echo] Compiling to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/classes

java:jar-resources:

test:prepare-filesystem:
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-reports

test:test-resources:
Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes

test:compile:
[javac] Compiling 1 source file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/test-classes

[junit] Running org.apache.axis2.policy.model.MTOMAssertionTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.497 sec

jar:jar:
[jar] Building jar: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/mtompolicy/target/axis2-mtompolicy-SNAPSHOT.jar

jar:install:
[echo] Installing...
Uploading to org.apache.axis2/jars/axis2-mtompolicy-SNAPSHOT.jar: 
 (8K)
Uploading to org.apache.axis2/poms/axis2-mtompolicy-SNAPSHOT.pom: 
 (13K)

+
| Executing multiproject:install-callback Apache Axis 2.0 - ping
| Memory: 33M/46M
+
DEPRECATED: the default goal should be specified in the build section of 
project.xml instead of maven.xml
DEPRECATED: the default goal should be specified in the build section of 
project.xml instead of maven.xml

build:end:

build:start:

multiproject:install-callback:
[echo] Running jar:install for Apache Axis 2.0 - ping
java:prepare-filesystem:
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes
Running post goal: java:prepare-filesystem

java:compile:
[echo] Compiling to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes
[javac] Compiling 3 source files to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes
Running post goal: java:compile
[mkdir] Created dir: 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF
[copy] Copying 1 file to 
/export/home/illsleyd/continuum/continuum-1.0.3/apps/continuum/working-directory/1/modules/ping/target/classes/META-INF

Re: [Axis2] Plan for the hackathon

2007-06-11 Thread Eran Chinthaka

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Ajith and all,

We identified following areas to concentrate during this session.

Build overview
WSDL2Java
Java2WSDL
Deployment
DOCS
Fault handling
Arch/Engine flow


Now we are going thru JIRA blockers. Please get in to axis IRC. We all
are there.

Chinthaka

Ajith Ranabahu wrote:
 oops - missed the prefix !
 
 -- Forwarded message --
 From: Ajith Ranabahu [EMAIL PROTECTED]
 Date: Jun 11, 2007 1:38 AM
 Subject: Plan for the hackathon
 To: Axis developer list axis-dev@ws.apache.org
 
 
 Hi all,
 I am sure the Axis2ers around the world are excited about the
 hackathon that is about to start tomorrow [Well today - (Monday 11th
 June) :)] Unfortunately I can only come for half the days but I'm sure
 any major decision will be reported to the list and the irc will be
 live as usual (I will participate in the sessions remotely as far as
 possible) However more importantly we need to outline the objective
 and layout the things we plan to attack.
 
 I will outline some items I felt as important to address while
 browsing the Jira list. Others are welcome to jump in and correct me
 in any place that I've missed. Again I believe the objective of this
 hackathon is to fix whatever is broken in the existing functionality
 rather than adding or discussing new features.
 
 1. Exception handling
  Number of issues have been reported about incorrect exception
 handling, irrelavant exceptions being thrown etc. So it seems that
 this is something we need to look at more carefully and correct.
 
 2 .WSDL2WS and ADB issues
  There are number of 'edge cases' reported about WSDL2WS - specially
 against the ADB binding. While some of these will fall into new
 features, I suppose we should address all the issues that are against
 the existing features and make it work for some of those edge cases.
 
 3. Java2WSDL issues
 There are some blockers reported about Java2WSDL. I believe Java2WSDL
 works ok for most of the cases but there seems to be some cases we
 need to answer. Both for WSDL2WS and Java2WSDL, they are the two most
 'visible' components for the users and that makes it important
 
 4. Misc
 There are a ton of small issue that does not specifically fall into a
 broad category. I'm hoping we can cover most of them by the time we
 end up fixing the major issues but we could tackle whatever is
 remaining once the major issues are covered.
 
 5. Documentation
 While we will not sit and write the user guide once more at this
 occasion I see this as a time we can add some of the missing javadocs
 to the source (and also correct some header problems. I see a Jira
 that says some license headers are not proper)
 
 Anything else we can try to tackle in this limited time frame?
 
 Ajith Ranabahu
 
 

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGbWDijON2uBzUhh8RAt9wAJ4k05S2yvYKDHgpLFijzxUwOP4nNACfYFUY
Kxx/PyN62ZCuNPARwmejGaA=
=rDxX
-END PGP SIGNATURE-

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

[jira] Commented: (AXIS2-2785) Service lifecycle

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

Glen Daniels commented on AXIS2-2785:
-

Here's a summary of the discussion here at the hackathon about this:

* The exception referred to is now being caught, so the intial serious
problem is already dealt with. However, we all agreed that we should NOT be
logging it (since it's not really an error not to implement the method)

* This issue is now really about whether or not we want to move (back) to
having a ServiceLifecycle interface, or continue reflecting to find the init()
and destroy() methods. Dims and Michele have indicated a preference for the
interface approach.

* The feeling in the room here is generally that the interface approach is
better, but we're unsure if it's worth changing it right now.

* Glen's opinion is that it's a lot better to do the interface for a variety of
reasons including a) speed, b) ease of use (the IDE can help you get the
methods right instead of relying upon error-prone transcriptions of
documentation), and c) architectural clarity. I believe we can do this change
cleanly by adding back in the interface so we're back to doing both for a
while... then making VERY clear we plan to phase out the non-interface methods
at some point. People will need to add a single implements ServiceLifecycle
to their impl classes at some point.

We'd like to get a few more opinions. Leaving this open for the moment.

Service lifecycle
-

Key: AXIS2-2785
URL: https://issues.apache.org/jira/browse/AXIS2-2785
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Affects Versions: 1.2
Reporter: Michele Mazzucco
Assignee: Deepal Jayasinghe
Priority: Blocker

http://www.nabble.com/java.lang.NoSuchMethodException-tf3886972.html

--
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-2792) Java2WSDL is oddly naming WSDL faults

Java2WSDL is oddly naming WSDL faults
-

 Key: AXIS2-2792
 URL: https://issues.apache.org/jira/browse/AXIS2-2792
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Reporter: Glen Daniels
Assignee: Deepal Jayasinghe
 Fix For: 1.3


If we have

package ns;
class Service {
void foo(int i) throws CustomException {
}
void bar(int i) throws CustomException {
}
}

Java2WSDL currently generates two separate fault messages:

message name=fooFault0
message name=barFault1

Both of those refer to part element=ns:CustomException

We should be generating a single message which gets referred to by both 
methods, just like the exception is used by both methods.

message name=CustomException

Deepal is working on this.

-- 
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-2792) Java2WSDL is oddly naming WSDL faults


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

Glen Daniels updated AXIS2-2792:


Priority: Blocker  (was: Major)

 Java2WSDL is oddly naming WSDL faults
 -

 Key: AXIS2-2792
 URL: https://issues.apache.org/jira/browse/AXIS2-2792
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Reporter: Glen Daniels
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3


 If we have
 package ns;
 class Service {
 void foo(int i) throws CustomException {
 }
 void bar(int i) throws CustomException {
 }
 }
 Java2WSDL currently generates two separate fault messages:
 message name=fooFault0
 message name=barFault1
 Both of those refer to part element=ns:CustomException
 We should be generating a single message which gets referred to by both 
 methods, just like the exception is used by both methods.
 message name=CustomException
 Deepal is working on this.

-- 
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-2785) Service lifecycle

2007-06-11 Thread Davanum Srinivas (JIRA)


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

Davanum Srinivas commented on AXIS2-2785:
-

Glen,

At this point i don't think anyone is going to change their opinions already 
stated out on the mailing lists. Could you please start a vote thread with some 
explicit proposal and we can make a decision and close this issue one way or 
another? 

thanks,
dims

 Service lifecycle
 -

 Key: AXIS2-2785
 URL: https://issues.apache.org/jira/browse/AXIS2-2785
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Michele Mazzucco
Assignee: Deepal Jayasinghe
Priority: Blocker

 http://www.nabble.com/java.lang.NoSuchMethodException-tf3886972.html

-- 
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: [jira] Commented: (AXIS2-2785) Service lifecycle

2007-06-11 Thread Glen Daniels


+1, will do.

And dims, GET BACK TO YOUR VACATION!!

--Glen

Davanum Srinivas (JIRA) wrote:
[ https://issues.apache.org/jira/browse/AXIS2-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503449 ] 


Davanum Srinivas commented on AXIS2-2785:
-

Glen,

At this point i don't think anyone is going to change their opinions already stated out on the mailing lists. Could you please start a vote thread with some explicit proposal and we can make a decision and close this issue one way or another? 


thanks,
dims


Service lifecycle
-

Key: AXIS2-2785
URL: https://issues.apache.org/jira/browse/AXIS2-2785
Project: Axis 2.0 (Axis2)
 Issue Type: Improvement
   Affects Versions: 1.2
   Reporter: Michele Mazzucco
   Assignee: Deepal Jayasinghe
   Priority: Blocker

http://www.nabble.com/java.lang.NoSuchMethodException-tf3886972.html




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

[Axis2] Versioning guidelines (was Re: Plan for the hackathon)

2007-06-11 Thread Dennis Sosnoski


+1 for adopting these guidelines for Axis2 Java.

 - Dennis

Samisa Abeysinghe wrote:
To add something, APR people have defined a set of guidelines for 
versioning: http://apr.apache.org/versioning.html
Though APR is a C project, there would be somethings to take form that 
- specially API compatibility with respect to version numbers. What 
could be broken and what should not be broken form major, minor to 
patch versions would help to keep backward compatibility that some 
users are complaining about.


Samisa...

Ajith Ranabahu wrote:

Hi all,
I am sure the Axis2ers around the world are excited about the
hackathon that is about to start tomorrow [Well today - (Monday 11th
June) :)] Unfortunately I can only come for half the days but I'm sure
any major decision will be reported to the list and the irc will be
live as usual (I will participate in the sessions remotely as far as
possible) However more importantly we need to outline the objective
and layout the things we plan to attack.

I will outline some items I felt as important to address while
browsing the Jira list. Others are welcome to jump in and correct me
in any place that I've missed. Again I believe the objective of this
hackathon is to fix whatever is broken in the existing functionality
rather than adding or discussing new features.

1. Exception handling
 Number of issues have been reported about incorrect exception
handling, irrelavant exceptions being thrown etc. So it seems that
this is something we need to look at more carefully and correct.

2 .WSDL2WS and ADB issues
 There are number of 'edge cases' reported about WSDL2WS - specially
against the ADB binding. While some of these will fall into new
features, I suppose we should address all the issues that are against
the existing features and make it work for some of those edge cases.

3. Java2WSDL issues
There are some blockers reported about Java2WSDL. I believe Java2WSDL
works ok for most of the cases but there seems to be some cases we
need to answer. Both for WSDL2WS and Java2WSDL, they are the two most
'visible' components for the users and that makes it important

4. Misc
There are a ton of small issue that does not specifically fall into a
broad category. I'm hoping we can cover most of them by the time we
end up fixing the major issues but we could tackle whatever is
remaining once the major issues are covered.

5. Documentation
While we will not sit and write the user guide once more at this
occasion I see this as a time we can add some of the missing javadocs
to the source (and also correct some header problems. I see a Jira
that says some license headers are not proper)

Anything else we can try to tackle in this limited time frame?

Ajith Ranabahu

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







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

[jira] Assigned: (AXIS2-2771) soap:header removed from WSDL since version 1.2


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

Jaliya Ekanayake reassigned AXIS2-2771:
---

Assignee: Jaliya Ekanayake  (was: Deepal Jayasinghe)

 soap:header removed from WSDL since version 1.2
 ---

 Key: AXIS2-2771
 URL: https://issues.apache.org/jira/browse/AXIS2-2771
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.2
 Environment: Windows XP, Tomcat 5.5, Java SE 5
Reporter: Peter Storch
Assignee: Jaliya Ekanayake
Priority: Blocker
 Attachments: Bank.getBank01.input.wsdl, Bank.getBank01.output.wsdl, 
 Bank.getBank01.xsd


 soap:header elements are removed from WSDL since Version 1.2

-- 
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-2793) WSDL2Java should generate some kind of infrastructure on the server side for soap:headers defined in WSDL

WSDL2Java should generate some kind of infrastructure on the server side for 
soap:headers defined in WSDL
-

 Key: AXIS2-2793
 URL: https://issues.apache.org/jira/browse/AXIS2-2793
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Glen Daniels


Right now we generate extra parameters on Stubs for soap:headers on the 
client side.  We do not do any equivalent for the server side skeletons.  This 
is potentially a problem in that if one of the headers is sent at runtime with 
MustUnderstand=true, we'll get a fault even though we should understand the 
header.

Proposal is to define an ApplicationHeaderHandler which reads metadata from 
AxisService describing which headers the service understands.  It a) checks to 
see that those headers are present in the message (faults if not), b) marks 
them as processed so MU test works, and c) supplies the OMElements in 
convenient properties of the MessageContext.


-- 
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-2703) Global phases after Dispatch are ignored


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

Glen Daniels resolved AXIS2-2703.
-

Resolution: Won't Fix

This actually does work - I hadn't understood that there is a separate copy of 
the operation-specific phases (after Dispatch) for each operation, and those 
copies are pre-filled from the global deployment.  Therefore the later handler 
in the example WILL get called.

No work needed.

 Global phases after Dispatch are ignored
 

 Key: AXIS2-2703
 URL: https://issues.apache.org/jira/browse/AXIS2-2703
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Glen Daniels
Assignee: Glen Daniels
Priority: Blocker
 Fix For: 1.3


 As noted by Afkham in http://www.wso2.org/jira/browse/WSAS-244, we aren't 
 currently respecting any phases deployed in axis2.xml after Dispatch.  This 
 is because in the last line of DispatchPhase.checkPostConditions(), we 
 *overwrite* the ExecutionChain in the MessageContext with the one we get from 
 the operation.  We should be *merging* the operation specific stuff with the 
 original version.  In other words, if we had the following EC:
 Phase1[ h1, h2 ], Dispatch[h3], Phase2[], Phase3[h4]
 ...and an operation which put handler h5 into Phase2, we should end up with:
 Phase1[ h1, h2 ], Dispatch[h3], Phase2[h5], Phase3[h4]
 after dispatching, with the execution point at Phase2.  In particular h4 
 should still be invoked.

-- 
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-2714) Unnecessary recording of directionality in MessageContext executed phases, general improvements to same

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

Glen Daniels commented on AXIS2-2714:
-

Based on hackathon discussion it looks like the second part of this can be
fixed by changing the overwrite of the executionChain to an append in
DispatchPhase when dispatch occurs. Will work on this.

Unnecessary recording of directionality in MessageContext executed phases,
general improvements to same
-

Key: AXIS2-2714
URL: https://issues.apache.org/jira/browse/AXIS2-2714
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Glen Daniels
Assignee: Glen Daniels
Priority: Blocker

When we added the flowComplete() stuff, I think we might have gotten a little
unnecessarily specific about direction in MessageContext and AxisEngine. In
particular - a MessageContext will only ever have a single direction, and
right now we have two separate LinkedLists for executed phases (sic - it's
really Handlers, even though they're usually Phases at the top level). This
bubbles through a lot of the code in AxisEngine too, and it doesn't seem to
be necessary.
I'd like to consider the following two-stage fix for this.
1) Remove all the directionality, and simply have
MessageContext.addExecutedHandler()/resetExecutedHandlers()/getExecutedHandlers().
This removes a bunch of code from MC (simplify simplify) and cleans up
AxisEngine nicely.
2) If AXIS2-2703 is fixed (and therefore a single ExecutionChain will
accurately reflect the entire list of executed handlers), we won't even need
a separate executedHandlers structure at all, and flowComplete() will then be
able to just work backwards from currentHandlerIndex to 0. At that point I
think we could remove it entirely.

--
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-2476) Generated WSDL does not implement the Microsoft rules on wrapping


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

Deepal Jayasinghe updated AXIS2-2476:
-

 Priority: Blocker  (was: Major)
Fix Version/s: 1.3

We need to fix the namespace issue.

 Generated WSDL does not implement the Microsoft rules on wrapping
 -

 Key: AXIS2-2476
 URL: https://issues.apache.org/jira/browse/AXIS2-2476
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
Reporter: Paul Fremantle
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3


 Unfortunately the WSDL that Axis2 generates is not picked up as doc/lit 
 WRAPPED by the Microsoft svcutil tool.
 The reasons are pretty minor. My personal preference would be that Microsoft 
 should fix these, but given that we want Axis2 to interoperate as well as 
 possible I propose that we change these.
 1) WCF svcutil looks at the names of the generated parts. We generate part1 
 but svcutil is looking for the part name parameters. Dumb huh! I have 
 reported this to Microsoft. I propose we also generate the part name 
 parameters since its a simple fix.
 2) WCF svcutil expects the target namespace of the wrapper element to match 
 the target namespace of the WSDL. Frankly I don't understand this either 
 since it doesn't affect the messages on the wire, but here is the comment 
 they produce:
 // CODEGEN: Generating message contract since the wrapper namespace 
 (http://sample/xsd) of message getProfileRequest does not match the default 
 value (http://sample)
 Currently we produce different namespaces - e.g. http://sample for the WSDL 
 and http://sample/xsd for the schema. I propose we also change this to 
 improve interop despite where the blame lies!!!
 I propose we stop appending /xsd since I think it looks ugly :-)

-- 
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-2791) Super class not being generated in WSDL


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

Srinath Perera updated AXIS2-2791:
--

Priority: Blocker  (was: Major)

 Super class not being generated in WSDL
 ---

 Key: AXIS2-2791
 URL: https://issues.apache.org/jira/browse/AXIS2-2791
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
 Environment: AXIS2 under Tomcat on XP
Reporter: Drew Bentley
Priority: Blocker

 XSD for inherited classes is not being generated correctly.
 Example:
 If a Test object extends TestBase the XSD generated is. ns:TestBase does not 
 exist in this XSD:
  wsdl:types
 xs:schema xmlns:ns=http://pkg/xsd; attributeFormDefault=qualified 
 elementFormDefault=qualified targetNamespace=http://pkg/xsd;
   xs:element name=test
 xs:complexType
   xs:sequence
 xs:element name=input nillable=true type=ns:Test/
   /xs:sequence
 /xs:complexType
   /xs:element
   xs:element name=Test type=ns:Test/
   xs:complexType name=Test
 xs:complexContent
   xs:extension base=ns:TestBase
 xs:sequence
   xs:element name=name nillable=true type=xs:string/
 /xs:sequence
   /xs:extension
 /xs:complexContent
   /xs:complexType
   xs:element name=testResponse
 xs:complexType
   xs:sequence
 xs:element name=return nillable=true type=ns:Test/
   /xs:sequence
 /xs:complexType
   /xs:element
 /xs:schema
   /wsdl:types

-- 
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-2603) Java2WSDL does not generate hierarchy if father class is not present in any service operation


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

Eran Chinthaka updated AXIS2-2603:
--

 Priority: Blocker  (was: Major)
Fix Version/s: 1.3

With the recent fix in 2779, this also must have fixed by now. Just making this 
as a blocker as this issue itself is important. 

 Java2WSDL does not generate hierarchy if father class is not present in any 
 service operation
 -

 Key: AXIS2-2603
 URL: https://issues.apache.org/jira/browse/AXIS2-2603
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
 Environment: Windows XP SP2, Java 1.5.0-11, Eclipse plugin generator 
 of Axis2 1.2
Reporter: Jorge Fernández
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3

 Attachments: Administrator.java, API.java, API.wsdl, User.java


 When I have a hierarchy, JAVA2WSDL  generates children correctly (as 
 extension) but it doesn't generate the father if the father is not present as 
 a parameter or return in the API from which I generate the WSDL.

-- 
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-2279) java.lang.NullPointerException at org.apache.axis2.description.ClientUtils.inferInTransport (ClientUtils.java:85)

2007-06-11 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi updated AXIS2-2279:


Priority: Blocker  (was: Major)

 java.lang.NullPointerException at 
 org.apache.axis2.description.ClientUtils.inferInTransport  
 (ClientUtils.java:85)
 --

 Key: AXIS2-2279
 URL: https://issues.apache.org/jira/browse/AXIS2-2279
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.1.1
 Environment: Windows XP, Eclipse 3.2 , jre 1.5.0_06, Axis2 1.1.1
Reporter: oliv g
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: testEDD.java


 java.lang.NullPointerException
   at 
 org.apache.axis2.description.ClientUtils.inferInTransport(ClientUtils.java:85)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:163)
   at 
 fr.acme.www.myapp_v1.AskForPricingStub.AskForPricingOperation(AskForPricingStub.java:150)
   at fr.acme.www.myapp_v1.Client.go(Client.java:51)
 which is not a clear error message.
 Server and client are generated automaticly from the wsdl with Axis2 code 
 generator and xmlbeans databinding within Eclipse
 (same result using wsdl2java.bat)
 Here is the null pointer exception (transportOut is null) at 
 org.apache.axis2.description.ClientUtils.inferInTransport  
 (ClientUtils.java:85) received when launching my client code trying to 
 invoque the available service.
   
   } else {
 //assume listener transport as sender transport
 --listenerTransportProtocol = 
 msgCtxt.getTransportOut().getName().getLocalPart();
 }
 }
 Here is the wsdl :
 ?xml version=1.0 encoding=UTF-8?
 wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
   xmlns:val=http://www.acme.fr/myapp_V1;
   xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
   xmlns:xsd=http://www.w3.org/2001/XMLSchema; name=AskForPricing
   targetNamespace=http://www.acme.fr/myapp_V1;
   wsdl:types
   xsd:schema elementFormDefault=qualified
   targetNamespace=http://www.acme.fr/myapp_V1;
   xsd:include schemaLocation=myappCommonTypes.xsd /
   xsd:element name=Instruments
   xsd:complexType
   xsd:sequence
   xsd:element 
 maxOccurs=unbounded minOccurs=0
   name=Instrument 
 type=val:InstrumentType /
   /xsd:sequence
   /xsd:complexType
   /xsd:element
   xsd:element name=AskForPricingOperationResponse
   xsd:complexType
   xsd:sequence
   xsd:element name=result 
 type=xsd:string /
   /xsd:sequence
   /xsd:complexType
   /xsd:element
   xsd:element name=HeaderNCB 
 type=val:HeaderNCBToFRType /
   xsd:element name=AskForPricingOperation_fault
   xsd:complexType
   xsd:sequence
   xsd:element 
 name=AskForPricingOperation_fault
   type=xsd:string
   /xsd:element
   /xsd:sequence
   /xsd:complexType
   /xsd:element
   /xsd:schema
   /wsdl:types
   wsdl:message name=AskForPricingOperationRequest
   wsdl:part element=val:Instruments name=ListOfInstruments /
   /wsdl:message
   wsdl:message name=AskForPricingOperationRequestHeader
   wsdl:part element=val:HeaderNCB name=RequestHeader /
   /wsdl:message
   wsdl:message name=AskForPricingOperationResponse
   wsdl:part element=val:AskForPricingOperationResponse
   name=Response /
   /wsdl:message
   wsdl:message name=AskForPricingOperation_faultMsg
   wsdl:part element=val:AskForPricingOperation_fault
   name=parameters /
   /wsdl:message
   wsdl:portType name=AskForPricing
   wsdl:operation name=AskForPricingOperation
   wsdl:input message=val:AskForPricingOperationRequest 
 /
   wsdl:output 
 message=val:AskForPricingOperationResponse /
   !--

[jira] Updated: (AXIS2-2606) Disable implicit support for SOAPBinding.Use is ENCODED


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

Glen Daniels updated AXIS2-2606:


Fix Version/s: 1.3

 Disable implicit support for SOAPBinding.Use is ENCODED
 ---

 Key: AXIS2-2606
 URL: https://issues.apache.org/jira/browse/AXIS2-2606
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Reporter: Roy A. Wood Jr.
Assignee: Rich Scheuerle
 Fix For: 1.3

 Attachments: patch_2255_2256.txt


 We do not support SOAPBinding.Use = ENCODED. However, currently we are not 
 flagging this as a validation error in the
 SOAPBinding annotation. With this fix, a webServiceException will be thrown.

-- 
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-2468) Handling of names with '-' symbol


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

Deepal Jayasinghe updated AXIS2-2468:
-

Fix Version/s: 1.3
Affects Version/s: (was: 1.2)
   1.3

 Handling of names with '-' symbol
 -

 Key: AXIS2-2468
 URL: https://issues.apache.org/jira/browse/AXIS2-2468
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.3
 Environment: Ubuntu 6.10, Jdk 1.4.2
Reporter: Jose Antonio
Assignee: Amila Chinthaka Suriarachchi
 Fix For: 1.3

 Attachments: oasis-200401-wss-wssecurity-utility-1.0.xsd, 
 reference-1.1.xsd, wsctx.wsdl, wsctx.xsd


 I have a schema with an attribute named 'reference-scheme' and I need to use 
 it in my code. When I try to generate code using ADB I get the following:
 ..
  // handle attribute reference-scheme
 java.lang.String tempAttribreference-scheme =
   reader.getAttributeValue(,reference-scheme);
if (tempAttribreference-scheme!=null){
  java.lang.String content = 
 tempAttribreference-scheme;
 
  object.setReferenceScheme(
 
 org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference-scheme));
 
 } else {

 }
 handledAttributes.add(reference-scheme);
 
 
 reader.next();
 .
 And that doesn't compile, so when an attribute or element name contains a '-' 
 character, the generated variables should replace it by _ so it generates the 
 following code:
 ..
  // handle attribute reference-scheme
 java.lang.String tempAttribreference_scheme =
   reader.getAttributeValue(,reference-scheme);
if (tempAttribreference_scheme!=null){
  java.lang.String content = 
 tempAttribreference_scheme;
 
  object.setReferenceScheme(
 
 org.apache.axis2.databinding.utils.ConverterUtil.convertToAnyURI(tempAttribreference_scheme));
 
 } else {

 }
 handledAttributes.add(reference-scheme);
 
 
 reader.next();
 .
 That compiles or something similar.

-- 
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-2461) -ns2p switch ignored when using wsdl2java with xmlbeans databindings


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

Deepal Jayasinghe updated AXIS2-2461:
-

Priority: Blocker  (was: Major)

This is smt we need to fix for 1.3

 -ns2p switch ignored when using wsdl2java with xmlbeans databindings
 

 Key: AXIS2-2461
 URL: https://issues.apache.org/jira/browse/AXIS2-2461
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2, 1.1.1
 Environment: Java 1.5.0_09 
Reporter: Murray Furtado
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker

  I want to override the default package my xml beans get generated in. 
  
 I issue my wsdl2java command with eg -ns2p http://www.xyx.com=com.abc.efg  or 
 -ns2p www.xyx.com=com.abc.efg 
 When I do so, my classes get generated in a package com.xyx.www.impl 
 regardless

-- 
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-2454) No indication given when the TCPserver is started


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

Deepal Jayasinghe updated AXIS2-2454:
-

Fix Version/s: 1.3
Affects Version/s: (was: 1.2)
   1.3

 No indication given when the TCPserver is started
 -

 Key: AXIS2-2454
 URL: https://issues.apache.org/jira/browse/AXIS2-2454
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: transports
Affects Versions: 1.3
 Environment: winxp, jdk15, tomcat 6.0.10
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Minor
 Fix For: 1.3


 User is not informed when tcp server is started. It just shows the following 
 output.
 TCPServer repositoryLocation port

-- 
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-2599) Document simple deployment


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

Eran Chinthaka resolved AXIS2-2599.
---

   Resolution: Fixed
Fix Version/s: 1.3

Since there is some sort of documentation on this within Dims' blog, let's 
close this. And this JIRA will point to the documentation. 

 Document simple deployment
 

 Key: AXIS2-2599
 URL: https://issues.apache.org/jira/browse/AXIS2-2599
 Project: Axis 2.0 (Axis2)
  Issue Type: Task
  Components: documentation
Affects Versions: 1.2
 Environment: N/A
Reporter: Joshua White
Assignee: Chatra Nakkawita
Priority: Minor
 Fix For: 1.3


 Simple deployment does not involve any additional archive files.  Copy your 
 services.xml as well as wsdl/xsd's into the WEB-INF folder and place your 
 classes in WEB-INF/classes and libs in WEB-INF/lib.  Leave the axis2.xml in 
 /WEB-INF/conf/axis2.xml.  (Does it also work when placed directly under 
 WEB-INF?).
 This is a great feature for those who want a simple deployment or those who 
 have classloader issues (Such as weblogic 8..1.x) and are unable to deploy in 
 the standard way.
 Regards,
 Joshua

-- 
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-2451) WS Policy Attachments for services.xml


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

Deepal Jayasinghe updated AXIS2-2451:
-

Priority: Blocker  (was: Major)

Hi Sanka ,
If we are going to do this , then do that for 1.3

 WS Policy Attachments for services.xml
 --

 Key: AXIS2-2451
 URL: https://issues.apache.org/jira/browse/AXIS2-2451
 Project: Axis 2.0 (Axis2)
  Issue Type: New Feature
Reporter: Nencho Lupanov
Assignee: Sanka Samaranayake
Priority: Blocker
 Attachments: PolicyEngine.diff, PolicyReaderThread.java, 
 PolicyReference.diff, PolicyReference.diff


 Axis2 does not recognize policy references in services.xml.
 Implementation should alow usage such:
  wsp:PolicyReference
  URI=http://localhost:53307/policy.xml#UTOverTransport; /
 /wsp:PolicyAttachment

-- 
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-2450) Building generated code (xmlbeans based databinding) creates jars with duplicate content


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

Deepal Jayasinghe updated AXIS2-2450:
-

Priority: Blocker  (was: Major)

 Building generated code (xmlbeans based databinding) creates jars with 
 duplicate content
 

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


 Attached zip file contains xmlbeans based stubs generated using 
 StockQuoteService.wsdl file comes with Axis2 distro.
 To produce the issue :
 - I first generated the stubs, using following command :
 wsdl2java -uri StockQuoteService.wsdl -p com.mycompany -d xmlbeans
 - Then I build build.xml with ant.
 Check  StockQuoteService-test-client.jar and XBeans-packaged.jar files. You 
 will see the same set of .xsb
 files are packaged into both jar files.
 Entire directory with generated jar files mentioned above is attached.

-- 
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-2438) wsdl2java's generated build.xml file needs ${classes} added to classpath of run.test target


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

Deepal Jayasinghe updated AXIS2-2438:
-

Fix Version/s: (was: 1.1.1)
   1.3
Affects Version/s: 1.3

 wsdl2java's generated build.xml file needs ${classes} added to classpath of 
 run.test target
 ---

 Key: AXIS2-2438
 URL: https://issues.apache.org/jira/browse/AXIS2-2438
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.3
Reporter: Glen Mazza
Assignee: Amila Chinthaka Suriarachchi
Priority: Minor
 Fix For: 1.3

 Attachments: wsdl2javapatch.txt


 When running the run.test target without modification, JUnit reports an 
 error that it can't find the compiled JUnit test class.  Adding ${classes} to 
 the classpath of the run.test target fixes this problem.  This would seem to 
 be needed just for Ant files of the binding frameworks (ADB and JIBX)  that 
 depend on the compile.test target--because ${classes} is exactly where the 
 compiled JUnit test class is placed.

-- 
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-2264) org.apache.axis2.AxisFault: Incoming message input stream is null while engaging addressing module on client side

2007-06-11 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi updated AXIS2-2264:


Priority: Blocker  (was: Major)

 org.apache.axis2.AxisFault: Incoming message input stream is null while 
 engaging addressing module on client side
 ---

 Key: AXIS2-2264
 URL: https://issues.apache.org/jira/browse/AXIS2-2264
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.1.1
 Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 1.1.1
Reporter: Federica Ciotti
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: AddService.java, Constants.java, MultiplyService.java, 
 newCalc.aar


 My client class needs to engage addressing module.
 This is my client
 package calc1;
 public class RPC_MyCalcClient {
   public static void main(String[] args){
   try{
   EndpointReference targetEPR = new 
 EndpointReference(http://localhost:8080/axis2/services/AddService/;);
   EndpointReference myEPR = new 
 EndpointReference(http://localhost:8080/axis2/services/clientService/;);
   Options options = new Options();
   options.setTo(targetEPR);
   options.setReplyTo(myEPR);
   options.setFrom(myEPR);
   //options.setAction(addPrevious);
   options.setAction(add);
   options.setFrom(myEPR);
   options.setMessageId(Msg123);

   RPCServiceClient sender = new RPCServiceClient();
   sender.setOptions(options);
   sender.engageModule(new 
 QName(Constants.MODULE_ADDRESSING));
   //add
   QName opAdd = new QName(http://calc/xsd;, add);
   Integer a = new Integer(1);
   Integer b = new Integer(2);
   Object[] params = new Object[] { a, b };
   Class[] returnTypes = new Class[] { Integer.class };
   Object[] response = sender.invokeBlocking(opAdd, 
 params, returnTypes);
   Integer result = (Integer) response[0];
   if (result == null) {System.out.println(Null);}
   else System.out.println(Result + result.toString());
   
   //addPrev
   /*QName opAdd = new QName(http://calc/xsd;, 
 addPrevious);
   Integer a = new Integer(1);
   Object[] params = new Object[] { a};
   Class[] returnTypes = new Class[] { Integer.class };
   Object[] response = sender.invokeBlocking(opAdd, 
 params, returnTypes);
   Integer result = (Integer) response[0];
   if (result == null) {System.out.println(Null);}
   else System.out.println(Result + result.toString());*/
   }catch(AxisFault a){a.printStackTrace();}
   }
 }
 Even if the addressing module is in the classpath I get AxisFault. 
 This is the exception i get trying to engage addressing module on client side
 org.apache.axis2.AxisFault: Incoming message input stream is null
   at 
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:64)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:252)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
   at 
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579)
   at 
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
   at 
 org.apache.axis2.rpc.client.RPCServiceClient.invokeBlocking(RPCServiceClient.java:95)
   at calc1.RPC_MyCalcClient.main(RPC_MyCalcClient.java:52)
 I noticed from SOAPMonitor that apart the AxisFault the request and response 
 messages are correct but only the request one has the wsa header fields:
 SOAPRequest
 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; 
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
   soapenv:Header
 wsa:Tohttp://localhost:8080/axis2/services/AddService//wsa:To
 wsa:ReplyTo
   
 wsa:Addresshttp://localhost:8080/axis2/services/clientService//wsa:Address
 /wsa:ReplyTo
 wsa:From
   
 wsa:Addresshttp://localhost:8080/axis2/services/clientService//wsa:Address
 /wsa:From
 wsa:MessageIDMsg123/wsa:MessageID

[jira] Updated: (AXIS2-2249) Codegen is not able to compile multiple WSDL with the same instance of ant task

2007-06-11 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi updated AXIS2-2249:


Priority: Blocker  (was: Major)

 Codegen is not able to compile multiple WSDL with the same instance of ant 
 task
 ---

 Key: AXIS2-2249
 URL: https://issues.apache.org/jira/browse/AXIS2-2249
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.1
Reporter: Sebastian Gil
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: build-test.xml


 In case that there is an attempt to execute codegen from many task withing 
 the same ant session. Compilation fails with: Error parsing WSDL. Solution is 
 to create separate task deffinitions.

-- 
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-2431) JAXB code generation failure


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

Deepal Jayasinghe updated AXIS2-2431:
-

Priority: Blocker  (was: Critical)

 JAXB code generation failure
 

 Key: AXIS2-2431
 URL: https://issues.apache.org/jira/browse/AXIS2-2431
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: nightly
Reporter: Dennis Sosnoski
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: jaxb-issue.zip


 Trying to use JAXB data binding with Wsdl2Java results in 
 NullPointerException:
  [java] Caused by: java.lang.NullPointerException
  [java] at 
 org.apache.axis2.jaxbri.CodeGenerationUtility.processSchemas(CodeGenerationUtility.

-- 
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-2699) Documentation http transport BASIC authentication outdated


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

Jaliya Ekanayake reassigned AXIS2-2699:
---

Assignee: Jaliya Ekanayake  (was: Chatra Nakkawita)

 Documentation http transport BASIC authentication outdated
 --

 Key: AXIS2-2699
 URL: https://issues.apache.org/jira/browse/AXIS2-2699
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: transports
Affects Versions: 1.2
Reporter: Andreas Schoedl
Assignee: Jaliya Ekanayake
Priority: Minor

 Example on bottom of page 
 http://ws.apache.org/axis2/1_2/http-transport.html#preemptive_auth
 last line says:  
 options.setProperty(org.apache.axis2.transport.http.HTTPConstants.BASIC_AUTHENTICATE,auth);
 should say:
 options.setProperty(org.apache.axis2.transport.http.HTTPConstants.AUTHENTICATE,auth);
 Also I'd like to see 
 auth.setPreemptiveAuthentication(true);
 documented, here which is already in the HTML anchor (see URL), but not 
 mentioned. 

-- 
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-2248) unreliable behavior of sendRobust

2007-06-11 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi updated AXIS2-2248:


Priority: Blocker  (was: Major)

 unreliable behavior of sendRobust
 -

 Key: AXIS2-2248
 URL: https://issues.apache.org/jira/browse/AXIS2-2248
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: client-api
 Environment: linux, sun jdk 1.5.0_10
Reporter: Michele Mazzucco
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: nightly

 Attachments: axis2_logs_double.log, axis2_logs_single.log, 
 catalina_double.out, catalina_single.out, qosp_debug_double.log, 
 qosp_debug_single.log


 The sendRobust method is not reliable at all. Messages are delivered to the 
 destination, but on the sender side errors happen (and this causes me some 
 big troubles).
 The used ConfigurationContext is:
 multiThreadedConfigurationContext = ConfigurationContextFactory 
 //.createEmptyConfigurationContext();
 .createConfigurationContextFromFileSystem(null, null);
 MultiThreadedHttpConnectionManager connectionManager = new 
 MultiThreadedHttpConnectionManager();
 HttpConnectionManagerParams params = new HttpConnectionManagerParams();
 params.setDefaultMaxConnectionsPerHost(5);
 params.setMaxTotalConnections(200);
 params.setStaleCheckingEnabled(true);
 connectionManager.setParams(params);
 HttpClient httpClient = new HttpClient(connectionManager);
 multiThreadedConfigurationContext.setProperty(
 HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
 multiThreadedConfigurationContext.setProperty(
 HTTPConstants.CACHED_HTTP_CLIENT, httpClient);

-- 
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-2243) When running the databinding sample if a wrong symbol is specified, a successful response is given without throwing an error

2007-06-11 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi updated AXIS2-2243:


Priority: Blocker  (was: Major)

 When running the databinding sample if a wrong symbol is specified, a 
 successful response is given without throwing an error
 

 Key: AXIS2-2243
 URL: https://issues.apache.org/jira/browse/AXIS2-2243
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: samples
Affects Versions: nightly
 Environment: Windows XP, JDK 1.4.2_13, Firefox version 1.5.0.8
Reporter: Evanthika Amarasiri
Assignee: Davanum Srinivas
Priority: Blocker

 Was running the databinding sample and experienced the following. Below are 
 the steps taken to produce the issue
 1. Execute the command ant run.client 
 -Durl=http://localhost:8080/axis2/services/StockQuoteService -Dsymbol=IBM 
 and received the results successfully.
 2. Executed the same command with a wrong symbol
 E.g.:- ant run.client 
 -Durl=http://localhost:8080/axis2/services/StockQuoteService -Dsymbol=TEST
  and you will still get the same results.
 Since this symbol does not exist, it should throw an error instead.

-- 
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-2231) not able to call a service from another service

2007-06-11 Thread Amila Chinthaka Suriarachchi (JIRA)


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

Amila Chinthaka Suriarachchi updated AXIS2-2231:


Priority: Blocker  (was: Major)

 not able to call a service from another service
 ---

 Key: AXIS2-2231
 URL: https://issues.apache.org/jira/browse/AXIS2-2231
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
 Environment: windows xp 
Reporter: Shree Rangan
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: JaguarClient.java, JaguarService.java, SecondService.java


 I have a POJO exposed as a Webservice using Axis2. I have tested this 
 service using RPCServiceClient and it works fine. This service needs to talk 
 to other services which are also POJO's exposed as Webservices using Axis2. 
 The other services also work fine when invoked by RPCServiceClient mechanism. 
 But if I invoke those services from my Axis2 service using the same mechanism 
 of RPCServiceClient mechanism, it gives me the following exception. 
 java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:585)
   at 
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:118)
   at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:493)
   at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:319)
   at 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:247)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
   at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
   at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
   at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
   at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
   at 
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
   at 
 org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
   at 
 org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
   at 
 org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
   at 
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:595)
 Caused by: java.lang.NullPointerException
   at 
 org.apache.axis2.context.MessageContext.isHeaderPresent(MessageContext.java:1054)
   at 
 org.apache.axis2.handlers.addressing.AddressingInHandler.invoke(AddressingInHandler.java:72)
   at org.apache.axis2.engine.Phase.invoke(Phase.java:381)
   at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:518)
   at org.apache.axis2.engine.AxisEngine.receiveFault(AxisEngine.java:596)
   at 
 org.apache.axis2.description.RobustOutOnlyAxisOperation$RobustOperationClient.send(RobustOutOnlyAxisOperation.java:99)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:295)
   at 
 org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:453)
   at 
 org.apache.axis2.client.ServiceClient.sendRobust(ServiceClient.java:380)
   at 
 org.apache.axis2.rpc.client.RPCServiceClient.invokeRobust(RPCServiceClient.java:131)
   at sample.pojo.service.JaguarService.meth2(Unknown Source)
   ... 25 more
 here, i am calling meth2(the first service) from the client using 
 RPCServiceClient. 
 from meth2 i am calling meth3(the second service) using RPCServiceClient 
 again. 
 the services work fine independently, when invoked from within a client. 
 the exception is only when the second service is invoked from within another 
 service. 

-- 
This message is automatically generated by JIRA.
-
You

[jira] Updated: (AXIS2-2426) Policy-driven code generation is broken


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

Deepal Jayasinghe updated AXIS2-2426:
-

Priority: Blocker  (was: Critical)

if you are doing this , let's do this for 1.3

 Policy-driven code generation is broken
 ---

 Key: AXIS2-2426
 URL: https://issues.apache.org/jira/browse/AXIS2-2426
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.1.1
 Environment: Apache Tomcat 5.5.23 , WinXP Pro, Axis2 1.1.1 , 
 rampart-1.1 , etc.
Reporter: Angel Todorov
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Fix For: nightly


 When I have a policy in my WSDL , the policy-enforcement is not affected in 
 the generated code. 
 Here is the problem reported by email:
 Hi,
 I have seen policy-driven code generation as a feature of Axis2, but
 I couldn't get it to work properly. Is this feature currently
 supported in Axis2 ? If yes, where can I find a sample demonstrating
 it?
 What I assume it means, is to have a policy (let's say UsernameToken
 auth) in my WSDL, and when I run wsdl2java, I would like to have the
 rampart module automatically engaged in the generated stubs, and most
 of the setups of the module -  auto generated. To sum it up:
 1) given a WSDL with policy definitions in it
 2) run wsdl2java
 3) the tool generates code in the stub that activates the policy
 Thanks.
 Regards,
 Angel

-- 
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-2594) Using attributeFormDefault=qualified in a schema causes null attribute values in Java objects


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

Eran Chinthaka updated AXIS2-2594:
--

Fix Version/s: 1.3
 Priority: Blocker  (was: Minor)

 Using attributeFormDefault=qualified in a schema causes null attribute 
 values in Java objects
 ---

 Key: AXIS2-2594
 URL: https://issues.apache.org/jira/browse/AXIS2-2594
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.1.1
 Environment: Windows XP
 Java 1.6.0
 XMLBeans data binding
Reporter: Paul Chisholm
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Fix For: 1.3


 When the schema that appears in the wsdl:types section of a WSDL file 
 specifies attributeFormDefault=qualified then the the getter corresponding 
 to an attribute returns null even though an attribute value is specified in 
 the XML.
 Example:
 Schema is
 xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://quickstart.samples/xsd;
   xs:element name=attribute
 xs:complexType
   xs:sequence
 xs:element name=value nillable=true type=xs:string /
   /xs:sequence
   xs:attribute name=status type=xs:string /
 /xs:complexType
   /xs:element
   xs:element name=attributeResponse
 xs:complexType
   xs:sequence
 xs:element name=value nillable=true type=xs:string /
   /xs:sequence
   xs:attribute name=status type=xs:string /
 /xs:complexType
   /xs:element
 /xs:schema
 Message/port definition is
 wsdl:message name=attributeMessage
   wsdl:part name=part1 element=ns:attribute/
 /wsdl:message 
 wsdl:message name=attributeResponseMessage
   wsdl:part name=part1 element=ns:attributeResponse/ 
 /wsdl:message
 wsdl:portType name=MyServicePortType
   wsdl:operation name=attribute
 wsdl:input message=axis2:attributeMessage/
 wsdl:output message=axis2:attributeResponseMessage/
   /wsdl:operation
 /wsdl:portType
 Client code is
public static void attribute(MyServiceStub stub){
 try{
 AttributeDocument reqDoc = 
 AttributeDocument.Factory.newInstance();
 AttributeDocument.Attribute req = reqDoc.addNewAttribute();
 req.setStatus(OK);
 req.setValue(Testing);
 AttributeResponseDocument res = stub.attribute(reqDoc);
 
 System.err.println(Status=+res.getAttributeResponse().getStatus());
 
 System.err.println(Value=+res.getAttributeResponse().getValue());
 } catch(Exception e){
 e.printStackTrace();
 System.err.println(\n\n\n);
 }
}
 Service code is
 public AttributeResponseDocument attribute(AttributeDocument param1) {
 String status = param1.getAttribute().getStatus();
 String value = param1.getAttribute().getValue();
 System.err.println();
 System.err.println(Status=+status);
 System.err.println(Value=+value);
 AttributeResponseDocument resDoc =
 AttributeResponseDocument.Factory.newInstance();
 AttributeResponseDocument.AttributeResponse res =
 resDoc.addNewAttributeResponse();
 res.setStatus(status);
 res.setValue(value);
 return resDoc;
 }
 When the client is run tracing of the element values displays as expected, 
 but tracing of the attributes always shows null.
 If the schema is changed to attributeFormDefault=unqualified the attribute 
 values are displayed successfully.

-- 
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-2423) 'Emitter class not found' exception thrown when csharp is specified as the output language in wsdl2java


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

Deepal Jayasinghe updated AXIS2-2423:
-

Priority: Blocker  (was: Major)

 'Emitter class not found' exception thrown when csharp is specified as the 
 output language in wsdl2java
 ---

 Key: AXIS2-2423
 URL: https://issues.apache.org/jira/browse/AXIS2-2423
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.2
 Environment: winxp, jdk15, Axis2-1.2-RC1
Reporter: Charitha Kankanamge
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker

 Following exception thrown when csharp is given as the output language in 
 code generation. (wsdl2java.bat  -l charp 
 Exception in thread main 
 org.apache.axis2.wsdl.codegen.CodeGenerationException: java.lang.Exception: 
 Emitter class not found!
 at 
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:251
 )
 at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
 at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
 Caused by: java.lang.Exception: Emitter class not found!
 at 
 org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:227
 )
 ... 2 more

-- 
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-2417) unimplemented code in kernel module saaj SOAPPartImpl


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

Deepal Jayasinghe updated AXIS2-2417:
-

Priority: Blocker  (was: Major)

Sumeda,
Will you be able to finish this before 1.3 ?

 unimplemented code in kernel module saaj SOAPPartImpl
 -

 Key: AXIS2-2417
 URL: https://issues.apache.org/jira/browse/AXIS2-2417
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
 Environment: discovered in running new JAXWS AddNumbersHandler tests
Reporter: Mike Rheinheimer
Assignee: sumedha rubasinghe
Priority: Blocker
 Attachments: axis-2417.patch, 
 TEST-org.apache.axis2.jaxws.sample.AddNumbersHandlerTests.xml


 When JAXWS handlers are present in an endpoint implementation, or client app, 
 they may obviously have access to the SOAP message elements in a given SOAP 
 message.  This requires that the message be demarshalled for a handler's use. 
  In this case, the handler would be using the 
 org.apache.axis2.saaj.SOAPPartImpl class from the axis2 kernel module to get 
 and set elements in the SOAP message.  Hardly anything is implemented in this 
 class; there are 58 occurances of TODO in there.
 To reproduce the problem, download and build the axis2 environment with the 
 org.apache.axis2.jaxws.sample.AddNumbersHandler tests enabled (by removing 
 the '_' from the method names in that class)... or a simple reading of the 
 SOAPPartImpl will show the unimplemented code.

-- 
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-2592) AxisServlet does not respect Servlet Context paths with slashes


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

Eran Chinthaka updated AXIS2-2592:
--

Fix Version/s: 1.3
 Priority: Blocker  (was: Major)

 AxisServlet does not respect Servlet Context paths with slashes
 ---

 Key: AXIS2-2592
 URL: https://issues.apache.org/jira/browse/AXIS2-2592
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: nightly
 Environment: Tomcat 6 or Glassfish 9 on Windows XP.
Reporter: Steven E. Harris
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3


 AxisServlet.initContextRoot() inspects the Servlet parameter 
 axis2.find.context to figure out whether it should use the contextRoot 
 parameter specified in axis2.xml, or attempt to discover the Servlet's 
 context path from the current request, per this discussion:
 svn commit: r468722 ...
 http://mail-archives.apache.org/mod_mbox/ws-axis-cvs/200610.mbox/[EMAIL 
 PROTECTED]
 The problem lies with the following portion of initContextRoot():
 if (contextRoot == null || contextRoot.trim().length() == 0) {
 String[] parts = JavaUtils.split(req.getContextPath(), '/');
 if (parts != null) {
 for (int i = 0; i  parts.length; i++) {
 if (parts[i].length()  0) {
 contextRoot = parts[i];
 break;
 }
 }
 }
 if (contextRoot == null || req.getContextPath().equals(/)) {
 contextRoot = /;
 }
 configContext.setContextRoot(contextRoot);
 }
 For some reason, this code takes the current request's reported context path 
 and splits it on slashes, taking only the first token as the context path. 
 This fails with Servlets deployed with context paths containing slashes.
 As an example, my Servlet is deployed with a context path of 2007/04 and an 
 Axis2 servicePath of ws. That is, services should be found via
   http://my server/2007/04/ws/service name
 I specified 2007/04 in axis2.xml as my contextRoot, but Axis2 winds up 
 ignoring this parameter anyway if the axis2.find.context Servlet parameter 
 is not set to false. Upon the first real request arriving, 
 AxisServlet.initContextRoot() runs. It decides to try to honor the Servlet's 
 context path, and retrieves it via HttpServletRequest.getContextPath(). This 
 function returns /2007/04. But the split operation chops this up and 
 selects 2007 as the the context root, then proceeds to set this as the 
 configurationContext's contextRoot.
 This causes the configurationContext's serviceContextPath value to get 
 rewritten as 2007/ws, which fails to locate a service.
 The fix is to not try splitting up the HttpServletRequest's context path. 
 Perhaps you want to remove the leading slash, but there's no reason that we 
 should be only honoring the name components before the first slash beyond the 
 leading one.

-- 
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-2591) useOriginalwsdl return the custom wsdl including the imported definitions


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

Eran Chinthaka updated AXIS2-2591:
--

Fix Version/s: 1.3
 Priority: Blocker  (was: Major)

 useOriginalwsdl return the custom wsdl including the imported definitions
 -

 Key: AXIS2-2591
 URL: https://issues.apache.org/jira/browse/AXIS2-2591
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.1.1
 Environment: Linux Fedora fc5, tomcat 6.0.7, java1.5.0_11, Axis2 1.1.1
Reporter: Federica Ciotti
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3

 Attachments: StockQuoteService.wsdl, StockQuoteService.wsdl


 My wsdl in META-INF contains only the import elemnt and a wsdl:service 
 element.
 Even if  useOriginalwsdl parameter is included in services.xml all the 
 definition are generated while accessing the wsdl from ?wsdl.

-- 
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-2415) Service invocation fails when original wsdl is included in the service archive and generate client code using ?wsdl


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

Deepal Jayasinghe updated AXIS2-2415:
-

Priority: Blocker  (was: Major)

 Service invocation fails when original wsdl is included in the service 
 archive and generate client code using ?wsdl
 ---

 Key: AXIS2-2415
 URL: https://issues.apache.org/jira/browse/AXIS2-2415
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.2
 Environment: winxp, jdk15, tomcat 6.0.10
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: Mathsclass-doc.wsdl, myAxisService.aar, 
 MyAxisservice.wsdl


 I observed the following behavior in axis2-1.2 RC1 and seems to be a bug. I 
 noticed that the wsdl file generated by java2wsdl and ?wsdl are different 
 even if the service implementation class is same. 
 I deployed a service and generated client using the wsdl2java by specifying 
 http://localhost:8080/axis2/services/servicename?wsdl as url. 
 Then I wrote a java client and accessed the service successfully.
 After that, I generated the wsdl of the same service by using java2wsdl 
 command.
 Then I added the generated wsdl in to the META-INF directory of the service 
 archive and set useOriginalwsdl=true in services.xml
 Restarted the tomcat server and sent the same request through the java client 
 which was written previously.
 Then the following exception was thrown and listed in tomcat server console.
 SEVERE: Exception occurred while trying to invoke service method addnumbers
 java.lang.IllegalArgumentException: wrong number of arguments
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at 
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:95)
 at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
 at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:144)
 at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:279)
 at 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:116)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
 at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
 at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:228)
 at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
 at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
 at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
 at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
 at 
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
 at 
 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:634)
 at 
 org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
 at java.lang.Thread.run(Thread.java:595)
 Steps to reproduce:
 
 1. Deploy a service archive
 2. Generate client stubs using wsdl2java by specifying ?wsdl url of the 
 service (-uri http://localhost:8080/axis2/services/MyAxisservice?wsdl) and 
 write a client
 3. Invoke the service. This should be successful.
 4. Now generate the wsdl using same service implementation class (java2wsdl)
 ie:- java2wsdl -cn Mathsclass -o C:\Axis2\axis2-1.2-RC1\bin\out -cp . -sn 
 MyAxisservice
 5. Add the generated wsdl in to service archive and set useOriginalwsdl=true 
 in services.xml
 6. Redeploy the same service and invoked it through the above client
 Please find the attached wsdl files for more information
 1. Mathsclass-doc.wsdl is the wsdl generated by java2wsdl command
 2. MyAxisservice.wsdl is the one generated by ?wsdl

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

[jira] Assigned: (AXIS2-2696) namespaceURI problems when moving form Axis2 1.1.1 to Axis2 1.2


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

Jaliya Ekanayake reassigned AXIS2-2696:
---

Assignee: Jaliya Ekanayake  (was: Deepal Jayasinghe)

 namespaceURI problems when moving form Axis2 1.1.1 to Axis2 1.2
 ---

 Key: AXIS2-2696
 URL: https://issues.apache.org/jira/browse/AXIS2-2696
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.2
 Environment: Windows XP, Tomcat 5.5
Reporter: Dobri Kitipov
Assignee: Jaliya Ekanayake
Priority: Blocker
 Attachments: screenshot-from-my-Eclipse.jpg


 Hi everybody,
 We have a project that used to work with Axis2 v.1.1.1. Currently, we are 
 trying to migrate to Axis2 v.1.2. The problem is that the test I call in 
 order to verify that everything is ok works fine with v.1.1.1, but not with 
 v.1.2.
 I use XMLSpy to send the following request (note the namespaceURI passed in 
 bold):
 SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 xmlns:m0=http://sample.application/shiporders;
   SOAP-ENV:Body
   m:create 
 xmlns:m=http://sdo.generated.shiporders.ShiporderAccessService/operations;
   m:param0
   m0:id3/m0:id
   m0:orderpersonString/m0:orderperson
   m0:shipto
   m0:nameString/m0:name
   m0:addressString/m0:address
   m0:cityString/m0:city
   m0:countryString/m0:country
   /m0:shipto
   m0:item
   m0:titleString/m0:title
   m0:noteString/m0:note
   m0:quantity127/m0:quantity
   m0:price0.0/m0:price
   /m0:item
   /m:param0
   /m:create
   /SOAP-ENV:Body
 /SOAP-ENV:Envelope
 The problem is that the namespaceURI passed (m:create 
 xmlns:m=http://sdo.generated.shiporders.ShiporderAccessService/operations; 
 ) is missing when retrieved from msgContext.axisOperation.name.namespaceURI, 
 but still available from msgContext.axisMessage.elementQname.namespaceURI.
 I tested this with the already mentioned 
 http://wso2.org/repos/wso2/people/saliya/ScraperService/ScraperService.aar 
 into the JIRA's kernel issues part (see 
 http://issues.apache.org/jira/browse/AXIS2-2663). I deployed this aar into my 
 Tomcat (which is debug mode). Then I used the XmlSpy in order to send a 
 request to the Scraper WS:
 SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema;
   SOAP-ENV:Body
   m:scrape xmlns:m=http://mashup.wso2.org/xsd;
   m:scrapehaha/m:scrape
   /m:scrape
   /SOAP-ENV:Body
 /SOAP-ENV:Envelope
 I have set a breakpoint into 
 org.apache.axis2.receivers.RawXMLINOutMessageReceiver class into 
 invokeBusinessLogic(MessageContext msgContext, MessageContext newmsgContext) 
 method. At this point you can see (as I already mentioned) that the 
 namespaceURI (http://mashup.wso2.org/xsd;) is available into 
 msgContext.axisMessage.elementQname.namespaceURI, but not into 
 msgContext.axisOperation.name.namespaceURI.
 Thank you in advance!
 Regards,
 Dobri

-- 
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-2774) Lack of support for XML Schema Inheiritance


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

Srinath Perera updated AXIS2-2774:
--

Priority: Blocker  (was: Major)

 Lack of support for XML Schema Inheiritance
 ---

 Key: AXIS2-2774
 URL: https://issues.apache.org/jira/browse/AXIS2-2774
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
 Environment: Windows
Reporter: Raine Fujisama
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: ConsumerManagerTrial3.wsdl


 I wrote a WSDL, ran wsdl2java.bat to generate server side code.  Compiled.  
 Build the aar and deployed it in tomcat.
 I then sent it a couple sample soap files and got unexpected results.  This 
 makes me think that some of the xsd features I used are not supported by 
 Axis, namely the abstract attribute and inheiritance of complex types.  Can 
 someone confirm my suspicions or tell me where I'm going wrong?
 The first message I sent was:
 SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 xmlns:m0=http://consumermgr.sss.com/consumermgr;
 SOAP-ENV:Body
 m:addDevice xmlns:m=http://consumermgr.sss.com; 
 SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
 addDeviceInputParam
 m0:header
 m0:timestamp2001-12-17T09:30:47.0Z/m0:timestamp
 m0:fromId0/m0:fromId
 /m0:header
 m0:deviceId
 m0:idType/
 m0:id/
 /m0:deviceId
 m0:attributes/m0:attributes/
 /addDeviceInputParam
 /m:addDevice
 /SOAP-ENV:Body
 /SOAP-ENV:Envelope
 The response I got was:
 ?xml version=1.0 encoding=UTF-8?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Body
 soapenv:Fault
 faultcodesoapenv:Client/faultcode
 faultstringPlease implement 
 com.sss.consumermgr.consumermgr.ConsumerMgrServiceSkeleton#addDevice/faultstring
 detail/
 /soapenv:Fault
 /soapenv:Body
 /soapenv:Envelope
 apparently meaning that the soap message was validated.  How can this be?!  
 m0:attributes is defined as a complextype for which abstract=true.  That 
 means that it is invalid for it to appear in an actual instance!  Is the 
 abstract attribute not supported by Axis???
 The second soap message I sent was:
 SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/; 
 xmlns:SOAP-ENC=http://schemas.xmlsoap.org/soap/encoding/; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 xmlns:m0=http://consumermgr.sss.com/consumermgr;
 SOAP-ENV:Body
 m:addDevice xmlns:m=http://consumermgr.sss.com; 
 SOAP-ENV:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
 addDeviceInputParam
 m0:header
 m0:timestamp2001-12-17T09:30:47.0Z/m0:timestamp
 m0:fromId0/m0:fromId
 /m0:header
 m0:deviceId
 m0:idType/
 m0:id/
 /m0:deviceId
 m0:attributes 
 xsi:type=STBAttributeSetTypem0:passwordMyPW/m0:password/m0:attributes/
 /addDeviceInputParam
 /m:addDevice
 /SOAP-ENV:Body
 /SOAP-ENV:Envelope
 The Response was:
 ?xml version=1.0 encoding=UTF-8?
 soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Body
 soapenv:Fault
 faultcodesoapenv:Client/faultcode
 faultstringjava.lang.RuntimeException: Unsupported type null 
 STBAttributeSetType/faultstring
 detail/
 /soapenv:Fault
 /soapenv:Body
 /soapenv:Envelope
 Now in my schema STBAttributeSetType is defined as extending an abstract 
 complex type.  attributes is of type that abstract type.  Therefore the 
 axis-generated server code should like STBAttributeSetType.  Does the 
 Unsupported type error it returns mean that axis doesn't support 
 complextype inheiritance?

-- 
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-2589) com.ctc.wstx.exc.WstxParsingException: Expected a text token, got START_ELEMENT.


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

Eran Chinthaka updated AXIS2-2589:
--

Fix Version/s: 1.3
 Priority: Blocker  (was: Critical)

 com.ctc.wstx.exc.WstxParsingException: Expected a text token, got 
 START_ELEMENT.
 

 Key: AXIS2-2589
 URL: https://issues.apache.org/jira/browse/AXIS2-2589
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: om
Affects Versions: 1.1.1
 Environment: WindowsXP, Java 1.4.2, Eclipse 3.2.1
Reporter: Stuart Bell
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Fix For: 1.3

 Attachments: Product_Version_For_JIRA.wsdl


 Hi,
 I have SOAP XML being returned from a service using Axis2, however it is 
 resorting to the following exception:
 com.ctc.wstx.exc.WstxParsingException: Expected a text token, got 
 START_ELEMENT.
 This Exception is thrown in my generated stub class derived from a WSDL.  The 
 line that it is failing on is when it attempts to execute a getElementText() 
 method on an XMLStreamReader based object.  I performed various checks and I 
 can confirm that the state of the XML reader is START_ELEMENT.  According to 
 Stax documentation, this is a valid state for the getElementText() method to 
 be called.
 A sample of the response XML I am attempting to parse is as follows:
 ?xml version='1.0' encoding='utf-8'?
 soapenv:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; 
   xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
   xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
   soapenv:Body
   ns1:response 
 xmlns:ns1=http://tempuri.org/Product_Version_V002/definitions;
   ns1:response
   FundVersionResponse
   
 TransactionStatusSuccess/TransactionStatus
   Platform
   IndicatorM/Indicator
   Version
   VersionNo4/VersionNo
   /Version
   /Platform
   Platform
   IndicatorU/Indicator
   Version
   VersionNo7/VersionNo
   /Version
   Version
   VersionNo8/VersionNo
   /Version
   Version
   VersionNo9/VersionNo
   /Version
   Version
   
 VersionNo10/VersionNo
   /Version
   Version
   
 VersionNo11/VersionNo
   /Version
   /Platform
   /FundVersionResponse
   /ns1:response
   /ns1:response
   /soapenv:Body
 /soapenv:Envelope
 Can anyone please help or comment on this?  This is preventing me from using 
 Axis2 altogether during my proof of concept.
 Thanks,
 Stuart

-- 
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-2695) Content-Type not defined in admin console (axis2-admin, listService)


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

Jaliya Ekanayake reassigned AXIS2-2695:
---

Assignee: Jaliya Ekanayake  (was: Deepal Jayasinghe)

 Content-Type not defined in admin console (axis2-admin, listService)
 

 Key: AXIS2-2695
 URL: https://issues.apache.org/jira/browse/AXIS2-2695
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: admin console
Affects Versions: 1.1.1
 Environment: solaris 10 intel, jdk 1.5.0_04, tomcat 5.5.23, 
 mod_jk1.2.21, apache 1.3
Reporter: Hubert Grégoire
Assignee: Jaliya Ekanayake
Priority: Minor

 When browsing with Firefox thru mod_jk, the admin console is displayed as 
 plain text . Internet Explorer runs well

-- 
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-2413) Invalid wsdl is generated by java2wsdl when rpc binding style is specified


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

Deepal Jayasinghe commented on AXIS2-2413:
--

I do not think that we need to fix this for 1.3. 

 Invalid wsdl is generated by java2wsdl when rpc binding style is specified
 --

 Key: AXIS2-2413
 URL: https://issues.apache.org/jira/browse/AXIS2-2413
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.2
 Environment: winxp, jdk15,Axis2-1.2-RC1
Reporter: Charitha Kankanamge
Assignee: Deepal Jayasinghe
Priority: Critical
 Attachments: Mathsclass-rpc.wsdl


 See the attached wsdl, which was generated by java2wsdl when rpc binding 
 style is specified. It includes the following element.
 wsdl:message name=addnumbersMessage
 wsdl:part name=part1 element=ns:addnumbers/
 /wsdl:message
 This should include type element instead of 'element' since rpc binding style 
 is specified when generating the wsdl.
 Steps to reproduce:
 
 Generate the wsdl by issuing the following command.
 java2wsdl -cn Mathsclass -o C:\Axis2\axis2-1.2-RC1\bin\out -cp . -sn 
 MyAxisservice -st rpc

-- 
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-2409) SOAP 1.2 contentType problem for Response


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

Deepal Jayasinghe updated AXIS2-2409:
-

Priority: Blocker  (was: Major)

  SOAP 1.2 contentType problem for Response
 --

 Key: AXIS2-2409
 URL: https://issues.apache.org/jira/browse/AXIS2-2409
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.2
Reporter: Gee Chia
Assignee: Thilina Gunarathne
Priority: Blocker

 Following was captured in TCPMon for a response message for SOAP 1.2. The 
 problem is the ;; before the charset= attribute in the  Content-Type, it 
 actually caused parsing problem. 
 HTTP/1.1 200 OK
 Server: Apache-Coyote/1.1
 Content-Type: 
 application/soap+xml;action=http://services.example.org/startResponse;;charset=UTF-8
 Transfer-Encoding: chunked
 Observation:
 As I traced the code, I observed  
 org.apache.axis2.transport.http.SOAPMessageFormatter:: getContentType() 
 returns a correct contentType, 
 (like 
 application/soap+xml;charset=UTF-8;action=http://services.example.org/startResponse;;),
  Then in SOAPMessageFormatter::writeTo method, once it called  
 OMElement.serializeAndConsume(out, format), the TCPMon displays shows the 
 content type with ;;. 

-- 
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-2765) Message Receiver not found for AxisOperation


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

Srinath Perera updated AXIS2-2765:
--

Priority: Blocker  (was: Major)

 Message Receiver not found for AxisOperation
 

 Key: AXIS2-2765
 URL: https://issues.apache.org/jira/browse/AXIS2-2765
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.2
 Environment: RAD 6.0, Axis 2 Version 1.2
Reporter: Satish Ghanekar
Assignee: Deepal Jayasinghe
Priority: Blocker

 I am trying to migrate my code from Axis 1.1.1 to Axis 1.2. So I wanted to 
 perform some testing. I downloaded Axis1.2 WAR file and and also the eclpise 
 plugins and installed them in RAD. I wrote the following POJO java class.
 /*
  * Created on Jun 4, 2007
  *
  * TODO To change the template for this generated file go to
  * Window - Preferences - Java - Code Style - Code Templates
  */
 package com.nationwide.marketlink.ws;
 /**
  * @author GHANEKS1
  *
  * TODO To change the template for this generated type comment go to
  * Window - Preferences - Java - Code Style - Code Templates
  */
 public class TestHandler {
 /**
  * @param param
  * @return
  */
 public String method1(String param) {
 String ret = Method 1 invoked with -  + param;
 System.out.println(Param =  + param);
 return ret;
 }
 /**
  * @param param
  * @return
  */
 public String method2(String param) {
 String ret = Method 2 invoked with -  + param;
 System.out.println(Param =  + param);
 return ret;
 }
 }
 Using the plugin Axis2 generated the following WSDL file
 wsdl:definitions xmlns:agm=http://ws.marketlink.nationwide.com;
   xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/;
   xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
   xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/;
   xmlns:xsd=http://ws.marketlink.nationwide.com/xsd;
   xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
   xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
   targetNamespace=http://ws.marketlink.nationwide.com;
   wsdl:types
   xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
   attributeFormDefault=qualified 
 elementFormDefault=qualified
   
 targetNamespace=http://ws.marketlink.nationwide.com/xsd;
   xs:element name=method1
   xs:complexType
   xs:sequence
   xs:element name=param 
 nillable=true
   type=xs:string /
   /xs:sequence
   /xs:complexType
   /xs:element
   xs:element name=method1Response
   xs:complexType
   xs:sequence
   xs:element name=return 
 nillable=true
   type=xs:string /
   /xs:sequence
   /xs:complexType
   /xs:element
   xs:element name=method2
   xs:complexType
   xs:sequence
   xs:element name=param 
 nillable=true
   type=xs:string /
   /xs:sequence
   /xs:complexType
   /xs:element
   xs:element name=method2Response
   xs:complexType
   xs:sequence
   xs:element name=return 
 nillable=true
   type=xs:string /
   /xs:sequence
   /xs:complexType
   /xs:element
   /xs:schema
   /wsdl:types
   wsdl:message name=method1Message
   wsdl:part name=part1 element=xsd:method1 /
   /wsdl:message
   wsdl:message name=method1ResponseMessage
   wsdl:part name=part1 element=xsd:method1Response /
   /wsdl:message
   wsdl:message name=method2Message
   wsdl:part name=part1 element=xsd:method2 /
   /wsdl:message
   wsdl:message name=method2ResponseMessage
   wsdl:part name=part1 element=xsd:method2Response /
   /wsdl:message
   wsdl:portType name=TestHandlerPortType
   wsdl:operation name=method1
   wsdl:input

[jira] Updated: (AXIS2-2404) Switch to turn off ServiceGroupID processing in Axis2


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

Deepal Jayasinghe updated AXIS2-2404:
-

Affects Version/s: 1.3
Fix Version/s: 1.3

If you are going to fix this , then let's fix this for 1.3

 Switch to turn off ServiceGroupID processing in Axis2
 -

 Key: AXIS2-2404
 URL: https://issues.apache.org/jira/browse/AXIS2-2404
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: kernel
Affects Versions: 1.3
Reporter: Chathura Ekanayake
Assignee: Deepal Jayasinghe
 Fix For: 1.3


 When working in SOAP sessions, Axis2 always tries to find service group if 
 axis2:ServiceGroupID header is set in the incoming SOAP message. This 
 behavior is not always desirable when Axis2 is acting as a SOAP intermediary, 
 where the actual service group may not have deployed in the intermediary 
 engine (e.g. Synapse). Such scenario would fail the intermediary Axis2 engine 
 when it tries to find the service group. Therefore, it is neccessary to have 
 a switch to diable service group ID processing in Axis2, which can be easily 
 configured using 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] Commented: (AXIS2-2596) Clean up cached attachment files


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

Glen Daniels commented on AXIS2-2596:
-

Let's either get this moving or close it... ?

 Clean up cached attachment files
 

 Key: AXIS2-2596
 URL: https://issues.apache.org/jira/browse/AXIS2-2596
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: transports
 Environment: Win XP
Reporter: Samuel Isokpunwu
Assignee: Thilina Gunarathne

 Added some code to clean up cached attachement files after use.

-- 
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-2395) AxisMessage.getSchema() returns null when schema element is found in an imported schema


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

Deepal Jayasinghe updated AXIS2-2395:
-

Fix Version/s: 1.3
 Priority: Blocker  (was: Minor)
Affects Version/s: (was: 1.1.1)
   (was: 1.2)
   1.3

 AxisMessage.getSchema() returns null when schema element is found in an 
 imported schema
 ---

 Key: AXIS2-2395
 URL: https://issues.apache.org/jira/browse/AXIS2-2395
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.3
 Environment: All
Reporter: Jeff Faath
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3


 When calling getSchema() on an AxisMessage, 'null' is returned when the 
 schema element is found in an imported schema.  This is because the code does 
 not check imported schema.  I've devised a solution below which recursively 
 traverses any imported schema.  The original getSchema() method can be 
 replaced by the two methods below:
 public XmlSchemaElement getSchemaElement() {
   AxisService service = (AxisService) getParent().getParent();
 ArrayList schemas = service.getSchema();
 for (int i = 0; i  schemas.size(); i++) {
   XmlSchema schema = (XmlSchema) schemas.get(i);
   return getSchemaElement(schema);
 }
 return null;
 }
 private XmlSchemaElement getSchemaElement(XmlSchema schema) {
   XmlSchemaElement returnElement = null;
   if (schema != null) {
 if (schema.getItems() != null) {
   Iterator schemaItems = schema.getItems().getIterator();
   while (schemaItems.hasNext()) {
 Object item = schemaItems.next();
 if (item instanceof XmlSchemaElement) {
   XmlSchemaElement xmlSchemaElement = (XmlSchemaElement) item;
   if (xmlSchemaElement.getQName().equals(this.elementQname)) {
 returnElement = xmlSchemaElement;
   }
 }
else if (item instanceof org.apache.ws.commons.schema.XmlSchemaImport) 
 {
  returnElement = 
 getSchemaElement(((org.apache.ws.commons.schema.XmlSchemaImport)item).getSchema());
}
else if (item instanceof 
 org.apache.ws.commons.schema.XmlSchemaInclude) {
  returnElement = 
 getSchemaElement(((org.apache.ws.commons.schema.XmlSchemaInclude)item).getSchema());
}
// We've found a matching element, no need to continue...
if (returnElement != null)
  break;
}
  }
}
return returnElement;
  }

-- 
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-2391) http binding and port are not added to the wsdl file generated using code generator wizard of eclipse plugin


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

Deepal Jayasinghe updated AXIS2-2391:
-

 Priority: Blocker  (was: Major)
Affects Version/s: (was: nightly)
   1.3
Fix Version/s: 1.3

Let's try to fix this for 1.3

 http binding and port are not added to the wsdl file generated using code 
 generator wizard of eclipse plugin
 

 Key: AXIS2-2391
 URL: https://issues.apache.org/jira/browse/AXIS2-2391
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Tools
Affects Versions: 1.3
 Environment: winxp, jdk15
Reporter: Charitha Kankanamge
Assignee: Lahiru Sandakith
Priority: Blocker
 Fix For: 1.3


 http binding and http port elements are not added to the wsdl file which is 
 generated by code generation wizard in Eclipse plugin. 
 Steps to reproduce:
 
 1. Start Axis2 code generation wizard
 2. Select a wsdl from a java source file option and continue
 3. Check the wsdl generated by plugin

-- 
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-2389) Dispatching based on the SOAP message body does not work for document/literal style


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

Deepal Jayasinghe updated AXIS2-2389:
-

Priority: Blocker  (was: Minor)

 Dispatching based on the SOAP message body does not work for document/literal 
 style
 ---

 Key: AXIS2-2389
 URL: https://issues.apache.org/jira/browse/AXIS2-2389
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.1.1
 Environment: Axis2, version 1.1.1
 Tomcat 5.0
 JDK1.6.0
Reporter: Jonas Boëthius
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker

 I am using a document/literal service and found that the dispatching based on 
 the message body does not seem to work. Any SOAPAction header except the one 
 defined in the WSDL causes the following fault:
  org.apache.axis2.AxisFault: Operation Not found EPR is...
 I've used ADB data binding and generated server side classes and services.xml 
 using the WSDL2Java utility.
 When debugging, I can see that the SOAPMessageBodyBasedDispatcher
  is invoked for the dispatching, that it finds the correct request element 
 name but when passing the call to the getOperation method in the AxisService 
 class, the operationsAliasesMap does not contain the name of the request 
 element. It seems like the initialization of the operationsAliasesMap does 
 not consider the case needed for the SOAPMessageBodyBasedDispatcher.
 Found an easy work-around of manually adding the name of the request root 
 element as actionMapping in the generated services.xml file. 

-- 
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-2756) problem to display the WSDL in a browser in Axis2.1.2

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

Srinath Perera updated AXIS2-2756:
--

Priority: Blocker (was: Major)

problem to display the WSDL in a browser in Axis2.1.2
-

Key: AXIS2-2756
URL: https://issues.apache.org/jira/browse/AXIS2-2756
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: deployment
Affects Versions: 1.2
Reporter: Stephane Roy
Assignee: Davanum Srinivas
Priority: Blocker
Attachments: stockquote.wsdl, stockquoteservice.wsdl,
stockquoteservice2.wsdl

I noticed a problem with the latest release of Axis2 (2.1.2).
Once the code is generated, compiled and deployed for the server part, I try
to display the related WSDL in my browser, by clicking on the line of my
service in the http://localhost:8080/axis2/services/listServices page.
The page http://localhost:8080/axis2/services/myService?wsdl opens with an
error:
org.apache.axis2.AxisFault: WSDLException: faultCode=OTHER_ERROR: Can't find
prefix for 'http://www.xxx.com/yyy/myService'. Namespace prefixes must be set
on the Definition object using the addNamespace(...) method.
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:850)

org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:221)
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:225)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
In Axis2.1.1.1, with the same WSDL, it worked fine.
In Axis2.1.2, I tried to generate the code in adb mode, then in xmlbeans mode
but I have the same problem.
After analysis, I found a scenario to reproduce the problem.
Our web service is defined with a WSDL divided in three parts. First we have
a concrete WSDL (defining the Service and the Binding). This WSDL imports an
abstract WSDL (defining the PortType and the Messages). Finally the abstract
WSDL imports a XSD Schema (defining the Types).
I found out that the WSDL cannot be displayed in my browser because there is
a conflict between two prefixes:
In the concrete WSDL, we defined the prefix 'tns' for our namespace. The
prefix 'tns' is also used in the abstract WSDL for another namespace.
With Axis2.1.2, this situation prevents the WSDL to be displayed in the
browser, whereas with Axis2.1.1.1, everything works fine.
I change one of the occurrences of the prefix 'tns' to 'tns2' and then
Axis2.1.2 can display the WSDL in the browser, just fine.
It seems that this is a regression of Axis2.1.2.
Thanks in advance.
PS: This problem has been submitted to the User mailing list:
http://marc.info/?l=axis-userm=117915706112761w=2

--
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-2383) [RPCMessageReceiver] Exception occurred while trying to invoke service method


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

Deepal Jayasinghe updated AXIS2-2383:
-

Priority: Blocker  (was: Critical)

 [RPCMessageReceiver] Exception occurred while trying to invoke service method
 -

 Key: AXIS2-2383
 URL: https://issues.apache.org/jira/browse/AXIS2-2383
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.1.1
 Environment: WinXP Pro SP2, Axis2-1.1.1 on Tomcat-5.5.x (WinXP Pro 
 SP2), Java-1.5.x, C# client for invoking the service.
Reporter: Eric Chow
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: KaraSysService.java, KaraSysService.wsdl, 
 KaraSysService.xml, Role.java, RoleDAO.java, services.xml, User.java, 
 UserDAO.java


 When invoking a AXIS2 web service from C# client, it just raised an exception 
 that I don't know what caused it. 
 18:25:13,125 ERROR [RPCMessageReceiver] Exception occurred while trying to 
 invoke service method getAllUsersArray
 org.apache.axiom.om.OMException: java.lang.NullPointerException
 at 
 org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:194)


-- 
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-2693) Client code generation not possible


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

Jaliya Ekanayake reassigned AXIS2-2693:
---

Assignee: Jaliya Ekanayake  (was: Amila Chinthaka Suriarachchi)

 Client code generation not possible
 ---

 Key: AXIS2-2693
 URL: https://issues.apache.org/jira/browse/AXIS2-2693
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: client-api, codegen
Affects Versions: 1.1.1
 Environment: WebLogic 8.1 sp5,  jdk1.4
Reporter: ankur sarkar
Assignee: Jaliya Ekanayake
 Attachments: build.xml, ManageCustomerOrder.wsdl, 
 ManageCustomerOrder.xsd, StandardHeader.xsd


 Hi,
 I am migrating from axis 1.4 to axis2 in my current project. Currently we are 
 using axis2 version 1.1.1. While trying to generate client classes through 
 ant script I am getting the following error:
  org.apache.axis2.wsdl.codegen.CodeGenerationException: 
 java.lang.RuntimeException: java.lang.reflect.InvocationTargetException.
 But this was working fine with axis 1.4. I have tried both adb and 
 xmlbeans databinding feature, but none of them seems to work
 Can you please help me out.
 Please find below the build script, the WSDL and the xsd files.
 build.xml
 -
 project name=build default=makejars basedir=.
  property name=lib.dir value=../lib /
property name=build.classes.dir value=../classes/
  property name=wsdl.dir value=../etc/wsdl/
  property name=wsdl.filename value=ManageCustomerOrder.wsdl/
  property name=src.generated.dir value=../src/
property name=app.lib.dir location=../../../APP-INF/lib/
  property name=axis.lib.dir location=../../../axis2/WEB-INF/lib/
property name=project.name value=ManageCustomerOrder/
target name=init
   mkdir dir=${src.generated.dir}/
   mkdir dir=${build.classes.dir}/
   mkdir dir=${lib.dir}/
/target

target name=clean
   delete dir=${lib.dir}/
   delete dir=${build.classes.dir}/
   delete dir=${src.generated.dir}/
/target
   
path id=axis.classpath
   fileset dir=${axis.lib.dir}
   include name=**/*.jar /
   /fileset
   /path
  target name=declare 
 taskdef name=codegen
  classname=org.apache.axis2.tool.ant.AntCodegenTask
  classpathref=axis.classpath/
 /target
 target name=import-wsdl depends=clean,init,declare
 codegen 
  wsdlfilename=${wsdl.dir}/${wsdl.filename}
  databindingname=adb
  output=${src.generated.dir}
  classpathref=axis.classpath/
 /target
  
  
target name=compile depends=import-wsdl
  javac srcdir=${src.generated.dir} destdir=${build.classes.dir} 
 classpathref=axis.classpath
debuglevel=lines,vars,source debug=true 
 includeAntRuntime=false/
/target
   target name=makejars depends=compile 
   
   jar destfile=${lib.dir}/${project.name}.jar
   fileset dir=${build.classes.dir}/
   /jar
   delete dir=${build.classes.dir}/
   
   /target
 /project
 ManageCustomerOrder.wsdl
 -
 ?xml version=1.0 encoding=UTF-8?
 wsdl:definitions 
 xmlns:MCO=http://itprogrammes.intra.bt.com/pdb/capabilities/ManageCustomerOrder/2006/12/;
  xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 
 xmlns:tns=http://capabilities.nat.bt.com/wsdl/ManageCustomerOrder; 
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; name=MCO 
 targetNamespace=http://capabilities.nat.bt.com/wsdl/ManageCustomerOrder;
   wsdl:types
   schema xmlns=http://www.w3.org/2001/XMLSchema; 
 xmlns:mrm=http://capabilities.nat.bt.com/wsdl/ManageCustomerOrder; 
 targetNamespace=http://capabilities.nat.bt.com/wsdl/ManageCustomerOrder;
   import 
 namespace=http://itprogrammes.intra.bt.com/pdb/capabilities/ManageCustomerOrder/2006/12/;
  schemaLocation=ManageCustomerOrder.xsd/
   /schema
   /wsdl:types
   wsdl:message name=queryOrderRequest
   wsdl:part name=queryOrderRequest 
 element=MCO:queryOrderRequest/
   /wsdl:message
   wsdl:message name=queryOrderResponse
   wsdl:part name=queryOrderResponse 
 element=MCO:queryOrderResponse/
   /wsdl:message
   wsdl:message name=requestOrderRequest
   wsdl:part name=requestOrderRequest 
 element=MCO:requestOrder/
   /wsdl:message
   wsdl:message name=requestOrderResponse
   wsdl:part name=requestOrderResponse 
 element=MCO:requestOrder/
   /wsdl:message
   wsdl:portType name=ManageCustomerOrderPortType
   wsdl:operation name=queryOrder
   wsdl:input

[jira] Updated: (AXIS2-2365) Better exception type if failed length check


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

Deepal Jayasinghe updated AXIS2-2365:
-

Priority: Blocker  (was: Major)

 Better exception type if failed length check
 

 Key: AXIS2-2365
 URL: https://issues.apache.org/jira/browse/AXIS2-2365
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: adb
Affects Versions: nightly
Reporter: Full Name
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker

 If a ADB setter is called with an invalid lenght string, a RuntimeExcpetion 
 without any further information is being thrown. A specialized excpetion 
 would be usefull.
 if (  (10  java.lang.String.valueOf(param).length()) 
 (java.lang.String.valueOf(param).length() = 80)  ) {
  this.value=param;
  }
  else {
  throw new
 java.lang.RuntimeException(); 

-- 
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-2358) Code level Comments


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

Deepal Jayasinghe updated AXIS2-2358:
-

Affects Version/s: (was: 1.2)
   1.3
Fix Version/s: (was: nightly)
   1.3

Need to apply the patch.

 Code level Comments
 ---

 Key: AXIS2-2358
 URL: https://issues.apache.org/jira/browse/AXIS2-2358
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: documentation
Affects Versions: 1.3
 Environment: Linux
Reporter: Karthiga Rajeevani Ratnam
Assignee: Thilina Gunarathne
 Fix For: 1.3

 Attachments: patch


 Improvements made to inline code level comments on 
 AddressingBasedDispatcher.java

-- 
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-2357) SOAP Attachment not working


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

Deepal Jayasinghe updated AXIS2-2357:
-

Priority: Blocker  (was: Major)

 SOAP Attachment not working
 ---

 Key: AXIS2-2357
 URL: https://issues.apache.org/jira/browse/AXIS2-2357
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel, modules
Affects Versions: 1.1.1
 Environment: axis2-1.1.1, JDK1.5.0_05, tomcat-5.5.20
Reporter: Sigirisetty Surya Kiran
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: AXIS2-2357.zip


 Hi Folks,
 I am trying to create a service which servers files. Client is successfully 
 making call to service and infact
 service is executed successfully. But i am getting exception on server some 
 where after service execution. 
 Pls let me know what's the possible cause.
 Env: Running Axis2-1.1.1 on tomcat.
 Mar 9, 2007 10:00:04 AM 
 org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver 
 invokeBusinessLogic
 SEVERE: Exception occurred while trying to invoke service method 
 getTermSheetFile
 java.lang.NullPointerException
   at 
 org.apache.axis2.databinding.utils.BeanUtil.getPullParser(BeanUtil.java:197)
   at 
 org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:90)
   at 
 org.apache.axis2.rpc.receivers.RPCUtil.processResponse(RPCUtil.java:192)
   at 
 org.apache.axis2.rpc.receivers.RPCInOutAsyncMessageReceiver.invokeBusinessLogic(RPCInOutAsyncMessageReceiver.java:121)
   at 
 org.apache.axis2.receivers.AbstractInOutAsyncMessageReceiver$2.run(AbstractInOutAsyncMessageReceiver.java:61)
   at 
 edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
   at 
 edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
   at java.lang.Thread.run(Unknown Source)
 Exception in thread Axis2 Task java.lang.NullPointerException
   at 
 org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:746)
   at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:433)
   at 
 org.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:304)
   at 
 org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:991)
   at org.apache.coyote.Response.action(Response.java:182)
   at 
 org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:322)
   at 
 org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:293)
   at 
 org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:97)
   at java.io.BufferedOutputStream.flush(Unknown Source)
   at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
   at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:184)
   at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:311)
   at 
 org.apache.axiom.om.impl.MTOMXMLStreamWriter.flush(MTOMXMLStreamWriter.java:115)
   at 
 org.apache.axiom.om.impl.llom.OMNodeImpl.serializeAndConsume(OMNodeImpl.java:420)
   at 
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.sendUsingOutputStream(CommonsHTTPTransportSender.java:276)
   at 
 org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:208)
   at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:714)
   at 
 org.apache.axis2.receivers.AbstractInOutAsyncMessageReceiver$1.handleFault(AbstractInOutAsyncMessageReceiver.java:51)
   at 
 org.apache.axis2.receivers.AbstractInOutAsyncMessageReceiver$2.run(AbstractInOutAsyncMessageReceiver.java:68)
   at 
 edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
   at 
 edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
   at java.lang.Thread.run(Unknown Source)
  
 cheers,
 sigirisetti
   
 
 
 Mar 9, 2007 9:57:31 AM org.apache.catalina.core.AprLifecycleListener 
 lifecycleEvent
 INFO: The Apache Tomcat Native library which allows optimal performance in 
 production environments was not found on the java.library.path: C:\Program 
 Files\Java\jre1.5.0_05\bin;.;C:\WINNT\system32;C:\WINNT;C:\Program 
 Files\WRQ\Reflection;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program
  Files\Real\Realplayer;C:\WINNT\System32\Wbem;C:\Program 
 Files\sql11\DLL;C:\Program Files\sql11\BIN;C:\Program 
 Files\jetform\5.2\;C:\Program Files\Oracle\ora92\bin;C:\Program 
 Files\SimonTatham\Putty\;C:\Program 
 Files\Sybase\shared\powerbuilder;C:\Program

[jira] Updated: (AXIS2-2690) Fixes to samples on quickstartguide.html page


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

Jaliya Ekanayake updated AXIS2-2690:


Fix Version/s: 1.3

 Fixes to samples on quickstartguide.html page
 -

 Key: AXIS2-2690
 URL: https://issues.apache.org/jira/browse/AXIS2-2690
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Glen Mazza
Assignee: Chatra Nakkawita
Priority: Minor
 Fix For: 1.3

 Attachments: quickstartguidepatch.txt, quickstartsamplespatch.txt


 Some fixes/enhancements added to quick start samples:
 1.)  The build scripts were missing a create client directory in the init 
 task, causing the create client targets to fail (they are dependent on an 
 already created subdirectory of that name.)
 2.)  I modified the clients to each use different stock symbols, so the 
 values returned from running them will not conflict with/override each other. 
  (Expected return values weren't working correctly because of previous runs 
 with different clients.)
 3.)  Some information in the quickstartguide.html was incorrect.
 Patch for quickstartguide.html is against 1.2 branch, patch for code samples 
 is against the trunk.

-- 
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-2356) does useOriginalwsdl do any special handling


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

Deepal Jayasinghe updated AXIS2-2356:
-

Priority: Blocker  (was: Major)

 does useOriginalwsdl do any special handling
 

 Key: AXIS2-2356
 URL: https://issues.apache.org/jira/browse/AXIS2-2356
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.1.1
 Environment: axis2-1.1.1, JDK1.5.0_05, tomcat-5.5.20
Reporter: Sigirisetty Surya Kiran
Assignee: Deepal Jayasinghe
Priority: Blocker
 Attachments: AXIS2-2356.zip


 Hi folks,
  I deployed a Web service in axis2 (R 1.1.1) by configuring  
 useOriginalwsdl=true as parameter in services.xml
 WSDL file being used is generated by axis2 it self. But service fails 
 complaining with below error.
 If i unset to useOriginalwsdl=false, then Web Service works.
  Client Side Stack trace:
  Sending request..
  hr:getEmployee 
 xmlns:hr=http://types.wsdl.custom.ws.ssk.com/xsd;hr:in1/hr:in/hr:getEmployeeorg.apache.axis2.AxisFault:
  Exception occurred while trying to invoke service method getEmployee
  at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:271)
  at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
  at 
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:579)
  at 
 org.apache.axis2.client.ServiceClient.sendReceive(ServiceClient.java:508)
  at 
 com.ssk.ws.custom.wsdl.types.HRServiceClient2.main(HRServiceClient2.java:43)
  Caused by: java.lang.Exception: org.apache.axis2.AxisFault: Exception 
 occurred while trying to invoke service method getEmployee; nested exception 
 is:
  java.lang.IllegalArgumentException: wrong number of arguments
  at 
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:159)
  at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
  at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
  at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328)
  at 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
  at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
  at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
  at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
  at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
  at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
  at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
  at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
  at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
  at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
  at 
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
  at 
 org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
  at 
 org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
  at 
 org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
  at 
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
  at java.lang.Thread.run(Unknown Source)
  Caused by: java.lang.IllegalArgumentException: wrong number of arguments
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  at java.lang.reflect.Method.invoke(Unknown Source)
  at 
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:95)
  ... 20 more
  at org.apache.axis2.AxisFault.init(AxisFault.java:159)
  ... 5 more
  Server Side Stack trace:
  Mar 20, 2007 4:02:05 PM org.apache.catalina.core.AprLifecycleListener 
 lifecycleEvent
  INFO: The Apache Tomcat Native library which allows optimal performance in 
 production environments was not found on the java.library.path: C:\Program 
 Files\Java\jre1.5.0_05\bin;.;C:\WINNT\system32;C:\WINNT;C:\Program

[jira] Updated: (AXIS2-2352) XMLBeans client getting org.apache.axis2.AxisFault: First Element must contain the local name, Envelope


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

Deepal Jayasinghe updated AXIS2-2352:
-

Priority: Blocker  (was: Major)

 XMLBeans client getting org.apache.axis2.AxisFault: First Element must 
 contain the local name, Envelope
 ---

 Key: AXIS2-2352
 URL: https://issues.apache.org/jira/browse/AXIS2-2352
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: client-api, codegen, wsdl
Affects Versions: 1.1.1
 Environment: Windows XP, JDK 1.4.2_09
Reporter: Raghu
Assignee: Davanum Srinivas
Priority: Blocker

  This does not seem to be related to the REST problem mentioned in some of 
 the other issues. since on the server side (a non-Axis server) I see the 
 following:
  POST / HTTP/1.1
 SOAPAction: bookstore.echoMe
 User-Agent: Axis2
 Host: localhost:
 Transfer-Encoding: chunked
 Content-Type: text/xml; charset=UTF-8
 [Fatal Error] :-1:-1: Premature end of file.
 This is the process I followed:
 I installed the said version of Axis2 today.
 I have my own wsdl (produced below).
 I set up JAVA_HOME, AXIS2_HOME.
 Then I ran:
 c:\axis2-1.1.1\bin\wsdl2java.bat -f -d xmlbeans -uri c:\wsdl\bookstore.wsdl
 which produced dirs/files under my current directory.
 Then I wrote a client class to invoke the operation (produced below).
 When I run it I get this exception on the client side I get the following 
 exception.
 org.apache.axis2.AxisFault: First Element must contain the local name, 
 Envelope; nested exception is: 
   org.apache.axiom.soap.SOAPProcessingException: First Element must 
 contain the local name, Envelope
   at 
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:126)
   at 
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:252)
   at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
   at bookstore.BookstoreStub.echoMe(BookstoreStub.java:141)
   at client_pkg.MyAxisClient.thisEchoMe(MyAxisClient.java:43)
   at client_pkg.MyAxisClient.main(MyAxisClient.java:22)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:324)
   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)
 Caused by: org.apache.axiom.soap.SOAPProcessingException: First Element must 
 contain the local name, Envelope
   at 
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.constructNode(StAXSOAPModelBuilder.java:217)
   at 
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.createOMElement(StAXSOAPModelBuilder.java:175)
   at 
 org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:120)
   at 
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:159)
   at 
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.identifySOAPVersion(StAXSOAPModelBuilder.java:133)
   at 
 org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.init(StAXSOAPModelBuilder.java:108)
   at 
 org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:120)
   ... 11 more
 Here is the wsdl file:
 definitions name=bookstoredefinitions targetNamespace=bookstore 
 xmlns:tns=bookstore xmlns=http://schemas.xmlsoap.org/wsdl/; 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
   types
 xsd:schema targetNamespace=bookstore  elementFormDefault=qualified 
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:tns=bookstore
   xsd:element name=echoMe
 xsd:complexType
   xsd:sequence
 xsd:element name=AuthorName
   xsd:complexType
   xsd:attribute name=Value type=xsd:string/ 

   /xsd:complexType
 /xsd:element
 xsd:element name=BookName
   xsd:complexType
 xsd:attribute name=Value type=xsd:string/   
   /xsd:complexType
 /xsd:element
   /xsd:sequence
 /xsd:complexType
   /xsd:element
   xsd:element name=echoMeResponse
 xsd:complexType
   xsd:sequence
 xsd:element name=AuthorName
   xsd:complexType
 xsd:attribute name=Value type=xsd:string/   
 
   /xsd:complexType

[jira] Updated: (AXIS2-2583) ServiceContext.activate() never executes a path because of null value


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

Eran Chinthaka updated AXIS2-2583:
--

 Priority: Critical  (was: Major)
Fix Version/s: 1.3
 Assignee: Bill Nagy  (was: Deepal Jayasinghe)

Bill,

You seems to be the person who had written this code and/or applied the patch 
(thanks to svn blame command)

I think this seems to be a trivial fix. Can we please get this fixed for the 
next release?

Thanks,
Chinthaka

 ServiceContext.activate() never executes a path because of null value
 -

 Key: AXIS2-2583
 URL: https://issues.apache.org/jira/browse/AXIS2-2583
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Reporter: Michele Mazzucco
Assignee: Bill Nagy
Priority: Critical
 Fix For: 1.3


 In ServiceContext.activate() there's:
 ServiceGroupContext existingSGC = null;
 if (existingSGC == null) {
 // do A
 } else {
// do B
 }
 The else is never executed

-- 
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-2349) JiBX wrapped databinding sample in the documentation


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

Deepal Jayasinghe updated AXIS2-2349:
-

Affects Version/s: (was: 1.1.1)
   1.3
Fix Version/s: 1.3

Hi Dennis,
What do you think abt this , do we need to fix this for 1.3  ?

Thanks
Deepal

 JiBX wrapped databinding sample in the documentation
 

 Key: AXIS2-2349
 URL: https://issues.apache.org/jira/browse/AXIS2-2349
 Project: Axis 2.0 (Axis2)
  Issue Type: Task
  Components: documentation
Affects Versions: 1.3
Reporter: Jorge Fernández
Assignee: Dennis Sosnoski
 Fix For: 1.3


 I think, currently there's only a sample for the unwrapped case and as I'm 
 having problems with generating code from Java classes. 
 In my case I'm trying to generate the wsdl from classes and then build new 
 JiBX code from that.
 As I don't find any good sample for wrapped mode, I think it could be cool to 
 have one in axis2 documentation.

-- 
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-2742) axis.sh is missing quotes on variables? causes ./axis2.sh: line 38: [: !=: unary operator expected


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

Srinath Perera updated AXIS2-2742:
--

Priority: Blocker  (was: Trivial)

To make sure we fix it for 1.3

 axis.sh is missing quotes on variables? causes ./axis2.sh: line 38: [: !=: 
 unary operator expected
 --

 Key: AXIS2-2742
 URL: https://issues.apache.org/jira/browse/AXIS2-2742
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
Affects Versions: 1.2
 Environment: linux
Reporter: Ted Leung
Assignee: Deepal Jayasinghe
Priority: Blocker

 When I run the .sh files in axis2, 1.2 I get a bash error as follows 
[1248:[EMAIL PROTECTED]:/data/svn/soap_client/axis2-1.2/bin]./wsdl2java.sh 
 Using AXIS2_HOME:   /data/svn/soap_client/axis2-1.2
 Using JAVA_HOME:   /data/apps/jdk1.6.0
./axis2.sh: line 38: [: !=: unary operator expected
 are the variables in the axis.sh file suppose to be in quotes? it seems to 
 make the error go away, i.e. 
 line 38 :   if [ $arg != -classpath ]  [ $arg != -cp ]  [ $prearg 
 != -classpath ]  [ $prearg != -cp  ]
 and 
 line  43 :   if [ $prearg = -classpath ] || [ $prearg = -cp  ]

-- 
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-2348) WSDL2JAVA always outputs xsd files using system's default encoding rather than UTF-8


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

Deepal Jayasinghe updated AXIS2-2348:
-

Priority: Blocker  (was: Major)

 WSDL2JAVA always outputs xsd files using system's default encoding rather 
 than UTF-8
 

 Key: AXIS2-2348
 URL: https://issues.apache.org/jira/browse/AXIS2-2348
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: wsdl
Affects Versions: 1.1.1
Reporter: Dmitry
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker

 WSDL2Java always outputs xsd files using system's default encoding rather 
 than UTF-8 (even if source xsds are in UTF-8).
 This seems to be  the same kind of problem as this 
 http://issues.apache.org/jira/browse/AXIS2-2318

-- 
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-2347) When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl) should reflect the annotations


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

Deepal Jayasinghe updated AXIS2-2347:
-

Affects Version/s: 1.3
Fix Version/s: 1.3

Let's try to fix this for 1.3. But I do not think this is a blocker.

 When deploying using JAXWSMessageReceiver, the dynamic wsdl (?wsdl) should 
 reflect the annotations
 --

 Key: AXIS2-2347
 URL: https://issues.apache.org/jira/browse/AXIS2-2347
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: jaxws
Affects Versions: 1.3
Reporter: Davanum Srinivas
Assignee: Nick Gallardo
 Fix For: 1.3


 Do we update the existing java2wsdl...how do we handle this situation?
 thanks,
 dims

-- 
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-2339) InOnly Receivers: wrong HTTP status with SOAP Fault


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

Deepal Jayasinghe updated AXIS2-2339:
-

Priority: Blocker  (was: Major)

 InOnly Receivers: wrong HTTP status with SOAP Fault
 ---

 Key: AXIS2-2339
 URL: https://issues.apache.org/jira/browse/AXIS2-2339
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.1.1
 Environment: Windows XP, Java 1.5.0_11, Tomcat 5.0.28
Reporter: Colin Markwell
Assignee: Deepal Jayasinghe
Priority: Blocker

 When an AxisFault is thrown from methods that use the InOnly receiver (i.e. 
 ones that don't return any data), a HTTP/1.1 202 Accepted response is 
 returned instead of HTTP/1.1 500 Internal Server Error.
 I believe that a 500 response is correct, according to:
 http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383529
 To demonstrate I've created some WSDL that has two methods - one that doesn't 
 return any data (in), and one that does (inout):
 --- Begin test.wsdl -
 ?xml version=1.0 encoding=UTF-8?
 wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
 xmlns:tns=http://www.example.org/test/;
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
 xmlns:xsd=http://www.w3.org/2001/XMLSchema; name=test
 targetNamespace=http://www.example.org/test/;
 wsdl:types
 xsd:schema targetNamespace=http://www.example.org/test/;
 xsd:element name=in type=xsd:string /
 xsd:element name=inout type=xsd:string /
 xsd:element name=inoutResponse type=xsd:string /
 /xsd:schema
 /wsdl:types
 wsdl:message name=inRequest
 wsdl:part name=parameters element=tns:in /
 /wsdl:message
 wsdl:message name=inoutRequest
 wsdl:part name=inoutRequest element=tns:inout /
 /wsdl:message
 wsdl:message name=inoutResponse
 wsdl:part name=parameters element=tns:inoutResponse /
 /wsdl:message
 wsdl:portType name=test
 wsdl:operation name=in
 wsdl:input message=tns:inRequest/wsdl:input
 /wsdl:operation
 wsdl:operation name=inout
 wsdl:input message=tns:inoutRequest/wsdl:input
 wsdl:output 
 message=tns:inoutResponse/wsdl:output
 /wsdl:operation
 /wsdl:portType
 wsdl:binding name=testSOAP type=tns:test
 soap:binding style=document
 transport=http://schemas.xmlsoap.org/soap/http; /
 wsdl:operation name=in
 soap:operation 
 soapAction=http://www.example.org/test/in; /
 wsdl:input
 soap:body use=literal /
 /wsdl:input
 /wsdl:operation
 wsdl:operation name=inout
 soap:operation 
 soapAction=http://www.example.org/test/inout; /
 wsdl:input
 soap:body use=literal /
 /wsdl:input
 wsdl:output
 soap:body use=literal /
 /wsdl:output
 /wsdl:operation
 /wsdl:binding
 wsdl:service name=test
 wsdl:port binding=tns:testSOAP name=testSOAP
 soap:address location=http://www.example.org/; /
 /wsdl:port
 /wsdl:service
 /wsdl:definitions
 --- End test.wsdl ---
 I then create the Java classes from the WSDL:
 wsdl2java -uri test.wsdl -ss -sd
 I then populate the skeleton class with code that throws AxisFaults:
 --- Begin src/org/example/www/test/TestSkeleton.java 
 package org.example.www.test;
 import org.apache.axis2.AxisFault;
 public class TestSkeleton{
 public InoutResponse inout(Inout param0) throws AxisFault {
 throw new AxisFault(Inout AxisFault);
 }
 public  void in(In param2) throws AxisFault {
 throw new AxisFault(In AxisFault);
 }
 }
 --- End src/org/example/www/test/TestSkeleton.java --
 I then build the aar file using ant and the wsdl2java-created build.xml and 
 deploy it to my application server.
 I then use Eclipse's Web Services Explorer to invoke the web service, 
 proxying the requests through Apache TCPMon so that I can view the headers.
 These are the responses I see (xml-reformatted by TCPMon):
 --- Begin response to inout SOAP message

[jira] Updated: (AXIS2-2687) Improvements to mail-configuration.html and migration.html


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

Jaliya Ekanayake updated AXIS2-2687:


Fix Version/s: 1.3

 Improvements to mail-configuration.html and migration.html
 --

 Key: AXIS2-2687
 URL: https://issues.apache.org/jira/browse/AXIS2-2687
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
Affects Versions: 1.2
Reporter: Glen Mazza
Assignee: Chatra Nakkawita
 Fix For: 1.3

 Attachments: mailmigrpatch.txt


 Patch for these two documents.

-- 
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-2022) setting HTTPConstants.SO_TIMEOUT option doesnt seems to work


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

Eran Chinthaka updated AXIS2-2022:
--

 Priority: Blocker  (was: Major)
Fix Version/s: 1.3

I think we should fix this too for the next release. 

 setting HTTPConstants.SO_TIMEOUT option doesnt seems to work
 

 Key: AXIS2-2022
 URL: https://issues.apache.org/jira/browse/AXIS2-2022
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.2
 Environment: jdk1.5 windows XP
Reporter: Arnaud Louet
Assignee: Deepal Jayasinghe
Priority: Blocker
 Fix For: 1.3


 on a genrated stub at construction time,  the following code doesn't seems to 
 change the default timeout:
 _serviceClient.getOptions().setProperty(HTTPConstants.SO_TIMEOUT,new 
 Integer(5*60*1000));
 the following call works though
 _serviceClient.getOptions().setTimeOutInMilliSeconds(5*60*1000);
 the documentation ( 
 http://ws.apache.org/axis2/1_1_1/http-transport.html#timeout_config ) implies 
 that both methods should work.

-- 
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-1994) Cannot Establish Session to Microsoft WSE 3.0 Server

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

Eran Chinthaka commented on AXIS2-1994:
---

Steve,

Any updates on this? Shall we mark this issue as resolved now?

Cannot Establish Session to Microsoft WSE 3.0 Server

Key: AXIS2-1994
URL: https://issues.apache.org/jira/browse/AXIS2-1994
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Affects Versions: 1.1.1
Reporter: Steve Haun
Assignee: Deepal Jayasinghe

Server is located in Windows 2003 and it is developed using Microsoft WSE
3.0. WSDL file is extracted from server side and Java Client code is
generated using the wsdl2java command. The setManageSession method (in
ServiceClient class) is used in client side to maintain session. But each
request in client side comes out as new session in server side. I checked the
session information in server side. New session ID is delivered for each
request and Session.IsNewSession property is always true. It looks like
session is not maintained between AXIS2 client and WSE 3.0 server.
We do not have this kind of session issue when we used AXIS 1.0 client with
WSE 2.0 server. The setMaintainSession method is used in AXIS 1.0 client. I
cannot figure out the proper way to main session between AXIS2 client and WSE
3.0 server.

--
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-2571) SOAPAction mismatch invoking service


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

Glen Daniels commented on AXIS2-2571:
-

Can we please see the WSDL you used to generate the stub and the code you're 
using to call it?

Thanks!


 SOAPAction mismatch invoking service
 

 Key: AXIS2-2571
 URL: https://issues.apache.org/jira/browse/AXIS2-2571
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: Addressing
 Environment: Ubuntu Linux 6.10, Sun JDK 1.4.2, Apache Tomcat 5.5.23
Reporter: Jose Antonio
Assignee: Brian DePradine

 I'm trying to invoke an Axis2 service inside a Muse service. To do
 this I'm using the Axis2 service stub I generated but when I send a
 message I get the following:
 POST /axis2/services/RegistrationService HTTP/1.1
 SOAPAction: 
 http://docs.oasis-open.org/wscaf/2005/10/wscf/RegistrationServicePortType/addParticipantResponse;
 User-Agent: Axis2
 Host: 127.0.0.1:8081
 Transfer-Encoding: chunked
 Content-Type: text/xml; charset=UTF-8
 545
 ?xml version='1.0' encoding='UTF-8'?
  soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing;
 xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/;
 soapenv:Header

 wsa:Tohttp://localhost:8081/axis2/services/RegistrationService/wsa:To
wsa:ReplyTo
   
 wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address
/wsa:ReplyTo

 wsa:MessageIDurn:uuid:63015A36B234BC96B8117708283322511/wsa:MessageID

 wsa:Actionhttp://docs.oasis-open.org/wscaf/2005/10/wscf/RegistrationServicePortType/addParticipant/wsa:Action
 /soapenv:Header
 
 As you can see, the SOAPAction and wsa Action elements are different
 and I don't know why. Using this same Stub in a local program I get
 the same text in both elements and the call succeed but using it in
 Muse gets this 'Response' part added.
 Is it a Muse or an Axis2 problem? Does Axis2 add a 'Response' element
 for every outgoing message in a service?

-- 
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-2685) wsdl2code lose XML declaration (?xml) in XSD


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

Jaliya Ekanayake updated AXIS2-2685:


Priority: Blocker  (was: Major)

 wsdl2code lose XML declaration (?xml) in XSD
 -

 Key: AXIS2-2685
 URL: https://issues.apache.org/jira/browse/AXIS2-2685
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.2
 Environment: Windows XP,
Reporter: Antoni Jakubiak
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker

 I use axis2-wsdl2code-maven-plugin. 
 My original XSD file begin with line:
 $ head -n 2 src/main/axis2/datamodel.xsd
 ?xml version=1.0 encoding=UTF-8?
 schema xmlns=http://www.w3.org/2001/XMLSchema;
 But generated XSD lose XML declaration:
 $ head -n 1 axis2/resources/xsd0.xsd
 schema xmlns:tns= [...]
 XSD files without XML declaration may not work correctly. 

-- 
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-2336) [Axis2-1.1.1] - Server- Error- mix webmethods name and its arguments


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

Deepal Jayasinghe resolved AXIS2-2336.
--

Resolution: Fixed

This was the issue due to we have used class varible in RPC MR (method) , now I 
have removed that. So now the issue shoud be fixed  , please re-run the test 
case and see whether you getting any error, if so please re-open the issue.

Thanks
Deepal

 [Axis2-1.1.1] - Server- Error- mix  webmethods name and its arguments
 -

 Key: AXIS2-2336
 URL: https://issues.apache.org/jira/browse/AXIS2-2336
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
 Environment: Linux  2.6.12
 jdk 1.5.0.11
 tomcat 5.5.20
 Axis2 1.1.1
Reporter: olivier DUGAST
Assignee: Davanum Srinivas
 Attachments: SOAPMonitor.jpg, source.zip


 Sometimes, when i call many webservices, at the same time(10 Threads on 
 client), i've errors ( less than 1% ) :
 On server, Axis2 mix
 - webmethods name
 - and its arguments
 As you can see below
 ---client ---
 ...
 org.apache.axis2.AxisFault: Exception occurred while trying to invoke service 
 method webMethod3
   at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:308)
   at com.me.client.ServiceTest2Stub.webMethod1(ServiceTest2Stub.java:369)
   at 
 com.me.client.ServiceTest2Client.webMethod1(ServiceTest2Client.java:37)
   at 
 com.me.client.ServiceTest2ClientMain.run(ServiceTest2ClientMain.java:30)
   at java.lang.Thread.run()V(Unknown Source)
 ...
 --
 - server --
 16 mars 2007 11:09:22 org.apache.axis2.rpc.receivers.RPCMessageReceiver 
 invokeBusinessLogic
 GRAVE: Exception occurred while trying to invoke service method webMethod3
 java.lang.NumberFormatException: For input string: param1
   at 
 java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
   at java.lang.Integer.parseInt(Integer.java:447)
   at java.lang.Integer.init(Integer.java:620)
   at 
 org.apache.axis2.databinding.typemapping.SimpleTypeMapper.getSimpleTypeObject(SimpleTypeMapper.java:61)
   at 
 org.apache.axis2.databinding.utils.BeanUtil.processObject(BeanUtil.java:552)
   at 
 org.apache.axis2.databinding.utils.BeanUtil.ProcessElement(BeanUtil.java:507)
   at 
 org.apache.axis2.databinding.utils.BeanUtil.deserialize(BeanUtil.java:446)
   at 
 org.apache.axis2.rpc.receivers.RPCUtil.processRequest(RPCUtil.java:109)
   at 
 org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusinessLogic(RPCMessageReceiver.java:116)
   at 
 org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
   at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
   at 
 org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328)
   at 
 org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
   at 
 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
   at 
 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
   at 
 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
   at 
 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
   at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
   at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
   at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
   at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
   at 
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
   at 
 org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
   at 
 org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
   at 
 org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
   at 
 org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
   at java.lang.Thread.run(Thread.java:619)
 16 mars 2007 11:09:22 org.apache.axis2.rpc.receivers.RPCMessageReceiver 
 invokeBusinessLogic
 GRAVE: Exception occurred while trying to invoke service method webMethod1
 java.lang.IllegalArgumentException
   at sun.reflect.GeneratedMethodAccessor42.invoke(Unknown Source)
   at

[jira] Updated: (AXIS2-2335) need to be able to change service policy on the fly...


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

Deepal Jayasinghe updated AXIS2-2335:
-

Priority: Blocker  (was: Major)

Sanka,
Its your call.

Thanks
Deepal

 need to be able to change service policy on the fly...
 --

 Key: AXIS2-2335
 URL: https://issues.apache.org/jira/browse/AXIS2-2335
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: kernel
Affects Versions: 1.1.1
 Environment: Windows XP, Tomcat 4.1, Axis2, using rampart 1.1
Reporter: Jackson Wynn
Assignee: Sanka Samaranayake
Priority: Blocker

 I  need to be able to dynamically change the security policy of a specified 
 axis service, where new security policies are constructed from static policy 
 components contained in the services.xml, combined with policy components 
 read in from external policy files downloaded separately to the server. This 
 work is motivated by one of the rampart sample applications that loads policy 
 files on the fly - I want to be able to demonstrate on-the-fly policy changes 
 in an axis service as well..
 I wrote some service code that merges and normalizes policy components into a 
 single policy object, which is applied to the axisService using 
 applyPolicy(). I was able to verify in a debugger that the new policy object 
 is correctly formed and stored in the axisService's policyInclude. The 
 problem that I'm seeing is that the configurationContext that my service code 
 updates with this new policy info is not the same instance that is used to 
 initialize the messageContext for incoming SOAP messages. This second 
 configurationContext is created when the AxisServlet is initialized, before 
 my new policy is constructed, and there does not appear to be anyway to 
 access this configurationContext instance within my service code. 
 One possible solution would be for the ConfigurationContextFactory to 
 maintain a reference to the initial configurationContext instance that it 
 creates and to provide a static method that can be used to retrieve it from 
 within the service code.  I'm putting this in as an improvement request, but 
 I'm not sure why there is a global context that is not globally accessible. I 
 don't know the axis kernel well enough to understand why this would be a bad 
 idea.
 Is there any other way to access the configurationContext instance maintained 
 by the AxisServlet?
 Any ideas would be appreciated!
 Thanks,
 Jackson Wynn
 Lead Infosec Engineer - G026
 The MITRE Corporation
 Bedford, MA

-- 
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-2683) Doc enhancements -- json-support / jms-transport / installation guide


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

Jaliya Ekanayake updated AXIS2-2683:


Fix Version/s: 1.3

 Doc enhancements -- json-support / jms-transport / installation guide
 -

 Key: AXIS2-2683
 URL: https://issues.apache.org/jira/browse/AXIS2-2683
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: documentation
Affects Versions: 1.2
Reporter: Glen Mazza
Assignee: Chatra Nakkawita
 Fix For: 1.3

 Attachments: jsonjmsinstallpatch.txt


 Patch for cleanup / enhancements to three more documents.

-- 
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-2741) Attachment using org.apache.axis2.rpc.receivers.RPCMessageReceiver is broken


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

Srinath Perera updated AXIS2-2741:
--

Priority: Blocker  (was: Major)

 Attachment using org.apache.axis2.rpc.receivers.RPCMessageReceiver is broken
 

 Key: AXIS2-2741
 URL: https://issues.apache.org/jira/browse/AXIS2-2741
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: transports
Affects Versions: 1.2
 Environment: Axis2-1.2 release/ WindowsLinux /Jboss 4.05GA
Reporter: Aliho
Assignee: Deepal Jayasinghe
Priority: Blocker

 org.apache.axis2.rpc.receivers.RPCMessageReceiver will throw a 
 NumberFormatException from trying to create a Byte object from a long binary 
 string.
 ==TestService.java=
 package test;
 public class TestService{
   
   public String Test(String fileName, String contentType, byte[] binary){
 return boom!;
   }
 }
 =service.xml=
   service name=TestService
scope=application
descriptionThis is used for testing/description
   messageReceivers
   messageReceiver 
 mep=http://www.w3.org/2004/08/wsdl/in-only;

 class=org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver/
   messageReceiver 
 mep=http://www.w3.org/2004/08/wsdl/in-out;

 class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/
   /messageReceivers
   parameter 
 name=useOriginalwsdlfalse/parameter 
parameter name=ServiceClasstest.TestService/parameter
   /service  
 The above pojo will generate the following WSDL file.
 Generated wsdl===
 wsdl:definitions xmlns:axis2=http://test; 
 xmlns:ns1=http://org.apache.axis2/xsd; 
 xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
 xmlns:http=http://schemas.xmlsoap.org/wsdl/http/; 
 xmlns:ns0=http://test/xsd; xmlns:xs=http://www.w3.org/2001/XMLSchema; 
 xmlns:mime=http://schemas.xmlsoap.org/wsdl/mime/; 
 xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 
 xmlns:soap12=http://schemas.xmlsoap.org/wsdl/soap12/; 
 targetNamespace=http://test;wsdl:documentationTestService/wsdl:documentationwsdl:typesxs:schema
  xmlns:ns=http://test/xsd; attributeFormDefault=qualified 
 elementFormDefault=qualified targetNamespace=http://test/xsd;
 xs:element name=Test
 xs:complexType
 xs:sequence
 xs:element name=fileName nillable=true type=xs:string /
 xs:element name=contentType nillable=true type=xs:string /
 xs:element name=binary nillable=true type=xs:base64Binary /
 /xs:sequence
 /xs:complexType
 /xs:element
 xs:element name=TestResponse
 xs:complexType
 xs:sequence
 xs:element name=return nillable=true type=xs:string /
 /xs:sequence
 /xs:complexType
 /xs:element
 /xs:schema/wsdl:typeswsdl:message name=TestMessagewsdl:part 
 name=part1 element=ns0:Test //wsdl:messagewsdl:message 
 name=TestResponsewsdl:part name=part1 element=ns0:TestResponse 
 //wsdl:messagewsdl:portType name=TestServicePortTypewsdl:operation 
 name=Testwsdl:input 
 xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl; 
 message=axis2:TestMessage wsaw:Action=urn:Test /wsdl:output 
 message=axis2:TestResponse //wsdl:operation/wsdl:portTypewsdl:binding 
 name=TestServiceSOAP11Binding 
 type=axis2:TestServicePortTypesoap:binding 
 transport=http://schemas.xmlsoap.org/soap/http; style=document 
 /wsdl:operation name=Testsoap:operation soapAction=urn:Test 
 style=document /wsdl:inputsoap:body use=literal 
 //wsdl:inputwsdl:outputsoap:body use=literal 
 //wsdl:output/wsdl:operation/wsdl:bindingwsdl:binding 
 name=TestServiceSOAP12Binding 
 type=axis2:TestServicePortTypesoap12:binding 
 transport=http://schemas.xmlsoap.org/soap/http; style=document 
 /wsdl:operation name=Testsoap12:operation soapAction=urn:Test 
 style=document /wsdl:inputsoap12:body use=literal 
 //wsdl:inputwsdl:outputsoap12:body use=literal 
 //wsdl:output/wsdl:operation/wsdl:bindingwsdl:binding 
 name=TestServiceHttpBinding type=axis2:TestServicePortTypehttp:binding 
 verb=POST /wsdl:operation name=Testhttp:operation location=Test 
 /wsdl:inputmime:content type=text/xml 
 //wsdl:inputwsdl:outputmime:content type=text/xml 
 //wsdl:output/wsdl:operation/wsdl:bindingwsdl:service 
 name=TestServicewsdl:port name=TestServiceSOAP11port_http 
 binding=axis2:TestServiceSOAP11Bindingsoap:address 
 location=http://10.67.90.102:/cms-war-0.0.1/services/TestService; 
 //wsdl:portwsdl:port name=TestServiceSOAP11port_tcp1 
 binding=axis2:TestServiceSOAP11Bindingsoap:address 
 location=tcp://10.67.90.102:6061/axis2/services/TestService 
 //wsdl:portwsdl:port name=TestServiceSOAP12port_http

[jira] Updated: (AXIS2-2677) Updates to online docs


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

Jaliya Ekanayake updated AXIS2-2677:


Fix Version/s: 1.3

 Updates to online docs
 --

 Key: AXIS2-2677
 URL: https://issues.apache.org/jira/browse/AXIS2-2677
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: documentation
Reporter: Glen Mazza
Assignee: Chatra Nakkawita
 Fix For: 1.3

 Attachments: sixfilepatch.txt


 Updates to these files: Axis2ArchitectureGuide.html, axis2config.html, 
 Axis2-rpc-support.html, contents.html, adv-userguide.html, app_server.html

-- 
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-2584) AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file (interpreted as a URI)


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

Glen Daniels updated AXIS2-2584:


Fix Version/s: 1.3

 AAR deployment fails with a WSDL 2 document due to spaces in path to AAR file 
 (interpreted as a URI)
 

 Key: AXIS2-2584
 URL: https://issues.apache.org/jira/browse/AXIS2-2584
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: deployment
Affects Versions: nightly
 Environment: Windows XP, Apache Tomcat 6
Reporter: Steven E. Harris
Assignee: Keith Godwin Chapman
 Fix For: 1.3

 Attachments: ArchiveReader.java.diff, ArchiveReader.java.diff


 The class org.apache.axis2.deployment.repository.util.ArchiveReader attempts 
 to construct a JAR-based URI in its processWSDLFile() method:
 } else if (axisServiceBuilder instanceof 
 WSDL20ToAxisServiceBuilder) {
 // trying to use the jar scheme as the base URI. I think 
 this can be used to handle
 // wsdl 1.1 as well without using a custome URI resolver. 
 Need to look at it later.
 axisServiceBuilder.setBaseUri(
 jar:file:// + 
 serviceArchiveFile.getAbsolutePath() + !/ + baseURI);
 }
 The call to serviceArchiveFile.getAbsolutePath() creates a path string with 
 embedded spaces and backslashes (on Windows). The java.net.URI constructor 
 rejects such a path, emitting an error such as:
 INFO: Trouble processing wsdl file :Illegal character in opaque part at index 
 13: jar:file://C:\Program 
 Files\\apache-tomcat-6.0.10\webapps\axis2\WEB-INF\services\my.service.aar!/META-INF/myservice.wsdl
 Note that it's complaining about the backslash after the C:' part.
 The fix is simple: build the new URI from yet another URI:
 axisServiceBuilder.setBaseUri(
 jar: + serviceArchiveFile.toURI() + !/ + 
 baseURI);
  

-- 
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-2326) WSDL2Java generates too many if sentences in MessageReceiver's fromOM method with xmlbeans


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

Deepal Jayasinghe updated AXIS2-2326:
-

Priority: Blocker  (was: Trivial)

 WSDL2Java generates too many if sentences in MessageReceiver's fromOM method 
 with xmlbeans
 --

 Key: AXIS2-2326
 URL: https://issues.apache.org/jira/browse/AXIS2-2326
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen
Affects Versions: 1.1.1
 Environment: Windows XP SP2, Java 1.5, Eclipse 3.2.2, Eclipse Axis 
 Plugin 1.2.1
Reporter: Jorge Fernández
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: API.wsdl, Medici_LinkMessageReceiverInOut.java


 If I define in a wsdl that different methods are throwing the same exception, 
 in the fromOM method of the MessageReceiver class generated, it appears a if 
 statement for the exception as many times as methods are throwing it.
 Something similar happens in the generated stub's method populateFaults. Each 
 fault is defined many times, I think as many as methods are throwing them in 
 the skeleton.

-- 
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-1986) axis looking in wrong place for generated ADB factory


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

Eran Chinthaka updated AXIS2-1986:
--

Fix Version/s: 1.3
 Priority: Blocker  (was: Major)

 axis looking in wrong place for generated ADB factory
 -

 Key: AXIS2-1986
 URL: https://issues.apache.org/jira/browse/AXIS2-1986
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: adb
Affects Versions: 1.1.1
 Environment: linux
Reporter: chad davis
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Fix For: 1.3


 I've created and partially successfully run the ADB client from the
 user guide.  See following link:
 http://ws.apache.org/axis2/1_1_1/userguide-creatingclients.html#adb
 My Problem:
 I've got 3 of four requests / responses behaving properly.  On the
 fourth, the multiple parameters in both directions one, it blows up
 with a classnotfound on the MultipleParametersAddItemRequest$Factory
 class.  This class does exist on the classpath.  The problem is that
 it is an inner class, as created by the wsdl2java with ADB set.  It
 seems that axis2 is looking for the the MPARequest as a toplevel
 class?  Below is the stack trace.  How is this generated Request any
 different than the ones for the first three requests?
 calling do in only
 done
 calling two way echo
 Knock Knock
 calling no parameters.
 [EMAIL PROTECTED]
 calling mulitp param
 org.apache.axis2.AxisFault: java.lang.NoClassDefFoundError:
 org/apache/axis2/axis2userguide/MultipleParametersAddItemRequest$Factory
at 
 org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:271)
at 
 org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
at 
 org.apache.axis2.axis2userguide.Axis2UserGuideServiceStub.MultipleParametersAddItem(Axis2UserGuideServiceStub.java:398)
at 
 org.apache.axis2.axis2userguide.TestClient.multipleParameters(TestClient.java:89)
at org.apache.axis2.axis2userguide.TestClient.main(TestClient.java:26)

-- 
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-2677) Updates to online docs


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

Jaliya Ekanayake updated AXIS2-2677:


Priority: Blocker  (was: Major)

 Updates to online docs
 --

 Key: AXIS2-2677
 URL: https://issues.apache.org/jira/browse/AXIS2-2677
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: documentation
Reporter: Glen Mazza
Assignee: Chatra Nakkawita
Priority: Blocker
 Fix For: 1.3

 Attachments: sixfilepatch.txt


 Updates to these files: Axis2ArchitectureGuide.html, axis2config.html, 
 Axis2-rpc-support.html, contents.html, adv-userguide.html, app_server.html

-- 
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-2322) If i generate skeleton classes, interfaces and stubs using the no matter what version of axis2 I use


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

Deepal Jayasinghe updated AXIS2-2322:
-

Priority: Blocker  (was: Critical)

 If i generate skeleton classes, interfaces and stubs using the no matter what 
 version of axis2 I use
 

 Key: AXIS2-2322
 URL: https://issues.apache.org/jira/browse/AXIS2-2322
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: codegen, databinding, deployment, wsdl
Affects Versions: 1.1.1, 1.1, 1.0
 Environment: Windows 2000, sdk 1.5
Reporter: John McCosker
Assignee: Amila Chinthaka Suriarachchi
Priority: Blocker
 Attachments: build.xml, GENI_CommonTypes.xsd, 
 GENI_FileSystemModifyService.wsdl, GENI_FileSystemModifyServiceTypes.xsd


 If i generate skeleton classes, interfaces and stubs using the
 wsdl2java ant task I can't then compile my classes,
 now I know its because all of the below mentioned methods (and others)
 fromOM(result.getResponseEnvelope().getBody().getFirstElement() and
 toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI())
 fromOM(faultElt,messageClass,null)
 are not included in org.apache.axis2.client.Stub as they have been
 left out for what-ever reason. All online documentation and mailing
 list indicated that,
 getElement()  method was removed from the stub class sometime back,
 since the generated code no longer uses it.
 Please use the latest nightlies to generate your code... 
 Ok, I have done that, does'nt work.
 Others suggest get the latest stable build, what version is stable,
 have tried, 1.0, 1.1, 1.1.1, extracted axis.war tried that, and tried
 axis2-1.1.1-SNAPSHOT,
 but all gave the same error.
 What version of axis will stop creating the these properties in the
 stubs so that I can then compile it.

-- 
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-2729) Documentation Clarification on the use of .aar and .mar files