date:20060526


Is this is a BUG

I have used WSDL2Java to generate code and test class,

Axis2 1.0,

I get this error when I run it,  I have copied schema and wsdl to can
recreate this problem after generating code from WSDL2Java  and running test

I get this problem with all my wsdl??

Even I tried with sample Axis2SampleDocLit.wsdl from axis2 distribution

Testcase: testHelloWorldOperation took 1.059 sec
Caused an ERROR
java.lang.IllegalStateException
org.apache.axiom.om.OMException: java.lang.IllegalStateException
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:206)
at
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:144)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:322)
at org.apache.axis2.HelloWorldStub.toOM(HelloWorldStub.java:302)
at org.apache.axis2.HelloWorldStub.toEnvelope(HelloWorldStub.java:317)
at
org.apache.axis2.HelloWorldStub.HelloWorldOperation(HelloWorldStub.java:119)
at
org.apache.axis2.HelloWorldTest.testHelloWorldOperation(HelloWorldTest.java:30)
Caused by: java.lang.IllegalStateException
at
org.apache.xmlbeans.impl.store.Jsr173$XMLStreamReaderForString.next(Jsr173.java:1110)
at
org.apache.xmlbeans.impl.store.Jsr173$SyncedJsr173.next(Jsr173.java:1138)
at org.apache.axis2.util.StreamWrapper.next(StreamWrapper.java:68)
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:123)
... 21 more

--
HelloWorld.wsdl

?xml version=1.0 encoding=UTF-8?
wsdl:definitions xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; 

xmlns:tns=http://www.liquid.com/ns/keystone/helloworld; 
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/; 
xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
name=HelloWorld 

targetNamespace=http://www.liquid.com/ns/keystone/helloworld; 

xmlns:ass=http://www.liquid.com/ns/keystone/asset;

wsdl:import namespace=http://www.liquid.com/ns/keystone/asset;
location=asset.xsd/wsdl:import

wsdl:message name=HelloWorldOperationResponse
wsdl:part element=ass:Asset 
name=HelloWorldOperationResponse/
/wsdl:message
wsdl:message name=HelloWorldOperationRequest
wsdl:part element=ass:Asset 
name=HelloWorldOperationRequest/
/wsdl:message
wsdl:portType name=HelloWorld
wsdl:operation name=HelloWorldOperation
wsdl:input message=tns:HelloWorldOperationRequest/
wsdl:output message=tns:HelloWorldOperationResponse/
/wsdl:operation
/wsdl:portType
wsdl:binding name=HelloWorldSOAP type=tns:HelloWorld
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=HelloWorldOperation
soap:operation soapAction=HelloWorldOperation/
wsdl:input
soap:body parts=HelloWorldOperationRequest 
use=literal/
/wsdl:input
wsdl:output
soap:body parts=HelloWorldOperationResponse 
use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:service name=HelloWorld
wsdl:port binding=tns:HelloWorldSOAP name=HelloWorldSOAP
soap:address
location=http://la00771.liquid.com:8080/axis2/services/helloWorld/
/wsdl:port
/wsdl:service
/wsdl:definitions


asset.xsd

?xml version=1.0 encoding=UTF-8?
!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by Brad
Neighbors (Liquid Digital Media) --
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ns1=http://www.liquid.com/ns/keystone/asset;
targetNamespace=http://www.liquid.com/ns/keystone/asset;
elementFormDefault=qualified attributeFormDefault=unqualified
xs:element name=Asset type=ns1:AssetType/
xs:complexType name=AssetType
xs:sequence
xs:choice
xs:element name=Audio 
type=ns1:AudioAssetType/
xs:element name=Video 
type=ns1:VideoAssetType/
xs:element name=Image 
type=ns1:ImageAssetType/
/xs:choice
/xs:sequence
xs:attribute name=id type=xs:string use=optional/
xs:attribute name=size type=xs:long use=optional/
/xs:complexType
xs:complexType name=AudioAssetType
xs:sequence
xs:element name=Duration

Axis2[1.0] war in Weblogic 9.1


I tried axis2.war deploying on weblogic 9.1 as war, deployment was sucessful
but unable to load version service.

But if I use exploded war it works..

Any idea why it's happening, did any one had success runing axis2.war under
weblogic 9.1

Thanks
Gopal
--
View this message in context: 
http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990
Sent from the Axis - User forum at Nabble.com.


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

Re[2]: Axis2 High memory usage, OutOfMemory exception

2006-05-26 Thread Andreas Hörnicke


If you really want to store configurations from a service or
module i think you'd better use their contexts (again my proposal
of adding a init-method to the AbstractMessageReceiver to do some
one-time operations :) instead of http sessions. Because if some
client-api lacks the feature of sessions you might ran into an
even bigger problem.

-- Andreas

am Freitag, 26. Mai 2006 schrieb Rodrigo Ruiz:

RR Hi,

RR AFAIK, Axis 1 did not create HTTP sessions. I believe Axis 2 does, and
RR that may be the difference.

RR The suggestion of Andreas may work for you now, but I guess it may lead
RR you to some problems in a future, as other services or modules may need
RR the session to store configurations. Anyway, I would prefer a filter for
RR invalidating the session. Is less invasive than an AxisServlet subclass.

RR I think a better approach would be to activate HTTP session support on
RR your client, if you have control on it. This way, only one session would
RR be needed on your server. I don't know if this is possible, but being
RR Axis 2 HTTP transport based on commons-http-client, there must be a way
RR to activate this.

RR If the session support is already activated, perhaps you need to
RR refactor your test somehow to take advantage of it.

RR Maybe someone can bring some light on this subject :-)

RR Regards,
RR Rodrigo Ruiz

RR Ramanathan, Subramanyam wrote:
 Hi,
 
 Regarding setting the session-timeout, I found that
 session-timeout in Axis1 was set to 5 minutes by default, so I
 set it to 30 minutes in axis1 as well, just to compare.
 However, I don't find any big memory consumption increase when
 I pump requests. 
 
 As a matter of fact, the memory usage stays between 10 and
 25 M, whereas with axis2, even after setting session-timeout
 to 2 min, usage touches 100M frequently. So I am not sure that
 setting the session-timeout is a good workaround.
 Is there any reason for this high memory usage in axis2 as against axis1 ?
 
 I have not yet tried Andreas' suggestion, though, and I will do so now.
 
 Thanks and Regards, 
 Subramanyam
 
 
 -Original Message-
 From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
 Sent: Thursday, May 25, 2006 11:43 PM
 To: axis-user@ws.apache.org; Andreas Hörnicke
 Subject: Re: Re[2]: Axis2 High memory usage, OutOfMemory exception
 
 
 Andreas,
 
 Could you *please* add this info to bug report AXIS2-766?
 
 thanks,
 dims
 
 On 5/25/06, Andreas Hörnicke [EMAIL PROTECTED] wrote:
 Here is what i did to overcome this problem: After defining my
 own SessionListener and invalidating the created sessions
 immediately i got some exceptions thrown by axis. So my current
 solution is to extend the AxisServlet, overriding the service
 method and invalidate the session after super.service was called.
 Works fine in my testing environment.

 -- Andreas


 KI (tomcat)/conf/web.xml will contains session-timeout settings,
 KI and that value is default to 30 min.
 KI (tomcat)/webapps/axis2/WEB-INF/web.xml will not have this settings.

 KI I'm not sure but here is my guess,

 KI Service will run as servlet of tomcat, I think.
 KI And each servlet threads for invoked services will remain as session.
 KI After receiving request and send back response,
 KI web service session should be clear or invalidate by Axis2.
 KI But results of your test seems to remain those sessions until timeout.
 KI So, set the session-timeout to minimum value is work around for this.

 KI How everyone think about this ?

 KI Regards,
 KI kinichiro

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

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


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


 
 

RR -- 
RR ---
RR GRIDSYSTEMSRodrigo Ruiz Aguayo
RR Parc Bit - Son Espanyol
RR 07120 Palma de Mallorcamailto:[EMAIL PROTECTED]
RR Baleares - España  Tel:+34-971435085 Fax:+34-971435082
RR http://www.gridsystems.com
RR ---




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

Re: Axis2[1.0] war in Weblogic 9.1

2006-05-26 Thread Ali Sadik Kumlali

Hi Gopal,The same problem exists with WL8.1 SP4. What I saw there, when the war is uploaded by using console application, war is not totally extracted. Only some of subfolders and the files are extracted. May be the same extraction problem exists on WL9.1, too.I don't know why this happens, though.Regards,Ali Sadik KumlaliGopal Patwa [EMAIL PROTECTED] wrote: I tried axis2.war deploying on weblogic 9.1 as war, deployment was sucessfulbut unable to load version service.But if I use exploded war it works..Any idea why it's happening, did any one had success runing axis2.war underweblogic 9.1ThanksGopal--View this message in context: http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990Sent from the Axis - User forum at
 Nabble.com.-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
		How low will we go? Check out Yahoo! Messengers low  PC-to-Phone call rates.

Re: Axis2[1.0] war in Weblogic 9.1

2006-05-26 Thread Rodrigo Ruiz

Hi,

The behaviour you describe is perfectly normal with regard to the
Servlet Specification.

When deploying Axis 2 as a war, the container is not creating a
read-write directory structure, and peforms all accesses directly
through the war archive, instead of unpacking it. Whether to unpack the
WAR or not is up to the container implementation, and the specification
allows both options.

If you are interested in distributing Axis 2 with a set of fixed
pre-deployed services/modules, you can try to put those services/modules
directly within the war, and deploy the modified war. I am not sure at
all if this will work in the current version as, AFAIK, Axis 2 uses
custom classloaders for isolating services that might not work in this
mode. Anyway, I don't see any technical reason why this should not be
possible.

In any case, deploying it as an exploded war is the correct way to
prevent those errors.

Hope this helps,
Rodrigo Ruiz

Ali Sadik Kumlali wrote:

Hi Gopal,

The same problem exists with WL8.1 SP4. What I saw there, when the war
is uploaded by using console application, war is not totally extracted.
Only some of subfolders and the files are extracted. May be the same
extraction problem exists on WL9.1, too.

I don't know why this happens, though.

Regards,

Ali Sadik Kumlali

*/Gopal Patwa [EMAIL PROTECTED]/* wrote:

I tried axis2.war deploying on weblogic 9.1 as war, deployment was
sucessful
but unable to load version service.

But if I use exploded war it works..

Any idea why it's happening, did any one had success runing
axis2.war under
weblogic 9.1

Thanks
Gopal
--
View this message in context:
http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990
Sent from the Axis - User forum at Nabble.com.

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

How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call
rates.
http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date: 25/05/2006

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com

--
---
GRIDSYSTEMSRodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorcamailto:[EMAIL PROTECTED]
Baleares - España Tel:+34-971435085 Fax:+34-971435082
http://www.gridsystems.com
---

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date: 25/05/2006

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

Pls Help: Server returned HTTP response code: 500 for URL

2006-05-26 Thread Amjad Abu Zur - TusAlas




Hi all:

I have this code:




urlConn.setRequestProperty(Accept Encoding,gzip);
printout = new DataOutputStream(new
GZIPOutputStream(urlConn.getOutputStream())); //create a gzipped stream
String content = 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
+xmlPrueba+ /SOAP-ENV:Body/SOAP-ENV:Envelope;

printout.writeBytes(content); // write your request to the gzipped
output 
printout.flush();
printout.close();
encoding = urlConn.getContentEncoding();


if (encoding != null  encoding.equalsIgnoreCase(gzip)) {
System.out.println(THIS IS A GZIPED STREAM);

InputStream is= urlConn.getInputStream();   

input = new GZIPInputStream(is);

}
Else
...

I get the error Server returned HTTP response code: 500 for URL: .. in
the following line:
InputStream is= urlConn.getInputStream();   

I'm sending soap messague 
I do not how to deal with this error. I can not see if this is an error
of my soap message or of the communication.

thanks




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

Re: Pls Help: Server returned HTTP response code: 500 for URL

2006-05-26 Thread ajax chelsea

it seems that (Accept Encoding,gzip) should be set at server side.2006/5/26, Amjad Abu Zur - TusAlas [EMAIL PROTECTED]
:Hi all:I have this code:urlConn.setRequestProperty
(Accept Encoding,gzip);printout = new DataOutputStream(newGZIPOutputStream(urlConn.getOutputStream())); //create a gzipped streamString content = SOAP-ENV:Envelopexmlns: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+xmlPrueba+ /SOAP-ENV:Body/SOAP-ENV:Envelope;printout.writeBytes(content); // write your request to the gzippedoutputprintout.flush
();printout.close();encoding = urlConn.getContentEncoding();if (encoding != null  encoding.equalsIgnoreCase(gzip)) {System.out.println(THIS IS A GZIPED STREAM);
InputStream is= urlConn.getInputStream();input = new GZIPInputStream(is);}Else...I get the error Server returned HTTP response code: 500 for URL: .. in
the following line:InputStream is= urlConn.getInputStream();I'm sending soap messagueI do not how to deal with this error. I can not see if this is an errorof my soap message or of the communication.
thanks-To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Pls Help: Server returned HTTP response code: 500 for URL

2006-05-26 Thread Amjad Abu Zur - TusAlas









Dear ajax:



The server accept gzip encoding.













De: ajax chelsea
[mailto:[EMAIL PROTECTED] 
Enviado el: viernes, 26 mayo, 2006
11:30
Para: axis-user@ws.apache.org
Asunto: Re: Pls Help: Server
returned HTTP response code: 500 for URL





it seems that
(Accept Encoding,gzip) should be set at server side.



2006/5/26, Amjad Abu Zur - TusAlas [EMAIL PROTECTED] :




Hi all:

I have this code:




urlConn.setRequestProperty (Accept Encoding,gzip);
printout = new DataOutputStream(new
GZIPOutputStream(urlConn.getOutputStream())); //create a gzipped stream
String content = 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
+xmlPrueba+ /SOAP-ENV:Body/SOAP-ENV:Envelope;

printout.writeBytes(content); // write your request to the gzipped
output
printout.flush ();
printout.close();
encoding = urlConn.getContentEncoding();


if (encoding != null 
encoding.equalsIgnoreCase(gzip)) {
System.out.println(THIS
IS A GZIPED STREAM); 

InputStream
is= urlConn.getInputStream();

input
= new GZIPInputStream(is);

}
Else
...

I get the error Server returned HTTP response code: 500 for URL: ..
in 
the following line:
InputStream is= urlConn.getInputStream();

I'm sending soap messague
I do not how to deal with this error. I can not see if this is an error
of my soap message or of the communication. 

thanks




-
To unsubscribe, e-mail: [EMAIL PROTECTED]

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

Re: Axis2[1.0] war in Weblogic 9.1

2006-05-26 Thread Ali Sadik Kumlali

Thanks Rodrigo.

--- Rodrigo Ruiz [EMAIL PROTECTED] wrote:

 Hi,
 
 The behaviour you describe is perfectly normal with regard to the 
 Servlet Specification.
 
 When deploying Axis 2 as a war, the container is not creating a 
 read-write directory structure, and peforms all accesses directly 
 through the war archive, instead of unpacking it. Whether to unpack
 the 
 WAR or not is up to the container implementation, and the
 specification 
 allows both options.
 
 If you are interested in distributing Axis 2 with a set of fixed 
 pre-deployed services/modules, you can try to put those
 services/modules 
 directly within the war, and deploy the modified war. I am not sure
 at 
 all if this will work in the current version as, AFAIK, Axis 2 uses 
 custom classloaders for isolating services that might not work in
 this 
 mode. Anyway, I don't see any technical reason why this should not
 be 
 possible.
 
 In any case, deploying it as an exploded war is the correct way to 
 prevent those errors.
 
 Hope this helps,
 Rodrigo Ruiz
 
 Ali Sadik Kumlali wrote:
  Hi Gopal,
  
  The same problem exists with WL8.1 SP4. What I saw there, when the
 war 
  is uploaded by using console application, war is not totally
 extracted. 
  Only some of subfolders and the files are extracted. May be the
 same 
  extraction problem exists on WL9.1, too.
  
  I don't know why this happens, though.
  
  Regards,
  
  Ali Sadik Kumlali
  
  */Gopal Patwa [EMAIL PROTECTED]/* wrote:
  
  
  I tried axis2.war deploying on weblogic 9.1 as war, deployment
 was
  sucessful
  but unable to load version service.
  
  But if I use exploded war it works..
  
  Any idea why it's happening, did any one had success runing
  axis2.war under
  weblogic 9.1
  
  Thanks
  Gopal
  --
  View this message in context:
 

http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990
  Sent from the Axis - User forum at Nabble.com.
  
  
 
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
  
 


  How low will we go? Check out Yahoo! Messenger#65533;s low
PC-to-Phone
 call 
  rates. 
 

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com
  
  
  

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com
 


  
  No virus found in this incoming message.
  Checked by AVG Free Edition.
  Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date:
 25/05/2006
  

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com
 
 -- 
 ---
 GRIDSYSTEMSRodrigo Ruiz Aguayo
 Parc Bit - Son Espanyol
 07120 Palma de Mallorcamailto:[EMAIL PROTECTED]
 Baleares - España  Tel:+34-971435085 Fax:+34-971435082
 http://www.gridsystems.com
 ---
 
 
 -- 
 No virus found in this outgoing message.
 Checked by AVG Free Edition.
 Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date:
 25/05/2006
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 


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

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

get server name

2006-05-26 Thread Matteo Cremolini


Hi,

can i retrieve (at run-time) in my web servcie the name or address of the server in them 
my web service is deployed???

Any suggestion??

Matteo


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

Re: AXIS2 1.0

2006-05-26 Thread Deepal Jayasinghe

Hmm , can u pls create a JIRA ,I think this a bug.

Suyog Gandhi wrote:

I am using AXIS2, RPCMessageReceiver.

I am passing following obbject as a parameter in one of my call.

WMemberInfo
   |- ID
   |- WMemberAttribute []
   |- Name
   |- Value
   |- isChanged

 I can get value of ID properly. But I cannot get WMemberAttribute
properly. On SOAP monitor I can see request XML is proper. But I get
null in all the place holders in WMemberAttribute ( i.e Name, value are
null and isChanged is false default value.). 

I checked the tracker variables, all the tracker variables are true. ( I
think it means it will serialize the object.)

Anyboyd has any insight on how to tackel this problem. ( Using 25 May
2006 Nightly build).

Thanks  Regards,
Suyog




  


-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: [Axis2] How to build aar and Axis2 war with Maven2?

2006-05-26 Thread Deepal Jayasinghe

Hi Dave ;
I dont think you need to compile Axis2 code , what I think is you have
to add dependency into your project to pick Axis2 jars from apache repo.

Dave Hoffer wrote:

 I would like to start using Axis2 in a new project. The project will
 use Maven2 as the build system. How can I integrate Axis2?
 Specifically, how do I?

 - Compile my sources into the Axis aar format? Or take my
 application’s jar and create the Axis2 aar format?

 - Take the Axis2 aar and make the Axis war needed for deployment.

 I would greatly appreciate info on how to do this.

 -dh


-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: [Axis2]How to process SOAP header in service class? or handler class?

2006-05-26 Thread Deepal Jayasinghe

Hi Sukie;
pls see my comment blow;

蘇 軼（CEC） wrote:

hi Chinthaka,

Thank you for your help !

Please let me ask tow more question :

1. If I don't use RawXMLINOutMessageReceiver, I can't
process headers in service method?
  

If you use any of the default message receivers in Axis2 you can get
access to OperationContext , only requirement is to have
setOperationContext method in service impl class.

2. The setOperationContext(...) method is ONE method,
what could I do when I want to deal headers in different
way because client calls different method?
  

I think you are missing smt , say your service impl class is as follows

class MyService {
public void setOperationContext (OperationConetxt opctx) {
}

public String echo(String val){
return val;
}

public int add(int a , int b){
return a + b;
}
}

So client can call either add or echo but not the setOperationContex ,
coz that method is not visible to him. If he call either add or echo
setOperationConetxt method will be called. When there is a req for ur
service and if the service has setOperationConetxt method then first it
will called setOperationContext and then it will called the actual java
method client want to invoke.

Thank you !

- sukie


- Original Message - 
From: Eran Chinthaka [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Wednesday, May 24, 2006 6:35 PM
Subject: Re: [Axis2]How to process SOAP header in service class? or handler
class?



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



  


-- 
Thanks,
Deepal

~Future is Open~ 



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

Re: get server name

2006-05-26 Thread Michele Mazzucco

Yes,

you can in the usual way (i.e. through java.net.InetAddress).

Michele

Matteo Cremolini wrote:
 Hi,
 
 can i retrieve (at run-time) in my web servcie the name or address of
 the server in them my web service is deployed???
 Any suggestion??
 
 Matteo
 
 
 -
 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]

Deployment with JDK5 and annotations?

2006-05-26 Thread Larry Meadors


Are there any examples of doing annotation-based deployment of web
services with axis?

I can't help but think that if I can generate all of the XML that I
need to use for deployment, that I could auto-deploy web services
based on annotations, but I haven't seen anything like that anywhere
in the Java world, only in ASP.NET.

Larry

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

Re: REPOST FOR HELP: Axis client logging from web applet causes security error

I'm sorry. I do not know how to do that.- Original Message From: Davanum Srinivas [EMAIL PROTECTED]To: axis-user@ws.apache.org; ANTHONY ZIOLKOWSKI [EMAIL PROTECTED]Cc: robert lazarski [EMAIL PROTECTED]Sent: Thursday, May 25, 2006 10:40:47 PMSubject: Re: REPOST FOR HELP: Axis client logging from web applet causes security errorPlease check the archives...you need a fresh jar of commons-discoverybuilt from the SVN sources for discovery.thanks,dimsOn 5/25/06, ANTHONY ZIOLKOWSKI [EMAIL PROTECTED] wrote: I moved to axis 1.4 and the problem went away. Unfortunately to be replaced by another
 problem. My console client stub still works fine. Running under firefox i get the following message in the Java Console window: Failure trying to get the Call object; nested exception is: java.lang.NoClassDefFoundError That's it, no stack trace, nothing in the Tomcat logs When I run under IE6 I get the following error and stack trace: Exception in thread "AWT-EventQueue-2" java.lang.ExceptionInInitializerError at org.apache.commons.discovery.jdk.JDKHooks.clinit(JDKHooks.java:75) at org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:412) at org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:378) at
 org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45) at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41) at org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:33) at org.apache.axis.handlers.BasicHandler.clinit(BasicHandler.java:43) at org.apache.axis.client.Service.getAxisClient(Service.java:104) at org.apache.axis.client.Service.init(Service.java:113) at com.zeesol.bizservice.client.BizService_ServiceLocator.init(BizService_ServiceLocator.java:12) at
 com.mazuma.applets.BaseRunner$1.actionPerformed(BaseRunner.java:156) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at
 java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at
 java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader) at java.security.AccessControlContext.checkPermission(Unknown Source) at java.security.AccessController.checkPermission(Unknown Source) at java.lang.SecurityManager.checkPermission(Unknown Source) at
 java.lang.SecurityManager.checkCreateClassLoader(Unknown Source) at java.lang.ClassLoader.init(Unknown Source) at org.apache.commons.discovery.jdk.PsuedoSystemClassLoader.init(PsuedoSystemClassLoader.java:73) at org.apache.commons.discovery.jdk.JDK12Hooks.findSystemClassLoader(JDK12Hooks.java:215) at org.apache.commons.discovery.jdk.JDK12Hooks.clinit(JDK12Hooks.java:73) ... 35 more - Original Message  From: robert lazarski [EMAIL PROTECTED] To: axis-user@ws.apache.org; ANTHONY ZIOLKOWSKI [EMAIL PROTECTED] Sent: Monday, May 8, 2006 8:36:16 AM Subject: Re: REPOST FOR HELP: Axis client logging from web applet causes security error I suspect this is primarily a
 log4j / commons-logging issue. Try editing the propertiesof each and comment out the file appenders. Or simply enable log4j based logging in the commons property file, and use your own log4j.properties file instead of the one that comes with axis. I'm enclosing my log4j.properties file that should do just that (I removed the file appender, but I didn't test it). It will still print lines to the console via stdout / stderr , but that shouldn't be a problem. Look in your browser in the tools section to view an applets stdout / stderr messages if you want to see them.HTH,Roberthttp://www.braziloutsource.com/ On 5/8/06, ANTHONY ZIOLKOWSKI [EMAIL PROTECTED]  wrote:  
 This is

Re: Complex type problem

2006-05-26 Thread Roy

I tried the beanmapping too but it didn't work. This is the the complex type i want to send and the deploy.wsdd file:Deploy.wsdd:deployment xmlns="http://xml.apache.org/axis/wsdd/" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" service name="EJBTestService" provider="java:EJB"  parameter name="wsdlTargetNamespace" value="http://ejb.test.com"/  parameter name="beanJndiName" value="ejb/TestService"/  parameter name="homeInterfaceName" value="com.test.ejb.TestServiceHome"/  parameter name="remoteInterfaceName" value="com.test.ejb.TestService"/  parameter name="allowedMethods" value="*"/  operation name="sendData"
 qname="operNS:SendData" xmlns:operNS="http://test.com/ejb/" returnQName="retNS:Result" xmlns:retNS="http://test.com/ejb/" returnType="rtns:int" xmlns:rtns="http://www.w3.org/2001/XMLSchema"   parameter qname="pns:reqData" xmlns:pns="http://test.com/ejb/" type="ns:RequestData" xmlns:tns="http://www.w3.org/2001/XMLSchema" /  /operation  parameter name="allowedMethods" value="*"/  beanMapping xmlns:ns="http://ejb.test.com/rd" qname="ns:RequestData" languageSpecificType="java:com.test.ejb.rd.RequestData"/ /service/deployment---public class RequestData implements java.io.Serializable{private String x;private String y;private int num;public void setX(String x)
this.x = x;public void setY(String y) this.y = y;public void setNum(String n) this.num = n;public String getX(){ return x;}public String getY(){  return y;}public int getNum{return num;}}If you see something wrong please tell me...Anne Thomas Manes [EMAIL PROTECTED] έγραψε: I think you need to use a beanmapping element rather than a typemapping element.If that doesn't work, please post more information.AnneOn 5/25/06,  Roy [EMAIL PROTECTED]
 wrote:Hello all, I have deployed an ejb service with a method that takes as input a complex object (it contains 2 Strings and one int var). When i generate the code in the client with WSDL2Java and call the method i can see that this complex type object becomes null. I can see in the monitor that the request object isn't null but in the debug mode i can see that the service receives a null object. This problem doesn't occur when I use simple types to transfer. I tried the same code on a non-ejb service and works normally. In the deploy wsdd i use a typemapping element to describe the object and i use the BeanSerializerFactory and BeanDeSerializer factory as serializer-deserializer. Can someone explain why is this happening?Regards,Roy Χρησιμοποιείτε Yahoo!  Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr   
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr

[ADB] Problem with conversion object - OMElement

2006-05-26 Thread vandenberget


Hi,

I'm trying to convert an object to an
OMElement, as described in the ADB Howto (http://ws.apache.org/axis2/1_0/adb/adb-howto.html).

In fact, I'm doing exactly the same
as in the code snippets in the howto -- using the same xml and code examples.
I'm hitting a problem when I have created the OMElement using the StAXOMBuilder:
the OMElement that is produced is *not* the top-level myElement
element, but one of the sub-elements varString.

I had to change both the XSD and the
XML a bit in order to get the example correct and working:

schema
xmlns=http://www.w3.org/2001/XMLSchema

  
 xmlns:xsd=http://www.w3.org/2001/XMLSchema
  
 xmlns:tns=http://soapinterop.org/types
  
 targetNamespace=http://soapinterop.org/types
  
 elementFormDefault=qualified
complexType
name=SOAPStruct
 sequence
 element
name=varString
type=xsd:string/
 element
name=varInt
type=xsd:int/
 element
name=varFloat
type=xsd:float/
 /sequence
 attribute
name=foo/
/complexType
element
name=myElement
type=tns:SOAPStruct/
/schema

myElement
  
 xmlns=http://soapinterop.org/types
  
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance

  
 xsi:schemaLocation=http://soapinterop.org/types
test.xsd
  
 foo=bar
 varStringHello/varString
 varInt5/varInt
 varFloat3.3/varFloat
/myElement

I have added a foo attribute to the
toplevel element to further illustrate the problem.

I have pushed the xsd through XSD2Java,
resulting in MyElement.java and SOAPStruct.java.
The first problem is that the foo attribute
is not modeled anywhere in these two classes.

The following code reads the xml file,
parses it to a MyElement instance, and then creates an OMElement of it,
just as in the howto:

XMLStreamReader
reader = XMLInputFactory.newInstance().

   createXMLStreamReader(new FileReader(test.xml));
MyElement
elt = MyElement.Factory.parse(reader);
XMLStreamReader
r = elt.getPullParser(null);
OMElement
omElt = new StAXOMBuilder(r).getDocumentElement();
System.out.println(omElt);

The output reads
varString
xmlns=http://soapinterop.org/typesHello/varString

What I expect to see (and actually need)
is the full xml - not just the first sub element. 

Is the shown behaviour normal? If so,
what do I need to do to get an OMElement that represents the full xml document?

Thanks,
Tom

Re: Complex type problem

2006-05-26 Thread robert lazarski

You're trying to use a non-ejb client to connect to a Web Service that
implements implements SessionBean, is that correct? The only way I got
that to work - using jboss - was something like...

// remote ejb / web service
private CallCentreWebEndpoint endpoint;

String wsdl_loc = http://localhost:8080/CallCentreWebServiceJAR?wsdl;

// generated by JSWDP wscompile, which jboss insists on using
 URL
mappinglocation =
ClassLoader.getSystemResource(CallCentreWeb_Mapping.xml);
 assertNotNull(mappinglocation);
 // bean mapping
 URL
ws4eeMetaData = ClassLoader.getSystemResource(ws4ee-deploy.xml);
 assertNotNull(ws4eeMetaData);

 QName qname = new QName(http://localhost/callcentreweb,
 CallCentreWebService);
 URL url ="" new URL(wsdl_loc);


org.jboss.webservice.client.ServiceFactoryImpl factory=
(org.jboss.webservice.client.ServiceFactoryImpl)
ServiceFactoryImpl.newInstance();

javax.xml.rpc.Service service = factory.createService(url,
mappinglocation, ws4eeMetaData, qname, null);

endpoint = (CallCentreWebEndpoint)
service.getPort(CallCentreWebEndpoint.class);

The main idea here is ServiceFactoryImpl, which varies by vendor. This
may not be your problem, but thought I'd post it in case it helps. 

HTH,
Robert
http://www.braziloutsource.com/On 5/26/06, Roy [EMAIL PROTECTED]
 wrote:I tried the beanmapping too but it didn't work. This is the the complex type i want to send and the 
deploy.wsdd file:Deploy.wsdd:deployment xmlns=http://xml.apache.org/axis/wsdd/
 xmlns:java=http://xml.apache.org/axis/wsdd/providers/java service name=EJBTestService provider=java:EJB
  parameter name=wsdlTargetNamespace value=http://ejb.test.com/  parameter name=beanJndiName value=ejb/TestService/
  parameter name=homeInterfaceName value=com.test.ejb.TestServiceHome/  parameter name=remoteInterfaceName value=com.test.ejb.TestService/
  parameter name=allowedMethods value=*/  operation name=sendData
 qname=operNS:SendData xmlns:operNS=http://test.com/ejb/ returnQName=retNS:Result xmlns:retNS=
http://test.com/ejb/ returnType=rtns:int xmlns:rtns=
http://www.w3.org/2001/XMLSchema   parameter qname=pns:reqData xmlns:pns=
http://test.com/ejb/ type=ns:RequestData xmlns:tns=http://www.w3.org/2001/XMLSchema
 /  /operation  parameter name=allowedMethods value=*/  beanMapping xmlns:ns=
http://ejb.test.com/rd qname=ns:RequestData languageSpecificType=java:com.test.ejb.rd.RequestData/ /service/deployment---public class RequestData implements 
java.io.Serializable{private String x;private String y;private int num;public void setX(String x)
this.x = x;public void setY(String y) this.y = y;public void setNum(String n) this.num = n;public String getX(){ return x;}public String getY(){
  return y;}public int getNum{return num;}}If you see something wrong please tell me...Anne Thomas Manes 
[EMAIL PROTECTED] έγραψε: I think you need to use a beanmapping element rather than a typemapping element.
If that doesn't work, please post more information.AnneOn 5/25/06,  Roy 
[EMAIL PROTECTED]
 wrote:Hello all, I
have deployed an ejb service with a method that takes as input a
complex object (it contains 2 Strings and one int var). When i generate
the code in the client with WSDL2Java and call the method i can see
that this complex type object becomes null. I can see in the monitor
that the request object isn't null but in the debug mode i can see that
the service receives a null object. This problem doesn't occur when I
use simple types to transfer. I tried the same code on a non-ejb service and works normally. In
the deploy wsdd i use a typemapping element to describe the object and
i use the BeanSerializerFactory and BeanDeSerializer factory as
serializer-deserializer. Can someone explain why is this happening?Regards,Roy Χρησιμοποιείτε Yahoo!

Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την
καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr
   
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr

Re: Axis2: REST-Style with HTTP-GET - how to add parameters?

2006-05-26 Thread Christoph Miksovic

Thank you for your help!
But how can I configure Axis2 to generate a WSDL that does have a GET
binding?

Thank you very much.
Cheers,
Christoph



   
 Anne Thomas  
 Manes
 [EMAIL PROTECTED]  To
 maxis-user@ws.apache.org 
cc
 19.05.2006 21:44  
   Subject
   Re: Axis2: REST-Style with HTTP-GET
 Please respond to - how to add parameters?
 axis-user 
   
   
   
   
   




Your WSDL doesn't have a GET binding (just POST).

On 5/18/06, Christoph Miksovic [EMAIL PROTECTED]  wrote:
  Hello everybody,

  I have problems acessing the Axis2SampleDocLitService Sample using
  REST-Style with HTTP-GET.
  Can you please tell me what is the correct way to set the parameter?

  The operation signature is echoString(String echoStringParam) (see WSDL
  File below).

  I tried several things like for instance

  
http://localhost:8080/axis2/rest/Axis2SampleDocLitService/echoString?echoStringParam=hello


  But I always get an error as follows:
  org.apache.axis2.AxisFault: Data binding error; nested exception is:
java.lang.RuntimeException: Data binding error; nested exception
  is:
org.apache.axis2.AxisFault: Data binding error; nested exception
  is:
java.lang.RuntimeException: Data binding error

  
org.apache.axis2.transport.http.util.RESTUtil.processGetRequest(RESTUtil.java:141)


  org.apache.axis2.transport.http.AxisRESTServlet.doGet(AxisRESTServlet.java
 :36)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)


  Thanks a lot for any help!
  Cheers,
  Christoph


  
_

  WSDL File, generated by Axis2 Engine:
  wsdl:definitions targetNamespace=
  http://userguide.axis2.apache.org/Axis2SampleDocLit;
  -
wsdl:types
  -
schema targetNamespace=http://userguide.axis2.apache.org/xsd;
  elementFormDefault=qualified attributeFormDefault=unqualified
  -
complexType name=ArrayOfstring_literal
  -
sequence
  element type=string name=string maxOccurs=unbounded/
  /sequence
  /complexType
  -
complexType name=SOAPStruct
  -
all
  element type=float name=varFloat/
  element type=int name=varInt/
  element type=string name=varString/
  /all
  /complexType
  element type=string name=echoStringParam/
  element type=int name=echoIntParam/
  element type=string name=echoStringReturn/
  element type=xsd1:ArrayOfstring_literal name=echoStringArrayParam/
  element type=xsd1:ArrayOfstring_literal name=echoStringArrayReturn/

  element type=xsd1:SOAPStruct name=echoStructParam/
  element type=xsd1:SOAPStruct name=echoStructReturn/
  /schema
  /wsdl:types
  -
wsdl:message name=echoStringArray
  wsdl:part element=xsd1:echoStringArrayParam name=part1/
  /wsdl:message
  -
wsdl:message name=echoStringArrayResponse
  wsdl:part element=xsd1:echoStringArrayReturn name=part1/
  /wsdl:message
  -
wsdl:message name=echoString
  wsdl:part element=xsd1:echoStringParam name=part1/
  /wsdl:message
  -
wsdl:message name=echoStringResponse
  wsdl:part element=xsd1:echoStringReturn name=part1/
  /wsdl:message
  -
wsdl:message name=echoStruct
  wsdl:part element=xsd1:echoStructParam name=part1/
  /wsdl:message
  -
wsdl:message name=echoStructResponse
  wsdl:part element=xsd1:echoStructReturn name=part1/
  /wsdl:message
  -
wsdl:portType name=Axis2SampleDocLitServicePortType
  -
wsdl:operation name=echoStringArray
  wsdl:input message=tns:echoStringArray/
  wsdl:output message=tns:echoStringArrayResponse/
  /wsdl:operation
  -
wsdl:operation name=echoString
  wsdl:input message=tns:echoString/
  wsdl:output message=tns:echoStringResponse/
  /wsdl:operation
  -
wsdl:operation name=echoStruct
  wsdl:input message=tns:echoStruct/
  wsdl:output message=tns:echoStructResponse/
  /wsdl:operation
  /wsdl:portType
  -
wsdl:binding type=tns:Axis2SampleDocLitServicePortType
  name=Axis2SampleDocLitServiceSOAP11Binding

Re: Complex type problem

2006-05-26 Thread Roy

I think that this is not exactly my problem. I can call normally the service from my client when i use simple types. When i try to pass complex types i face the problem.robert lazarski [EMAIL PROTECTED] έγραψε: You're trying to use a non-ejb client to connect to a Web Service that implements implements SessionBean, is that correct? The only way I got that to work - using jboss - was something like...  // remote ejb / web service private CallCentreWebEndpoint endpoint;  String wsdl_loc = "http://localhost:8080/CallCentreWebServiceJAR?wsdl";  // generated by JSWDP wscompile, which jboss insists on using
  URL mappinglocation = ClassLoader.getSystemResource("CallCentreWeb_Mapping.xml");  assertNotNull(mappinglocation);  // bean mapping  URL ws4eeMetaData = ClassLoader.getSystemResource("ws4ee-deploy.xml");  assertNotNull(ws4eeMetaData);   QName qname = new QName("http://localhost/callcentreweb",  "CallCentreWebService");  URL url ="" new URL(wsdl_loc); 
  org.jboss.webservice.client.ServiceFactoryImpl factory= (org.jboss.webservice.client.ServiceFactoryImpl) ServiceFactoryImpl.newInstance();  javax.xml.rpc.Service service = factory.createService(url, mappinglocation, ws4eeMetaData, qname, null);  endpoint = (CallCentreWebEndpoint) service.getPort(CallCentreWebEndpoint.class);  The main idea here is ServiceFactoryImpl, which varies by vendor. This may not be your problem, but thought I'd post it in case it helps.   HTH, Robert http://www.braziloutsource.com/On 5/26/06, Roy [EMAIL PROTECTED]  wrote:I tried the beanmapping too but it didn't work. This is the the complex type i want to send and the  deploy.wsdd file:Deploy.wsdd:deployment xmlns="http://xml.apache.org/axis/wsdd/ " xmlns:java="http://xml.apache.org/axis/wsdd/providers/java" service name="EJBTestService" provider="java:EJB"   parameter name="wsdlTargetNamespace" value="http://ejb.test.com"/ 
 parameter name="beanJndiName" value="ejb/TestService"/   parameter name="homeInterfaceName" value="com.test.ejb.TestServiceHome"/  parameter name="remoteInterfaceName" value="com.test.ejb.TestService"/   parameter name="allowedMethods" value="*"/  operation name="sendData"  qname="operNS:SendData" xmlns:operNS="http://test.com/ejb/" returnQName="retNS:Result" xmlns:retNS=" http://test.com/ejb/" returnType="rtns:int" xmlns:rtns="
 http://www.w3.org/2001/XMLSchema"   parameter qname="pns:reqData" xmlns:pns=" http://test.com/ejb/" type="ns:RequestData" xmlns:tns="http://www.w3.org/2001/XMLSchema " /  /operation  parameter name="allowedMethods" value="*"/  beanMapping xmlns:ns=" http://ejb.test.com/rd" qname="ns:RequestData" languageSpecificType="java:com.test.ejb.rd.RequestData"/
 /service/deployment---public class RequestData implements  java.io.Serializable{private String x;private String y;private int num;public void setX(String x) this.x = x;public void setY(String y) this.y = y;public void setNum(String n) this.num = n;public String getX(){ return x;}public String getY(){   return y;}public int getNum{return num;}}If you see something wrong please tell me...Anne Thomas Manes  [EMAIL PROTECTED] έγραψε: I think you need to use a beanmapping element rather than a typemapping element. If that doesn't work, please post more information.AnneOn 5/25/06,  Roy  [EMAIL PROTECTED]  wrote:Hello all, I have deployed an ejb service with a method that takes as input a complex object (it contains 2 Strings and one int var). When i generate the code in the client with WSDL2Java and call the method i can see that this complex type object becomes null. I can see in the monitor that the request object isn't null but in the debug mode i can see that the service
 receives a null object. This problem doesn't occur when I use simple types to transfer. I tried the same code on a non-ejb service and works normally. In the deploy wsdd i use a typemapping element to describe the object and i use the BeanSerializerFactory and BeanDeSerializer factory as serializer-deserializer. Can someone explain why is this happening?Regards,Roy Χρησιμοποιείτε Yahoo!  Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr Χρησιμοποιείτε Yahoo!  Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr   
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr

Re: Complex type problem

2006-05-26 Thread robert lazarski

The other thing is make sure your vendor supports wsdl2java - jboss
does not, for example (although they run a modified version of axis 1.2
internally). The problem I had was similair, although IIRC correctly I
was getting ser / deser errors, not null. It was working on simple
types but failing on complex ones. 

HTH,
Robert
http://www.braziloutsource.com/On 5/26/06, Roy [EMAIL PROTECTED]
 wrote:I think that this is not exactly my problem. I can call normally
the service from my client when i use simple types. When i try to pass
complex types i face the problem.robert lazarski [EMAIL PROTECTED]
 έγραψε:
You're trying to use a non-ejb client to connect to a Web Service that
implements implements SessionBean, is that correct? The only way I got
that to work - using jboss - was something like...  // remote ejb / web service private CallCentreWebEndpoint endpoint;  String wsdl_loc = 
http://localhost:8080/CallCentreWebServiceJAR?wsdl;

// generated by JSWDP wscompile, which jboss insists on using
 URL
mappinglocation =
ClassLoader.getSystemResource(CallCentreWeb_Mapping.xml);  assertNotNull(mappinglocation);  // bean mapping
 URL
ws4eeMetaData = ClassLoader.getSystemResource(ws4ee-deploy.xml);  assertNotNull(ws4eeMetaData);   QName qname = new QName(
http://localhost/callcentreweb,  CallCentreWebService);  URL url ="" new URL(wsdl_loc); 
  org.jboss.webservice.client.ServiceFactoryImpl factory= (org.jboss.webservice.client.ServiceFactoryImpl) ServiceFactoryImpl.newInstance();

javax.xml.rpc.Service service = factory.createService(url,
mappinglocation, ws4eeMetaData, qname, null);

endpoint = (CallCentreWebEndpoint)
service.getPort(CallCentreWebEndpoint.class);  The main idea
here is ServiceFactoryImpl, which varies by vendor. This may not be
your problem, but thought I'd post it in case it helps.   HTH, Robert http://www.braziloutsource.com/
On 5/26/06, Roy [EMAIL PROTECTED] 
 wrote:I tried the beanmapping too but it didn't work. This is the the complex type i want to send and the  
deploy.wsdd file:Deploy.wsdd:deployment xmlns=http://xml.apache.org/axis/wsdd/
  xmlns:java=http://xml.apache.org/axis/wsdd/providers/java service name=EJBTestService provider=java:EJB 
  parameter name=wsdlTargetNamespace value=http://ejb.test.com/ 
 parameter name=beanJndiName value=ejb/TestService/   parameter name=homeInterfaceName value=com.test.ejb.TestServiceHome/  parameter name=remoteInterfaceName value=
com.test.ejb.TestService/   parameter name=allowedMethods value=*/  operation name=sendData  qname=operNS:SendData xmlns:operNS=
http://test.com/ejb/ returnQName=retNS:Result xmlns:retNS= 
http://test.com/ejb/ returnType=rtns:int xmlns:rtns=
 http://www.w3.org/2001/XMLSchema   parameter qname=pns:reqData xmlns:pns=
 http://test.com/ejb/ type=ns:RequestData xmlns:tns=http://www.w3.org/2001/XMLSchema 
 /  /operation  parameter name=allowedMethods value=*/  beanMapping xmlns:ns=
 http://ejb.test.com/rd qname=ns:RequestData languageSpecificType=java:com.test.ejb.rd.RequestData/
 /service/deployment---public class RequestData implements  java.io.Serializable{private String x;private String y;private int num;public void setX(String x)
 this.x = x;public void setY(String y) this.y = y;public void setNum(String n) this.num = n;public String getX(){ return x;}public String getY(){
   return y;}public int getNum{return num;}}If you see something wrong please tell me...Anne Thomas Manes 
 [EMAIL PROTECTED] έγραψε: I think you need to use a beanmapping element rather than a typemapping element. 
If that doesn't work, please post more information.AnneOn 5/25/06,  Roy 
 [EMAIL PROTECTED]  wrote:Hello all, I
have deployed an ejb service with a method that takes as input a
complex object (it contains 2 Strings and one int var). When i generate
the code in the client with WSDL2Java and call the method i can see
that this complex type object becomes null. I can see in the monitor
that the request object isn't null but in the debug mode i can see that
the service receives a null object. This problem doesn't occur when I
use simple types to transfer. I tried the same code on a non-ejb service and works normally. In
the deploy wsdd i use a typemapping element to describe the object and
i use the BeanSerializerFactory and BeanDeSerializer factory as
serializer-deserializer. Can someone explain why is this happening?Regards,Roy Χρησιμοποιείτε Yahoo! 

Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την
καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr 
Χρησιμοποιείτε Yahoo!
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την
καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων   http://login.yahoo.com/config/mail?.intl=gr
   
		 
Χρησιμοποιείτε Yahoo! 
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων  
http://login.yahoo.com/config/mail?.intl=gr

RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type

Has no-one ever run into this problem? This in reference to Axis2.

Thanks,
Ozzie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Thursday, May 25, 2006 1:32 PM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The WSDL operation:

wsdl:operation name=Update_MemberPCPDetail
soap:operation
soapAction=urn:ProviderService/
wsdl:input
soap:header
message=tns:Update_MemberPCPDetail_Request part=context
use=literal/
soap:header
message=tns:Update_MemberPCPDetail_Request part=header
use=literal/
soap:body parts=request
use=literal/
/wsdl:input
wsdl:output
soap:header
message=tns:Update_MemberPCPDetail_Response part=context
use=literal/
soap:body parts=response
use=literal/
/wsdl:output
wsdl:fault name=ESBError
soap:fault name=ESBError
use=literal/
/wsdl:fault
/wsdl:operation

The Message definitions:

wsdl:message name=Update_MemberPCPDetail_Request
wsdl:part name=context element=c:Context/
wsdl:part name=header element=h:ESBHeader/
wsdl:part name=request
element=m:ProviderService_Update_MemberPCPDetail_Request/
/wsdl:message
wsdl:message name=Update_MemberPCPDetail_Response
wsdl:part name=context element=c:Context/
wsdl:part name=response
element=m:ProviderService_Update_MemberPCPDetail_Response/
wsdl:part name=exception element=e:ExceptionList/
/wsdl:message

Why isn't the parameter in the method of type
com.wellpoint.service.provider.
ProviderServiceUpdateMemberPCPDetailRequestDocument

It is org.apache.axiom.om.OMElement.

What am I doing wrong This is a doc/lit.

Thanks,
Ozzie

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Wednesday, May 24, 2006 10:07 AM
To: axis-user@ws.apache.org
Subject: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The generated stub source doesn't contain the correct parameter type in
the service method. Instead of having the specific type as specified in
the WSDL for the parameter, it contains the generic
org.apache.axiom.om.OMElement type. 

The stub was generated using Axis2 1.0 WSDL2Java tool.

D:\dev\wellpoint\SAF\wsdl\ProviderDomaind:\devtools\axis2-SNAPSHOT\bin\
WSDL2Java.bat -uri ProviderService_Binding_JMS_V0100.wsdl -s -o codegen
-d xmlbeans -p com.wellpoint.integration.saf.int.provider.axis2

   /**
* Auto generated method signature
* @see
com.wellpoint.integration.saf.int.provider.axis2.ProviderService#UpdateM
emberPCPDetail
* @param param0

* @param param1

* @param param2

*/
public org.apache.axiom.om.OMElement
UpdateMemberPCPDetail(
org.apache.axiom.om.OMElement
param0,com.wellpoint.esb.context.ContextDocument
param1,com.wellpoint.esb.header.ESBHeaderDocument param2)

The first parameter should have been
com.wellpoint.service.provider.ProviderUpdateMemberPCPDetailRequestDocu
ment.

JIRA Issue: http://issues.apache.org/jira/browse/AXIS2-765

Thanks,
Ozgur (Ozzie) Gurkan
Wellpoint Member 2 - SAF Team

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.

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

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.

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

This message is for the designated recipient only and may contain privileged, 
proprietary, or otherwise private information.  If you have received it in 
error, please notify the sender immediately and delete the original.  Any other 
use of the email by you is prohibited.

where is this site maintained now?

2006-05-26 Thread Amjad Abu Zur - TusAlas











Hi all:



I need to make the compression with the old version
of axis. At the final part of this site



http://wiki.apache.org/ws/FrontPage/Axis/GzipCompression





there is a reference to the following one:





http://www.osmoticweb.com/axis-soap-compression.htm





But this site never works. Do you know where it is
maintained now?



Thanks in advance








 
  
  
  
  Mohamed Abu Zur___ 
  Browser
  System
  S.L.
  [www.tusalas.com]
  Departamento
  de Desarrollo e Informática
  
  
  TEL: +34 91 4750242 @mail: mabuzur@tusalas.com
  C/ Cristo de la
  victoria nº 102 - 104 ::: Madrid - España

How do I get wsdl2java to include code in generated stub for custom serializers/deserializers?

2006-05-26 Thread Ryan Norris


 I have written a custom serializer and deserializer and I would like the stub 
 that is generated from wsdl2java to register them for one of my objects.  The 
 generated stub's constructor contains code that registers Axis' serializers 
 and deserializers, however, I can't figure out how to get the task to 
 generate code for my custom serializer/deserializer.   Can someone help me 
 figure out if this is possible, and if so how I might be able to do it?
 
 I can specify my custom mappings with the java2wsdl task using the 
 complextype.  For ex:
 
 complextype classname=my.thingy.MyThingy namespace=http://thingy.my; 
 serializer=my.ser.MySerializerFactory 
 deserializer=my.ser.MyDeserializerFactory/
 
 I don't see an equivalent for wsdl2java.
 
 I am using Axis 1.2.1 and the ant tasks to generate the stubs.
 
 Thanks,
 -Ryan
 
 

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

new connection for every call! Keep-alive?

2006-05-26 Thread Morten Steffensen


Hello happy axis users,

How do I prevent axis2 client from making a new connection for every call?

I have built a client app based on the axis2 v1.0. The client is built 
like the EchoBlockingClient userguide sample. It seems that every call 
is done by a opening a new connection to the server. There doesn't seem 
to be any Keep-alive property in the http header. I have searched in the 
documentation and in the source code for a hook to switch Keep-alive on, 
but did not succeed. So I just added a setRequestHeader into the 
SOAPOverHttpSender.java. Now I get the Keep-alive in the http header, 
but it still seems that a new connection is opened for each call.


Please, help me with a hint on how to reuse connections.

--
Med venlig hilsen / Kind regards,
Morten Steffensen

Emercos ApS
http://www.emercos.com


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

[Axis2] setOperationContext() question

2006-05-26 Thread Michele Mazzucco

Hi all,

is it possible to get the same result with outgoing messages as well by
using the setOperationContext() (it seems to me that the

outMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

into the setOperationContext() doesn't work as espected
)?

If no, is there any way to add some headers to outgoing messages?

Thanks in advance,
Michele

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

Re: REPOST FOR HELP: Axis client logging from web applet causes security error

Nevermind. I found the latest build, used it and it works perfectly.- Original Message From: ANTHONY ZIOLKOWSKI [EMAIL PROTECTED]To: [EMAIL PROTECTED]; axis-user@ws.apache.orgCc: robert lazarski [EMAIL PROTECTED]Sent: Friday, May 26, 2006 7:31:01 AMSubject: Re: REPOST FOR HELP: Axis client logging from web applet causes security errorI'm sorry. I do not know how to do that.- Original Message From: Davanum Srinivas
 [EMAIL PROTECTED]To: axis-user@ws.apache.org; ANTHONY ZIOLKOWSKI [EMAIL PROTECTED]Cc: robert lazarski [EMAIL PROTECTED]Sent: Thursday, May 25, 2006 10:40:47 PMSubject: Re: REPOST FOR HELP: Axis client logging from web applet causes security errorPlease check the archives...you need a fresh jar of commons-discoverybuilt from the SVN sources for discovery.thanks,dimsOn 5/25/06, ANTHONY ZIOLKOWSKI [EMAIL PROTECTED] wrote: I moved to axis 1.4 and the problem went away. Unfortunately to be replaced by another
 problem. My console client stub still works fine. Running under firefox i get the following message in the Java Console window: Failure trying to get the Call object; nested exception is: java.lang.NoClassDefFoundError That's it, no stack trace, nothing in the Tomcat logs When I run under IE6 I get the following error and stack trace: Exception in thread "AWT-EventQueue-2" java.lang.ExceptionInInitializerError at org.apache.commons.discovery.jdk.JDKHooks.clinit(JDKHooks.java:75) at org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:412) at org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:378) at
 org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45) at java.security.AccessController.doPrivileged(Native Method) at org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41) at org.apache.axis.components.logger.LogFactory.clinit(LogFactory.java:33) at org.apache.axis.handlers.BasicHandler.clinit(BasicHandler.java:43) at org.apache.axis.client.Service.getAxisClient(Service.java:104) at org.apache.axis.client.Service.init(Service.java:113) at com.zeesol.bizservice.client.BizService_ServiceLocator.init(BizService_ServiceLocator.java:12) at
 com.mazuma.applets.BaseRunner$1.actionPerformed(BaseRunner.java:156) at javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at javax.swing.DefaultButtonModel.setPressed(Unknown Source) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at
 java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at
 java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Caused by: java.security.AccessControlException: access denied (java.lang.RuntimePermission createClassLoader) at java.security.AccessControlContext.checkPermission(Unknown Source) at java.security.AccessController.checkPermission(Unknown Source) at java.lang.SecurityManager.checkPermission(Unknown Source) at
 java.lang.SecurityManager.checkCreateClassLoader(Unknown Source) at java.lang.ClassLoader.init(Unknown Source) at org.apache.commons.discovery.jdk.PsuedoSystemClassLoader.init(PsuedoSystemClassLoader.java:73) at org.apache.commons.discovery.jdk.JDK12Hooks.findSystemClassLoader(JDK12Hooks.java:215) at org.apache.commons.discovery.jdk.JDK12Hooks.clinit(JDK12Hooks.java:73) ... 35 more - Original Message  From: robert lazarski [EMAIL PROTECTED] To: axis-user@ws.apache.org; ANTHONY ZIOLKOWSKI [EMAIL PROTECTED] Sent: Monday, May 8, 2006 8:36:16 AM Subject: Re: REPOST FOR HELP: Axis client logging from web applet causes security error I suspect this is primarily a
 log4j / commons-logging issue. Try editing the propertiesof each and comment out the file appenders. Or simply enable log4j based logging in the commons property file, and use your own log4j.properties file instead of the one that comes with axis. I'm enclosing my log4j.properties file that should do just that (I removed the file appender,

RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type

2006-05-26 Thread Suyog Gandhi

I have created the stub in a same way u creating, and it is creating
proper stubs for me. But I didn't use -s option. Also I am using
WSDL2Java from AXIS2 1.0 release version, not a snapshot.

Hoep it helps.
Suyog

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 9:48 AM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type


Has no-one ever run into this problem? This in reference to Axis2.

Thanks,
Ozzie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Thursday, May 25, 2006 1:32 PM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The WSDL operation:

wsdl:operation name=Update_MemberPCPDetail
soap:operation
soapAction=urn:ProviderService/
wsdl:input
soap:header
message=tns:Update_MemberPCPDetail_Request part=context
use=literal/
soap:header
message=tns:Update_MemberPCPDetail_Request part=header
use=literal/
soap:body parts=request
use=literal/
/wsdl:input
wsdl:output
soap:header
message=tns:Update_MemberPCPDetail_Response part=context
use=literal/
soap:body parts=response
use=literal/
/wsdl:output
wsdl:fault name=ESBError
soap:fault name=ESBError
use=literal/
/wsdl:fault
/wsdl:operation

The Message definitions:

wsdl:message name=Update_MemberPCPDetail_Request
wsdl:part name=context element=c:Context/
wsdl:part name=header element=h:ESBHeader/
wsdl:part name=request
element=m:ProviderService_Update_MemberPCPDetail_Request/
/wsdl:message
wsdl:message name=Update_MemberPCPDetail_Response
wsdl:part name=context element=c:Context/
wsdl:part name=response
element=m:ProviderService_Update_MemberPCPDetail_Response/
wsdl:part name=exception element=e:ExceptionList/
/wsdl:message

Why isn't the parameter in the method of type
com.wellpoint.service.provider.
ProviderServiceUpdateMemberPCPDetailRequestDocument

It is org.apache.axiom.om.OMElement.

What am I doing wrong This is a doc/lit.


Thanks,
Ozzie

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Wednesday, May 24, 2006 10:07 AM
To: axis-user@ws.apache.org
Subject: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The generated stub source doesn't contain the correct parameter type in
the service method. Instead of having the specific type as specified in
the WSDL for the parameter, it contains the generic
org.apache.axiom.om.OMElement type.

The stub was generated using Axis2 1.0 WSDL2Java tool.

D:\dev\wellpoint\SAF\wsdl\ProviderDomaind:\devtools\axis2-SNAPSHOT\bin\
WSDL2Java.bat -uri ProviderService_Binding_JMS_V0100.wsdl -s -o codegen
-d xmlbeans -p com.wellpoint.integration.saf.int.provider.axis2

   /**
* Auto generated method signature
* @see
com.wellpoint.integration.saf.int.provider.axis2.ProviderService#UpdateM
emberPCPDetail
* @param param0

* @param param1

* @param param2

*/
public org.apache.axiom.om.OMElement
UpdateMemberPCPDetail(
org.apache.axiom.om.OMElement
param0,com.wellpoint.esb.context.ContextDocument
param1,com.wellpoint.esb.header.ESBHeaderDocument param2)


The first parameter should have been
com.wellpoint.service.provider.ProviderUpdateMemberPCPDetailRequestDocu
ment.


JIRA Issue: http://issues.apache.org/jira/browse/AXIS2-765

Thanks,
Ozgur (Ozzie) Gurkan
Wellpoint Member 2 - SAF Team



This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.

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



This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.

-
To unsubscribe, e-mail: [EMAIL

RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type

I tried with 1.0, too. I will try with -s option to see if the parameter
is getting added. Have you tried with my zip contents?

Thanks,
Ozzie

-Original Message-
From: Suyog Gandhi [mailto:[EMAIL PROTECTED] 
Sent: Friday, May 26, 2006 10:44 AM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

I have created the stub in a same way u creating, and it is creating
proper stubs for me. But I didn't use -s option. Also I am using
WSDL2Java from AXIS2 1.0 release version, not a snapshot. 

Hoep it helps.
Suyog

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 9:48 AM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

Has no-one ever run into this problem? This in reference to Axis2.

Thanks,
Ozzie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Thursday, May 25, 2006 1:32 PM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The WSDL operation:

wsdl:operation name=Update_MemberPCPDetail
soap:operation
soapAction=urn:ProviderService/
wsdl:input
soap:header
message=tns:Update_MemberPCPDetail_Request part=context
use=literal/
soap:header
message=tns:Update_MemberPCPDetail_Request part=header
use=literal/
soap:body parts=request
use=literal/
/wsdl:input
wsdl:output
soap:header
message=tns:Update_MemberPCPDetail_Response part=context
use=literal/
soap:body parts=response
use=literal/
/wsdl:output
wsdl:fault name=ESBError
soap:fault name=ESBError
use=literal/
/wsdl:fault
/wsdl:operation

The Message definitions:

wsdl:message name=Update_MemberPCPDetail_Request
wsdl:part name=context element=c:Context/
wsdl:part name=header element=h:ESBHeader/
wsdl:part name=request
element=m:ProviderService_Update_MemberPCPDetail_Request/
/wsdl:message
wsdl:message name=Update_MemberPCPDetail_Response
wsdl:part name=context element=c:Context/
wsdl:part name=response
element=m:ProviderService_Update_MemberPCPDetail_Response/
wsdl:part name=exception element=e:ExceptionList/
/wsdl:message

Why isn't the parameter in the method of type
com.wellpoint.service.provider.
ProviderServiceUpdateMemberPCPDetailRequestDocument

It is org.apache.axiom.om.OMElement.

What am I doing wrong This is a doc/lit.

Thanks,
Ozzie

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Wednesday, May 24, 2006 10:07 AM
To: axis-user@ws.apache.org
Subject: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The generated stub source doesn't contain the correct parameter type in
the service method. Instead of having the specific type as specified in
the WSDL for the parameter, it contains the generic
org.apache.axiom.om.OMElement type. 

The stub was generated using Axis2 1.0 WSDL2Java tool.

D:\dev\wellpoint\SAF\wsdl\ProviderDomaind:\devtools\axis2-SNAPSHOT\bin\
WSDL2Java.bat -uri ProviderService_Binding_JMS_V0100.wsdl -s -o codegen
-d xmlbeans -p com.wellpoint.integration.saf.int.provider.axis2

   /**
* Auto generated method signature
* @see
com.wellpoint.integration.saf.int.provider.axis2.ProviderService#UpdateM
emberPCPDetail
* @param param0

* @param param1

* @param param2

*/
public org.apache.axiom.om.OMElement
UpdateMemberPCPDetail(
org.apache.axiom.om.OMElement
param0,com.wellpoint.esb.context.ContextDocument
param1,com.wellpoint.esb.header.ESBHeaderDocument param2)

The first parameter should have been
com.wellpoint.service.provider.ProviderUpdateMemberPCPDetailRequestDocu
ment.

JIRA Issue: http://issues.apache.org/jira/browse/AXIS2-765

Thanks,
Ozgur (Ozzie) Gurkan
Wellpoint Member 2 - SAF Team

This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information.  If you have
received it in error, please notify the sender immediately and delete
the original.  Any other use of the email by you is prohibited.

-
To unsubscribe,

RE: Incorrect parameter type in WSDL2Java generated stub method OMElement instead of specific type

2006-05-26 Thread Suyog Gandhi

No I didnot try your zip, .. I just crosschecked with my running
code.


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 10:45 AM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type


I tried with 1.0, too. I will try with -s option to see if the parameter
is getting added. Have you tried with my zip contents?

Thanks,
Ozzie

-Original Message-
From: Suyog Gandhi [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 10:44 AM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

I have created the stub in a same way u creating, and it is creating
proper stubs for me. But I didn't use -s option. Also I am using
WSDL2Java from AXIS2 1.0 release version, not a snapshot.

Hoep it helps.
Suyog

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 9:48 AM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type


Has no-one ever run into this problem? This in reference to Axis2.

Thanks,
Ozzie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Thursday, May 25, 2006 1:32 PM
To: axis-user@ws.apache.org
Subject: RE: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The WSDL operation:

wsdl:operation name=Update_MemberPCPDetail
soap:operation
soapAction=urn:ProviderService/
wsdl:input
soap:header
message=tns:Update_MemberPCPDetail_Request part=context
use=literal/
soap:header
message=tns:Update_MemberPCPDetail_Request part=header
use=literal/
soap:body parts=request
use=literal/
/wsdl:input
wsdl:output
soap:header
message=tns:Update_MemberPCPDetail_Response part=context
use=literal/
soap:body parts=response
use=literal/
/wsdl:output
wsdl:fault name=ESBError
soap:fault name=ESBError
use=literal/
/wsdl:fault
/wsdl:operation

The Message definitions:

wsdl:message name=Update_MemberPCPDetail_Request
wsdl:part name=context element=c:Context/
wsdl:part name=header element=h:ESBHeader/
wsdl:part name=request
element=m:ProviderService_Update_MemberPCPDetail_Request/
/wsdl:message
wsdl:message name=Update_MemberPCPDetail_Response
wsdl:part name=context element=c:Context/
wsdl:part name=response
element=m:ProviderService_Update_MemberPCPDetail_Response/
wsdl:part name=exception element=e:ExceptionList/
/wsdl:message

Why isn't the parameter in the method of type
com.wellpoint.service.provider.
ProviderServiceUpdateMemberPCPDetailRequestDocument

It is org.apache.axiom.om.OMElement.

What am I doing wrong This is a doc/lit.


Thanks,
Ozzie

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Sent: Wednesday, May 24, 2006 10:07 AM
To: axis-user@ws.apache.org
Subject: Incorrect parameter type in WSDL2Java generated stub method
OMElement instead of specific type

The generated stub source doesn't contain the correct parameter type in
the service method. Instead of having the specific type as specified in
the WSDL for the parameter, it contains the generic
org.apache.axiom.om.OMElement type.

The stub was generated using Axis2 1.0 WSDL2Java tool.

D:\dev\wellpoint\SAF\wsdl\ProviderDomaind:\devtools\axis2-SNAPSHOT\bin\
WSDL2Java.bat -uri ProviderService_Binding_JMS_V0100.wsdl -s -o codegen
-d xmlbeans -p com.wellpoint.integration.saf.int.provider.axis2

   /**
* Auto generated method signature
* @see
com.wellpoint.integration.saf.int.provider.axis2.ProviderService#UpdateM
emberPCPDetail
* @param param0

* @param param1

* @param param2

*/
public org.apache.axiom.om.OMElement
UpdateMemberPCPDetail(
org.apache.axiom.om.OMElement
param0,com.wellpoint.esb.context.ContextDocument
param1,com.wellpoint.esb.header.ESBHeaderDocument param2)


The first parameter should have been
com.wellpoint.service.provider.ProviderUpdateMemberPCPDetailRequestDocu
ment.


JIRA Issue: http://issues.apache.org/jira/browse/AXIS2-765

Thanks,
Ozgur (Ozzie) Gurkan
Wellpoint Member 2 - SAF Team



This message is for the designated recipient only and may contain
privileged, proprietary, or

QUESTION: meaning of message - FileProvider - Configuration file read-only so engine configuration changes will not be saved

While running an axis client under in a web browser applet, I get the message - FileProvider - Configuration file read-only so engine configuration changes will not be saved. What does it mean?

Re: [Axis2] setOperationContext() question

2006-05-26 Thread Samisa Abeysinghe


Michele Mazzucco wrote:


Hi all,

is it possible to get the same result with outgoing messages as well by
using the setOperationContext() (it seems to me that the

outMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

into the setOperationContext() doesn't work as espected
)?

If no, is there any way to add some headers to outgoing messages?
 


You can use:
public void addHeader(OMElement header)
of service client to add headers.

HTH.
Samisa...


Thanks in advance,
Michele

-
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]

RE: AXIS2 1.0

2006-05-26 Thread Suyog Gandhi

Created JIRA issue: AXIS2-770.
Let me know if you need more information.

Thanks  Regards,
Suyog

-Original Message-
From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 6:57 AM
To: axis-user@ws.apache.org
Subject: Re: AXIS2 1.0

Hmm , can u pls create a JIRA ,I think this a bug.

Suyog Gandhi wrote:

I am using AXIS2, RPCMessageReceiver.

I am passing following obbject as a parameter in one of my call.

WMemberInfo
   |- ID
   |- WMemberAttribute []
   |- Name
   |- Value
   |- isChanged

 I can get value of ID properly. But I cannot get WMemberAttribute
properly. On SOAP monitor I can see request XML is proper. But I get
null in all the place holders in WMemberAttribute ( i.e Name, value are
null and isChanged is false default value.).

I checked the tracker variables, all the tracker variables are true. (
I
think it means it will serialize the object.)

Anyboyd has any insight on how to tackel this problem. ( Using 25 May
2006 Nightly build).

Thanks  Regards,
Suyog

--
Thanks,
Deepal

~Future is Open~

-
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]

[Axis2] Namespaces with and without security turned on

2006-05-26 Thread Marcus Ludvigson

Hi, 

I am executing awebservice with and without security turned on. The result when executing the WS with security turned on is that I get excessive amount of namespaces (axis2ns23, axis2ns24, axis2ns25, etc) compared to executing without security. I also get a ArrayIndexOutOfBoundsException the first time running with security but it works if I run it again.


Who is generating all of these namespaces, and can I do something to avoid it?

See info below.

Regards, 
Marcus Ludvigson


Result when executing without security:

listAllServicesResponse xmlns=http://corp.net/ConfigManager/listAllServices service secure=false servicename=Program/
 service secure=false servicename=Apps/ service secure=false servicename=ConfigManager/ service secure=false servicename=version/
/listAllServicesResponse



Result when executing with security:

listAllServicesResponse xmlns:axis2ns21=http://corp.net/ConfigManager/listAllServices xmlns:xenc=
http://www.w3.org/2001/04/xmlenc# xmlns:wsa=http://www.w3.org/2005/08/addressing xmlns:wsu=
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd xmlns=http://corp.net/ConfigManager/listAllServices xmlns:soapenv=
http://schemas.xmlsoap.org/soap/envelope/ service secure=false servicename=Program xmlns:axis2ns22=
http://corp.net/ConfigManager/listAllServices/ service secure=false servicename=Apps xmlns:axis2ns23=http://corp.net/ConfigManager/listAllServices/
 service secure=true servicename=ConfigManager xmlns:axis2ns24=http://corp.net/ConfigManager/listAllServices/
/listAllServicesResponse


Relevantpart from the WSDL:

xs:schema targetNamespace=http://corp.net/ConfigManager/listAllServices elementFormDefault=qualifiedxs:element name=listAllServicesResponse
xs:complexTypexs:sequencexs:element name=service maxOccurs=unbounded xs:complexTypexs:attribute name=servicename type=xs:string /
xs:attribute name=secure type=xs:boolean //xs:complexType/xs:element/xs:sequence/xs:complexType/xs:element
/xs:schema


ArrayIndexOutOfBounds:

SymbMap.index(Object) line: not availableSymbMap.get(String) line: not availableNameSpaceSymbTable.addMapping(String, String, Attr) line: not availableCanonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).handleAttributesSubtree(Element, NameSpaceSymbTable) line: not available
Canonicalizer20010315ExclOmitComments(CanonicalizerBase).canonicalizeSubTree(Node, NameSpaceSymbTable, Node) line: not availableCanonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalizeSubTree(Node, Node) line: not available
Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalize(XMLSignatureInput) line: not availableCanonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).engineCanonicalize(XMLSignatureInput, String) line: not available
TransformC14NExclusive.enginePerformTransform(XMLSignatureInput, OutputStream) line: not availableTransform.performTransform(XMLSignatureInput, OutputStream) line: not availableTransforms.performTransforms(XMLSignatureInput, OutputStream) line: not available
Reference.getContentsAfterTransformation(XMLSignatureInput, OutputStream) line: not availableReference.dereferenceURIandPerformTransforms(OutputStream) line: not availableReference.calculateDigest() line: not available
Reference.verify() line: not availableSignedInfo(Manifest).verifyReferences(boolean) line: not availableSignedInfo.verify(boolean) line: not availableXMLSignature.checkSignatureValue(Key) line: not available
XMLSignature.checkSignatureValue(X509Certificate) line: not availableSignatureProcessor.verifyXMLSignature(Element, Crypto, X509Certificate[], Set, byte[][]) line: 264SignatureProcessor.handleToken(Element, Crypto, Crypto, CallbackHandler, WSDocInfo, Vector, WSSConfig) line: 79
WSSecurityEngine.processSecurityHeader(Element, CallbackHandler, Crypto, Crypto) line: 269WSSecurityEngine.processSecurityHeader(Document, String, CallbackHandler, Crypto, Crypto) line: 191WSDoAllReceiver.processMessage
(MessageContext) line: 180WSDoAllReceiver(WSDoAllHandler).invoke(MessageContext) line: 82

Type missing!

2006-05-26 Thread Dale Herrig




Hi,

I am using WSDL2Java from AXIS2 1.0 release version and getting the error"axis2.schema.SchemaCompilationException: Type missing!Is there any way I can figure out what the "Type missing" is.  XMLSpy saysthe WSDL file is syntactical correct but apparently WSSD2Java thinks there isa semantic problem, any ideas on how to figure out what the "Type missing" is.Regards,Dale

Re: [Axis2] Namespaces with and without security turned on

2006-05-26 Thread Eran Chinthaka

Seems like a bug in ns handling of DOOM. Can you please create a JIRA
issue (http://issues.apache.org/jira/browse/AXIS2).

Ruchith, you wanna try this ?



Marcus Ludvigson wrote:
 Hi,
  
 I am executing a webservice with and without security turned on. The
 result when executing the WS with security turned on is that I get
 excessive amount of namespaces ( axis2ns23, axis2ns24, axis2ns25, etc)
 compared to executing without security. I also get a
 ArrayIndexOutOfBoundsException the first time running with security but
 it works if I run it again.
  
 Who is generating all of these namespaces, and can I do something to
 avoid it?
  
 See info below.
  
 Regards,
 Marcus Ludvigson
  
  
 Result when executing without security: 
  
 listAllServicesResponse
 xmlns=http://corp.net/ConfigManager/listAllServices;
   service secure=false servicename=Program/
   service secure=false servicename=Apps/
   service secure=false servicename=ConfigManager/
   service secure=false servicename=version/
 /listAllServicesResponse
  
  
 Result when executing with security:
  
 listAllServicesResponse
 xmlns:axis2ns21=http://corp.net/ConfigManager/listAllServices;
 xmlns:xenc= http://www.w3.org/2001/04/xmlenc#;
 xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:wsu=
 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
 xmlns=http://corp.net/ConfigManager/listAllServices; xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/;
   service secure=false servicename=Program xmlns:axis2ns22=
 http://corp.net/ConfigManager/listAllServices/
 http://corp.net/ConfigManager/listAllServices/
   service secure=false servicename=Apps
 xmlns:axis2ns23=http://corp.net/ConfigManager/listAllServices/
 http://corp.net/ConfigManager/listAllServices/
   service secure=true servicename=ConfigManager
 xmlns:axis2ns24=http://corp.net/ConfigManager/listAllServices/
 http://corp.net/ConfigManager/listAllServices/
 /listAllServicesResponse
  
  
 Relevant part from the WSDL:
  
 xs:schema
 targetNamespace=http://corp.net/ConfigManager/listAllServices;
 elementFormDefault=qualified
xs:element name=listAllServicesResponse
 xs:complexType
  xs:sequence
   xs:element name=service maxOccurs=unbounded 
xs:complexType
 xs:attribute name=servicename type=xs:string /
 xs:attribute name=secure type=xs:boolean /
/xs:complexType
   /xs:element
  /xs:sequence
 /xs:complexType
/xs:element
  /xs:schema
  
  
 ArrayIndexOutOfBounds:
  
 SymbMap.index(Object) line: not available
 SymbMap.get(String) line: not available
 NameSpaceSymbTable.addMapping(String, String, Attr) line: not available
 Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).handleAttributesSubtree(Element,
 NameSpaceSymbTable) line: not available
 Canonicalizer20010315ExclOmitComments(CanonicalizerBase).canonicalizeSubTree(Node,
 NameSpaceSymbTable, Node) line: not available
 Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalizeSubTree(Node,
 Node) line: not available
 Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalize(XMLSignatureInput)
 line: not available
 Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).engineCanonicalize(XMLSignatureInput,
 String) line: not available
 TransformC14NExclusive.enginePerformTransform(XMLSignatureInput,
 OutputStream) line: not available
 Transform.performTransform(XMLSignatureInput, OutputStream) line: not
 available
 Transforms.performTransforms(XMLSignatureInput, OutputStream) line: not
 available
 Reference.getContentsAfterTransformation(XMLSignatureInput,
 OutputStream) line: not available
 Reference.dereferenceURIandPerformTransforms(OutputStream) line: not
 available
 Reference.calculateDigest() line: not available
 Reference.verify() line: not available
 SignedInfo(Manifest).verifyReferences(boolean) line: not available
 SignedInfo.verify(boolean) line: not available
 XMLSignature.checkSignatureValue(Key) line: not available
 XMLSignature.checkSignatureValue(X509Certificate) line: not available
 SignatureProcessor.verifyXMLSignature(Element, Crypto,
 X509Certificate[], Set, byte[][]) line: 264
 SignatureProcessor.handleToken(Element, Crypto, Crypto, CallbackHandler,
 WSDocInfo, Vector, WSSConfig) line: 79
 WSSecurityEngine.processSecurityHeader(Element, CallbackHandler, Crypto,
 Crypto) line: 269
 WSSecurityEngine.processSecurityHeader(Document, String,
 CallbackHandler, Crypto, Crypto) line: 191
 WSDoAllReceiver.processMessage (MessageContext) line: 180
 WSDoAllReceiver(WSDoAllHandler).invoke(MessageContext) line: 82
  
  




signature.asc
Description: OpenPGP digital signature

Re: Axis2[1.0] war in Weblogic 9.1

2006-05-26 Thread Junaid . Bhatra

If you are interested in distributing Axis2 with a set of fixed
pre-deployed services/modules, you can try to put those services/modules
directly within the war, and deploy the modified war.

I doubt if this will work in all containers since Axis2 relies on the
repository being a regular folder on the file system. As you said, it's up
to the container to explode the war internally (I believe WebSphere
explodes it while WebLogic 9.1 does not).

There are basically 2 options as I understand:
1)Deploy as an exploded war
2)Deploy as a war/ear and specifiy the paths to Axis2 repository and
axis2.xml via the following properties in web.xml:
init-param
param-nameaxis2.xml.path/param-name
param-valueC:\Axis2\repository\axis2.xml/param-value
/init-param
init-param
param-nameaxis2.repository.path/param-name
param-valueC:\Axis2\repository/param-value
/init-param

-Junaid

Rodrigo Ruiz
[EMAIL PROTECTED]
s.com To
axis-user@ws.apache.org
05/26/2006 04:38 cc
AM
Subject
Re: Axis2[1.0] war in Weblogic 9.1
Please respond to
[EMAIL PROTECTED]
he.org

Hi,

The behaviour you describe is perfectly normal with regard to the
Servlet Specification.

In any case, deploying it as an exploded war is the correct way to
prevent those errors.

Hope this helps,
Rodrigo Ruiz

Ali Sadik Kumlali wrote:
Hi Gopal,

I don't know why this happens, though.

Regards,

Ali Sadik Kumlali

*/Gopal Patwa [EMAIL PROTECTED]/* wrote:

I tried axis2.war deploying on weblogic 9.1 as war, deployment was
sucessful
but unable to load version service.

But if I use exploded war it works..

Any idea why it's happening, did any one had success runing
axis2.war under
weblogic 9.1

Thanks
Gopal
--
View this message in context:

http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4571990
Sent from the Axis - User forum at Nabble.com.

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

How low will we go? Check out Yahoo! Messenger’s low PC-to-Phone call
rates.

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.7.1/348 - Release Date: 25/05/2006

http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.com/evt=39663/*http://voice.yahoo.com

--
---
GRIDSYSTEMSRodrigo Ruiz Aguayo
Parc Bit - Son Espanyol
07120 Palma de Mallorca

RE: Type missing!

2006-05-26 Thread Dale Herrig




The 
actual exception being thrown is:

Exception in thread "main" 
org.apache.axis2.wsdl.codegen.CodeGenerationException: 
java.lang.RuntimeException: 
org.apache.axis2.schema.SchemaCompilationException: Type 
missing! at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) 
at 
org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) 
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)Caused by: 
java.lang.RuntimeException: org.apache.axis2.schema.SchemaCompilationException: 
Type missing! at 
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:117) 
at 
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:140) 
... 2 moreCaused by: org.apache.axis2.schema.SchemaCompilationException: 
Type missing! at 
org.apache.axis2.schema.writer.JavaBeanWriter.addPropertyEntries(JavaBeanWriter.java:464) 
at 
org.apache.axis2.schema.writer.JavaBeanWriter.populateInfo(JavaBeanWriter.java:426) 
at 
org.apache.axis2.schema.writer.JavaBeanWriter.getBeanElement(JavaBeanWriter.java:403) 
at 
org.apache.axis2.schema.writer.JavaBeanWriter.process(JavaBeanWriter.java:320) 
at 
org.apache.axis2.schema.writer.JavaBeanWriter.write(JavaBeanWriter.java:175) 
at 
org.apache.axis2.schema.SchemaCompiler.writeComplexType(SchemaCompiler.java:634) 
at 
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:389) 
at 
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:334) 
at 
org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:915) 
at 
org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:878) 
at 
org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:643) 
at 
org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:616) 
at 
org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:577) 
at 
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:366) 
at 
org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:344) 
at 
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:226) 
at 
org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:181) 
at 
org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:70)

  -Original Message-From: Dale Herrig 
  [mailto:[EMAIL PROTECTED]Sent: Friday, May 26, 2006 8:21 
  AMTo: axis-user@ws.apache.orgSubject: Type 
  missing!
  Hi,
  
  I am using WSDL2Java from AXIS2 1.0 release version and getting the error"axis2.schema.SchemaCompilationException: Type missing!Is there any way I can figure out what the "Type missing" is.  XMLSpy saysthe WSDL file is syntactical correct but apparently WSSD2Java thinks there isa semantic problem, any ideas on how to figure out what the "Type missing" is.Regards,Dale

Re: [Axis2] Namespaces with and without security turned on

2006-05-26 Thread Marcus Ludvigson

Of course,

JIRA: http://issues.apache.org/jira/browse/AXIS2-771

Regards, 
Marcus Ludvigson
On 5/26/06, Eran Chinthaka [EMAIL PROTECTED] wrote:
Seems like a bug in ns handling of DOOM. Can you please create a JIRAissue (
http://issues.apache.org/jira/browse/AXIS2).Ruchith, you wanna try this ?Marcus Ludvigson wrote: Hi, I am executing a webservice with and without security turned on. The
 result when executing the WS with security turned on is that I get excessive amount of namespaces ( axis2ns23, axis2ns24, axis2ns25, etc) compared to executing without security. I also get a ArrayIndexOutOfBoundsException the first time running with security but
 it works if I run it again. Who is generating all of these namespaces, and can I do something to avoid it? See info below. Regards, Marcus Ludvigson
 Result when executing without security: listAllServicesResponse xmlns=http://corp.net/ConfigManager/listAllServices
 service secure=false servicename=Program/ service secure=false servicename=Apps/ service secure=false servicename=ConfigManager/
 service secure=false servicename=version/ /listAllServicesResponse Result when executing with security: listAllServicesResponse
 xmlns:axis2ns21=http://corp.net/ConfigManager/listAllServices xmlns:xenc= http://www.w3.org/2001/04/xmlenc#
 xmlns:wsa=http://www.w3.org/2005/08/addressing xmlns:wsu= 
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd xmlns=http://corp.net/ConfigManager/listAllServices xmlns:soapenv=
 http://schemas.xmlsoap.org/soap/envelope/ service secure=false servicename=Program xmlns:axis2ns22=
 http://corp.net/ConfigManager/listAllServices/ http://corp.net/ConfigManager/listAllServices
/ service secure=false servicename=Apps xmlns:axis2ns23=http://corp.net/ConfigManager/listAllServices
/ http://corp.net/ConfigManager/listAllServices/ service secure=true servicename=ConfigManager
 xmlns:axis2ns24=http://corp.net/ConfigManager/listAllServices/ http://corp.net/ConfigManager/listAllServices
/ /listAllServicesResponse Relevant part from the WSDL: xs:schema targetNamespace=
http://corp.net/ConfigManager/listAllServices elementFormDefault=qualifiedxs:element name=listAllServicesResponse xs:complexTypexs:sequence
 xs:element name=service maxOccurs=unbounded xs:complexType xs:attribute name=servicename type=xs:string /
 xs:attribute name=secure type=xs:boolean //xs:complexType /xs:element/xs:sequence /xs:complexType
/xs:element/xs:schema ArrayIndexOutOfBounds: SymbMap.index(Object) line: not available SymbMap.get(String) line: not available 
NameSpaceSymbTable.addMapping(String, String, Attr) line: not available Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).handleAttributesSubtree(Element, NameSpaceSymbTable) line: not available
 Canonicalizer20010315ExclOmitComments(CanonicalizerBase).canonicalizeSubTree(Node, NameSpaceSymbTable, Node) line: not available Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalizeSubTree(Node,
 Node) line: not available Canonicalizer20010315ExclOmitComments(CanonicalizerBase).engineCanonicalize(XMLSignatureInput) line: not available Canonicalizer20010315ExclOmitComments(Canonicalizer20010315Excl).engineCanonicalize(XMLSignatureInput,
 String) line: not available TransformC14NExclusive.enginePerformTransform(XMLSignatureInput, OutputStream) line: not available Transform.performTransform(XMLSignatureInput, OutputStream) line: not
 available Transforms.performTransforms(XMLSignatureInput, OutputStream) line: not available Reference.getContentsAfterTransformation(XMLSignatureInput, OutputStream) line: not available
 Reference.dereferenceURIandPerformTransforms(OutputStream) line: not available Reference.calculateDigest() line: not available Reference.verify() line: not available SignedInfo(Manifest).verifyReferences(boolean) line: not available
 SignedInfo.verify(boolean) line: not available XMLSignature.checkSignatureValue(Key) line: not available XMLSignature.checkSignatureValue(X509Certificate) line: not available SignatureProcessor.verifyXMLSignature
(Element, Crypto, X509Certificate[], Set, byte[][]) line: 264 SignatureProcessor.handleToken(Element, Crypto, Crypto, CallbackHandler, WSDocInfo, Vector, WSSConfig) line: 79 WSSecurityEngine.processSecurityHeader
(Element, CallbackHandler, Crypto, Crypto) line: 269 WSSecurityEngine.processSecurityHeader(Document, String, CallbackHandler, Crypto, Crypto) line: 191 WSDoAllReceiver.processMessage (MessageContext) line: 180
 WSDoAllReceiver(WSDoAllHandler).invoke(MessageContext) line: 82

Re: [Axis2] setOperationContext() question

2006-05-26 Thread Michele Mazzucco

Right, but how can I get the same result, say, in a message handler,
where you have only the message context?

Michele

Samisa Abeysinghe wrote:
 Michele Mazzucco wrote:
 
 Hi all,

 is it possible to get the same result with outgoing messages as well by
 using the setOperationContext() (it seems to me that the

 outMsgCtx =
 opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

 into the setOperationContext() doesn't work as espected
 )?

 If no, is there any way to add some headers to outgoing messages?
  

 You can use:
 public void addHeader(OMElement header)
 of service client to add headers.
 
 HTH.
 Samisa...
 
 Thanks in advance,
 Michele

 -
 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]
 

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

Re: QUESTION: meaning of message - FileProvider - Configuration file read-only so engine configuration changes will not be saved

2006-05-26 Thread Jeff Greif


ANTHONY ZIOLKOWSKI wrote:
While running an axis client under in a web browser applet, I get the 
message - FileProvider - Configuration file read-only so engine 
configuration changes will not be saved. What does it mean?
Applets usually run in a sandbox which prevents them from writing to the 
file system.  In this case, the Axis engine is trying to save its 
configuration to a file.  As this is not allowed, it can keep it in 
memory but not persist it to disk.  For example, if additional services 
are deployed while it is running, they will need to be deployed the next 
time the applet is restarted.


Jeff

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

Re: [Axis2] setOperationContext() question

2006-05-26 Thread Samisa Abeysinghe


Michele Mazzucco wrote:


Right, but how can I get the same result, say, in a message handler,
where you have only the message context?
 

If I understand your problem correct, you want to add a header from a 
handler.
If that is the case, you can access the SOAP envelope and use its API to 
get the job done.


Samisa...


Michele

Samisa Abeysinghe wrote:
 


Michele Mazzucco wrote:

   


Hi all,

is it possible to get the same result with outgoing messages as well by
using the setOperationContext() (it seems to me that the

outMsgCtx =
opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

into the setOperationContext() doesn't work as espected
)?

If no, is there any way to add some headers to outgoing messages?


 


You can use:
public void addHeader(OMElement header)
of service client to add headers.

HTH.
Samisa...

   


Thanks in advance,
Michele

-
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]

   



-
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]

Re: Type missing!

2006-05-26 Thread Martin Gainty




Dale-
Can you post the WSDL you are using for us to look at?
Thanks,Martin --
*This 
email message and any files transmitted with it contain 
confidentialinformation intended only for the person(s) to whom this email 
message isaddressed. If you have received this email message in error, 
please notifythe sender immediately by telephone or email and destroy the 
originalmessage without making a copy. Thank you.



  - Original Message - 
  From: 
  Dale 
  Herrig 
  To: axis-user@ws.apache.org 
  Sent: Friday, May 26, 2006 11:36 AM
  Subject: RE: Type missing!
  
  The 
  actual exception being thrown is:
  
  Exception in thread "main" 
  org.apache.axis2.wsdl.codegen.CodeGenerationException: 
  java.lang.RuntimeException: 
  org.apache.axis2.schema.SchemaCompilationException: Type 
  missing! at 
  org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:185) 
  at 
  org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32) 
  at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)Caused by: 
  java.lang.RuntimeException: 
  org.apache.axis2.schema.SchemaCompilationException: Type 
  missing! at 
  org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:117) 
  at 
  org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGenerationEngine.java:140) 
  ... 2 moreCaused by: org.apache.axis2.schema.SchemaCompilationException: 
  Type missing! at 
  org.apache.axis2.schema.writer.JavaBeanWriter.addPropertyEntries(JavaBeanWriter.java:464) 
  at 
  org.apache.axis2.schema.writer.JavaBeanWriter.populateInfo(JavaBeanWriterjava:426) 
  at 
  org.apache.axis2.schema.writer.JavaBeanWriter.getBeanElement(JavaBeanWriter.java:403) 
  at 
  org.apache.axis2.schema.writer.JavaBeanWriter.process(JavaBeanWriter.java:320) 
  at 
  org.apache.axis2.schema.writer.JavaBeanWriter.write(JavaBeanWriter.java:175) 
  at 
  org.apache.axis2.schema.SchemaCompiler.writeComplexType(SchemaCompiler.java:634) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:389) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:334) 
  at 
  org.apache.axis2.schema.SchemaCompiler.process(SchemaCompiler.java:915) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processParticle(SchemaCompiler.java:878) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processComplexType(SchemaCompiler.java:643) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processNamedComplexSchemaType(SchemaCompiler.java:616) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processSchema(SchemaCompiler.java:577) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:366) 
  at 
  org.apache.axis2.schema.SchemaCompiler.processElement(SchemaCompiler.java:344) 
  at 
  org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:226) 
  at 
  org.apache.axis2.schema.SchemaCompiler.compile(SchemaCompiler.java:181) 
  at 
  org.apache.axis2.wsdl.codegen.extension.SimpleDBExtension.engage(SimpleDBExtension.java:70)
  
-Original Message-From: Dale Herrig 
[mailto:[EMAIL PROTECTED]Sent: Friday, May 26, 2006 8:21 
AMTo: axis-user@ws.apache.orgSubject: Type 
missing!
Hi,

I am using WSDL2Java from AXIS2 1.0 release version and getting the error"axis2.schema.SchemaCompilationException: Type missing!Is there any way I can figure out what the "Type missing" is.  XMLSpy saysthe WSDL file is syntactical correct but apparently WSSD2Java thinks there isa semantic problem, any ideas on how to figure out what the "Type missing" is.Regards,Dale

Re: QUESTION: meaning of message - FileProvider - Configuration file read-only so engine configuration changes will not be saved

I see. Is there anyway of supressing the message or eliminating entirely? My applet will be polling frequently and the message appears in the console on every poll.- Original Message From: Jeff Greif [EMAIL PROTECTED]To: axis-user@ws.apache.orgSent: Friday, May 26, 2006 11:53:20 AMSubject: Re: QUESTION: meaning of message - FileProvider - Configuration file read-only so engine configuration changes will not be savedANTHONY ZIOLKOWSKI wrote: While running an axis client under in a web browser applet, I get the  message - FileProvider - Configuration file read-only so engine  configuration changes will not be saved. What does it mean?Applets usually
 run in a sandbox which prevents them from writing to the file system.In this case, the Axis engine is trying to save its configuration to a file.As this is not allowed, it can keep it in memory but not persist it to disk.For example, if additional services are deployed while it is running, they will need to be deployed the next time the applet is restarted.Jeff-To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2[1.0] war in Weblogic 9.1


Thanks guys, now I am more clear weblogic 9.1 behaviour with axis2.war

I like 2nd option b'cos with 1st option I can't deploy exploded war in
production   

-Gopal
--
View this message in context: 
http://www.nabble.com/Axis2-1.0-+war+in+Weblogic+9.1-t1685447.html#a4579488
Sent from the Axis - User forum at Nabble.com.


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

[Axis 2]Deploying a Service and WSDL woes

2006-05-26 Thread James Loghry

Hi all,
Due to a need for supported Asynchronous messaging, I'm attempting to
migrate services from Axis 1.3 to Axis 2 1.0.  I'm having trouble
deploying a service.  When I deploy a service, a archive it into a .aar
file, along with its services.xml file in the META-INF folder.  I upload
it to the axis2/WEB-INF/services folder, and eventually it is listed
under Axis2 services.

However, when I click on the service, it claims the WSDL file is
missing.  Now, this was automatically generated in Axis 1.3 when you use
a *.WSDD file along with deploying.  On the Axis 2 user guide, I read
the WSDL file should be generated automatically after importing the .aar
file.  I had no such luck.

Do I have to generate the WSDL file by hand?  (I could not find an
install of Java2WSDL with the axis 2 1.0 binary distribution either..)

Thank you,
- James Loghry

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

Re: QUESTION: meaning of message - FileProvider - Configuration file read-only so engine configuration changes will not be saved

2006-05-26 Thread Jeff Greif


You could probably set the logging level to Warn for the logging category
org.apache.axis.configuration.FileProvider.  (The message you're
trying to suppress is of level Info.)  You'd probably need to edit the
logging.properties file in the axis jar or alter the logging
configuration programmatically.

Jeff
On 5/26/06, ANTHONY ZIOLKOWSKI [EMAIL PROTECTED] wrote:



I see. Is there anyway of supressing the message or eliminating entirely? My
applet will be polling frequently and the message appears in the console on
every poll.


- Original Message 
From: Jeff Greif [EMAIL PROTECTED]
To: axis-user@ws.apache.org
Sent: Friday, May 26, 2006 11:53:20 AM
Subject: Re: QUESTION: meaning of message - FileProvider - Configuration
file read-only so engine configuration changes will not be saved


ANTHONY ZIOLKOWSKI wrote:
 While running an axis client under in a web browser applet, I get the
 message - FileProvider - Configuration file read-only so engine
 configuration changes will not be saved. What does it mean?
Applets usually run in a sandbox which prevents them from writing to the
file system.  In this case, the Axis engine is trying to save its
configuration to a file.  As this is not allowed, it can keep it in
memory but not persist it to disk.  For example, if additional services
are deployed while it is running, they will need to be deployed the next
time the applet is restarted.

Jeff

-
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]

[Axis2] WSDL2Code ?

2006-05-26 Thread Paul Gonchar

Has anyone used WSDL2Code generator successfully? I
keep getting code that contains call to
org.apache.axiom.om.OMElement.Factory.parse().

Axiom spec says OMElement is an interface and it can't
contain any Factory.

Any ideas?

Thanks!
Paul.

P.S. Data binding mode does not matter - in all cases
I get this code.




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

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

Axis2[1.0] missing POM file on Maven2 repository


Axis2 Team,

Is it possible to upload a axis2 1.0 pom.xml on maven2 repository.
http://www.ibiblio.org/maven2/axis2/axis2/1.0/

I get this error if pom file is not uploaded, when I manually added my
dependencies.

May this is maven2 problem

Project ID: ws-commons:axiom-impl

Reason: Error getting POM for 'ws-commons:axiom-impl' from the repository:
Error transferring file
  ws-commons:axiom-impl:pom:1.0

(Internal repository, running  maven-proxy)

from the specified remote repositories:
  central (http://flygon.liquid.com:/repository)

Thanks
Gopal
--
View this message in context: 
http://www.nabble.com/Axis2-1.0-+missing+POM+file+on+Maven2+repository-t1687923.html#a4580015
Sent from the Axis - User forum at Nabble.com.


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

Controlling the reply destination of the SOAP client for IN-OUT sync pattern









I have a question about the JMS usage in Axis2. I see the
following snippet in the SendSession inner class:




byte[] call(JMSEndpoint endpoint, byte[] message, long timeout, HashMap
properties)


throws Exception {


Destination reply = createTemporaryDestination();


MessageConsumer subscriber = createConsumer(reply);


BytesMessage jmsMessage = m_session.createBytesMessage();



According to this, I dont have control over the
destination of the reply for Sync connections. Is this true? If that is the
case, I cannot properly communicate with an EnterpriseServiceBus using the
IN-OUT pattern. Am I missing something here? Is there no way to have the Sync
connection receive on a destination that is provided in the endpoint?



jms:/TestRequestQueue?replyDestination=TestResponseQueueconnectionFactory=ConnectionFactory



I should be able to direct the client to listen on the replyDestination
parameter.



Thanks,

Ozgur (Ozzie) Gurkan

Wellpoint Member 2 - SAF Team

Cell: 404-641-3381

Pager: [EMAIL PROTECTED]





This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

WSDL for passworded Service?

2006-05-26 Thread MacDermid, Kenny

Hello,

I'm looking to get the wsdl for a middle-tier application for which I
don't yet have the service password. I can retrieve the wsdl's for the
other services by simply adding '?wsdl' to the end, but this service
requests authentication even when just requesting the wsdl.

Is there any way to get around this?

Thanks,

Kenny

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

Re: [Axis2] setOperationContext() question

2006-05-26 Thread Chathura Herath


The out message context is created at the end of the in chain by the
message receiver only if required(e.g. if the mep is In-Only the
particular message receiver will not create the out message context).
Anyway, what you have described below isnt the anticipated programming
model of axis2.
Here is wht you should do.
Write an inflow  handler  that saves the headers/state(that u want to
lookup in the outflow) in the operationcontext using the setProperty
method.
Write and outflow handler that extracts this saved state/header from
the operation context and set it to the out soapEnvelop.
Create amodule out of this handler(s) and deploy.
You can use the same handler for both,  have a look at the login
module in the user guide.
http://ws.apache.org/axis2/1_0/userguide4.html#Step2_:_LogHandler
HTH
Chathura

On 5/26/06, Michele Mazzucco [EMAIL PROTECTED] wrote:

Hi all,

is it possible to get the same result with outgoing messages as well by
using the setOperationContext() (it seems to me that the

outMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

into the setOperationContext() doesn't work as espected
)?

If no, is there any way to add some headers to outgoing messages?

Thanks in advance,
Michele

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





--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/

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

Re: [Axis2] Returning a MTOM message causes IOException (closed stream)

2006-05-26 Thread Thilina Gunarathne


//image/echoImage/soapenv:Body/soapenv:Envelope--MIMEBoundaryurn_uuid_19E43A1912FEAF555111483041641261content-type: image/jpegcontent-transfer-encoding: binary
content-id: 1.urn:uuid:[EMAIL PROTECTED]ÿØÿà
Didn't you had a trailing boundary after this in your message...? Also try using FileDataSource instead of ImageDataSource... 

~Thilina

Re: [Axis2] setOperationContext() question

2006-05-26 Thread Chathura Herath


Following was for server side header manipulation btw.
Regards
Chathura

On 5/26/06, Chathura Herath [EMAIL PROTECTED] wrote:

The out message context is created at the end of the in chain by the
message receiver only if required(e.g. if the mep is In-Only the
particular message receiver will not create the out message context).
Anyway, what you have described below isnt the anticipated programming
model of axis2.
Here is wht you should do.
Write an inflow  handler  that saves the headers/state(that u want to
lookup in the outflow) in the operationcontext using the setProperty
method.
Write and outflow handler that extracts this saved state/header from
the operation context and set it to the out soapEnvelop.
Create amodule out of this handler(s) and deploy.
You can use the same handler for both,  have a look at the login
module in the user guide.
http://ws.apache.org/axis2/1_0/userguide4.html#Step2_:_LogHandler
HTH
Chathura

On 5/26/06, Michele Mazzucco [EMAIL PROTECTED] wrote:
 Hi all,

 is it possible to get the same result with outgoing messages as well by
 using the setOperationContext() (it seems to me that the

 outMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);

 into the setOperationContext() doesn't work as espected
 )?

 If no, is there any way to add some headers to outgoing messages?

 Thanks in advance,
 Michele

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




--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/




--
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/

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

Re: [Axis2] setOperationContext() question

2006-05-26 Thread robert lazarski

You can use WSDLConstants.MESSAGE_LABEL_IN_VALUE and
WSDLConstants.MESSAGE_LABEL_OUT_VALUE . Or, messageContext.getFLOW(),
ie: 

if (messageContext.getFLOW() == MessageContext.IN_FLOW) {
...
} else (messageContext.getFLOW() == MessageContext.OUT_FLOW) {
...
}

HTH,
Robert
http://www.braziloutsource.com/
On 5/26/06, Michele Mazzucco [EMAIL PROTECTED] wrote:
Chathura,I'm sorry, but if I use the same handler, how can I distinguish betweenincoming and outgoing messages?Thanks,MicheleChathura Herath wrote: The out message context is created at the end of the in chain by the
 message receiver only if required(e.g. if the mep is In-Only the particular message receiver will not create the out message context). Anyway, what you have described below isnt the anticipated programming
 model of axis2. Here is wht you should do. Write an inflowhandlerthat saves the headers/state(that u want to lookup in the outflow) in the operationcontext using the setProperty method.
 Write and outflow handler that extracts this saved state/header from the operation context and set it to the out soapEnvelop. Create amodule out of this handler(s) and deploy. You can use the same handler for both,have a look at the login
 module in the user guide. http://ws.apache.org/axis2/1_0/userguide4.html#Step2_:_LogHandler HTH Chathura
 On 5/26/06, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, is it possible to get the same result with outgoing messages as well by
 using the setOperationContext() (it seems to me that the outMsgCtx = opctx.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE); into the setOperationContext() doesn't work as espected
 )? If no, is there any way to add some headers to outgoing messages? Thanks in advance, Michele -
 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]

RE: Controlling the reply destination of the SOAP client for IN-OUT sync pattern