[jira] Resolved: (AXIS2-208) Setting desired ReplyTo and WSA Action in generated code.

[Davanum Srinivas (JIRA)]

 [ http://issues.apache.org/jira/browse/AXIS2-208?page=all ]
 
Davanum Srinivas resolved AXIS2-208:


Resolution: Fixed

with latest svn we can set these in Options.

> Setting desired ReplyTo and WSA Action in generated code.
> -
>
>  Key: AXIS2-208
>  URL: http://issues.apache.org/jira/browse/AXIS2-208
>  Project: Apache Axis 2.0 (Axis2)
> Type: Bug
> Reporter: Davanum Srinivas

>
> Right now, i have to modify the stub and add the following
> _call.setWsaAction("urn:hl7-org:v3:GetXRay");
> _messageContext.setReplyTo(new 
> EndpointReference(AddressingConstants.Submission.WSA_ANONYMOUS_URL));
> Is there a better way to do this?
> thanks,
> dims

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: [AXIS2] service implementation / clustering

[Chathura Herath]

+1 and i got a feeling this would come handy when we are doing the WSRF stuff.
THanks
Chathura

On 12/17/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:
> On Fri, 2005-12-16 at 14:20 -0500, Tony Dean wrote:
> > I was thinking of having something like J2EE ServiceLifecycle.
> >
> > public interface ServiceLifecycle
> > {
> >
> > public abstract void init(Object obj)
> > throws ServiceException;
> >
> > public abstract void destroy();
> > }
> >
> > Such that a service can choose to implement it or not.  If the service
> > does implement it then the engine must call its init() when the
> > service is loaded and likewise, call its destroy() when the service is
> > removed.  It would not be appropriate to force a service to implement
> > it.
>
> +1.
>
> Sanjiva.
>
> >
>
>


--
Chathura Herath
http://www.bloglines.com/blog/chathurah

Re: [Axis2] Memory usage

[Chathura Herath]

Hi,
Nice to hear that we are working on this already.

Ajith. I am afraid the profiler is propriotary and i am using the
evaluation:(. So cant check it in. I wonder they will be generious to
give a license to Apache like IntelliJIDEA did.

Thanks
Chathura

>
> Eran is working on this .. we should have it fixed this week. We've done
> a poor job of making stuff gets taken off the tables they find
> themselves in and as a result don't release stuff. :(. But its an easy
> fix as we know where stuff is!
>
> Sanjiva.
>
>


--
Chathura Herath
http://www.bloglines.com/blog/chathurah

RE: [AXIS2] service implementation / clustering

[Sanjiva Weerawarana]

On Fri, 2005-12-16 at 14:20 -0500, Tony Dean wrote:
> I was thinking of having something like J2EE ServiceLifecycle.
>  
> public interface ServiceLifecycle
> {
>  
> public abstract void init(Object obj)
> throws ServiceException;
>  
> public abstract void destroy();
> }
>  
> Such that a service can choose to implement it or not.  If the service
> does implement it then the engine must call its init() when the
> service is loaded and likewise, call its destroy() when the service is
> removed.  It would not be appropriate to force a service to implement
> it.

+1.

Sanjiva.

> 

Re: [Axis2] Memory usage

[Sanjiva Weerawarana]

On Fri, 2005-12-16 at 13:36 -0500, Chathura Herath wrote:
> Hi devs,
> I could find a little bit of time to run a profiler on Axis2 i have
> attached a html of the memory usage. THis is the snapshot when the
> Axis2 crashes because it ran out of memory.
> 
> The garbage collection of the Message contexts are not happening
> properly and this could indeed our main problem which leads to massive
> memory build up. There is a heavy usage of Hasmaps too, I am not sure
> whether all of them are necessary.
> I will try to put some time into this.

Eran is working on this .. we should have it fixed this week. We've done
a poor job of making stuff gets taken off the tables they find
themselves in and as a result don't release stuff. :(. But its an easy
fix as we know where stuff is!

Sanjiva.

[jira] Resolved: (AXIS2-318) UTF-16 support for MTOM

[Davanum Srinivas (JIRA)]

 [ http://issues.apache.org/jira/browse/AXIS2-318?page=all ]
 
Davanum Srinivas resolved AXIS2-318:


Resolution: Fixed

Fixed in latest SVN. Enabled UTF-16 in at least 2 test cases.

thanks,
dims

> UTF-16 support for MTOM
> ---
>
>  Key: AXIS2-318
>  URL: http://issues.apache.org/jira/browse/AXIS2-318
>  Project: Apache Axis 2.0 (Axis2)
> Type: Bug
>   Components: om
> Versions: 0.93
>  Environment: Linux
> Reporter: Saminda Wishwajith Abeyruwan

>
> MTOM does not work properly with UTF-16 encoding. This is mainly due 
> existance of undefine characters in the bite order marker. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (AXIS-2301) xsd:any is mapped to array of MessageElement while maxOccurs="1"

[Hans (JIRA)]

 [ http://issues.apache.org/jira/browse/AXIS-2301?page=all ]

Hans updated AXIS-2301:
---

Attachment: newpatch.zip

Attached updated zipped patch

> xsd:any is mapped to array of MessageElement while maxOccurs="1"
> 
>
>  Key: AXIS-2301
>  URL: http://issues.apache.org/jira/browse/AXIS-2301
>  Project: Apache Axis
> Type: Bug
>   Components: WSDL processing
> Versions: 1.2.1
> Reporter: Hans
>  Attachments: anytest.diff.txt, newpatch.zip, patch.diff.txt
>
> According to the JAX-RPC 1.1 specification xsd:any should be mapped to an 
> attribute of type javax.xml.soap.SOAPElement when maxOccurs="1", or 
> javax.xml.soap.SOAPElement[] when maxOccurs is greater than 1. However, Axis 
> will always generate an array, regardless of the maxOccurs attribute.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

RE: [AXIS2] service implementation / clustering

[Tony Dean]

I was thinking of having something like J2EE 
ServiceLifecycle.
 
public interface ServiceLifecycle{
 
    public abstract void init(Object 
obj)    throws 
ServiceException;
 
    public abstract void 
destroy();}
 
Such that a service can choose to implement it or 
not.  If the service does implement it then the engine must call its init() 
when the service is loaded and likewise, call its destroy() when the service is 
removed.  It would not be appropriate to force a service to implement 
it.


From: Ajith Ranabahu 
[mailto:[EMAIL PROTECTED] Sent: Friday, December 16, 2005 
2:04 PMTo: axis-dev@ws.apache.org; [EMAIL PROTECTED]Subject: 
Re: [AXIS2] service implementation / clustering

Hi All,
The init functionality is part of the 'dependency injection' capability of 
the message receiver. It would be inappropriate to have an interface 
representing this since the service author is somewhat restricted if he is bound 
to an interface. It will also not be the proper dependency injection model. 

However I agree that our model for scoping is still not complete. We have 
to work on that (allowing session and application wide service objects) and 
perhaps on an appropriate destroy method as well. 
On 12/16/05, Davanum 
Srinivas <[EMAIL PROTECTED]> 
wrote: 
Tony,Yes, 
  you are right. We need to clean this up. Could you please startwith a 
  JIRA?- I don't think we have an interface corresponding to the init. 
  - Yes, it is for every operation call.- No, we don't have a destroy() 
  AFAIK.thanks,dimsOn 12/16/05, Tony Dean <[EMAIL PROTECTED]> wrote:> Hi, 
  >> I have been using the "public void init()" method of my 
  service implemenation to perform one-time initialization.  I can't 
  remember how I stumbled across this functionality, but it would be nice for 
  you to define an implemenation interface that describes this 
  functionality.  Maybe you have and I just do not know about 
  it.  When I tested my service, it appeared that the engine called 
  init() on every operation invocation.  I did not spend much time 
  looking through the code so I'm asking how you conceptually designed these 
  semantics?  In particular, how many instances of a particular 
  service will be instantiated by the engine?  The init() method 
  should only be called once when the service is initally 
  instantiated.  Will the engine be able to quiesce unused service 
  instances?  These are the semantics that are usually derived from 
  the container itself.  Also, suppose I have some initialization code 
  that needs to be done once and can be shared among all of my service instances 
  > (singleton functionality).  How can I accomplish this... 
  for instance, is there a way to tell how many instances of myself have been 
  instantiated?  Lastly, is there an analogous "public void destroy()" 
  that can be used to release any required resources obtained by my service? 
  >> Thank you very much.>> Tony Dean> SAS 
  Institute Inc.> 919.531.6704> [EMAIL PROTECTED]>> SAS... 
  The Power to Know> http://www.sas.com>>--Davanum 
  Srinivas : http://wso2.com/blogs/-- Ajith Ranabahu 

Re: [Axis2] Memory usage

[Ajith Ranabahu]

Hi Chathura,
Thanks for the profiling. We have not been able to run a proper profiling yet and this is indeed valuable information. If possible please check in the profiler setup/config/code so that we may run it as well and see (BTW I'm not sure about the tool you used, Hope its not properietary :))

We are already working on the lifetime handling of contexts. There should be an improvement pretty soon. 
On 12/17/05, Chathura Herath <[EMAIL PROTECTED]> wrote:
Hi devs,I could find a little bit of time to run a profiler on Axis2 i haveattached a html of the memory usage. THis is the snapshot when the
Axis2 crashes because it ran out of memory.The garbage collection of the Message contexts are not happeningproperly and this could indeed our main problem which leads to massivememory build up. There is a heavy usage of Hasmaps too, I am not sure
whether all of them are necessary.I will try to put some time into this.Comments/help is appreciated.ThanksChathura--Chathura Herath
http://www.bloglines.com/blog/chathurah--Chathura Herathhttp://www.bloglines.com/blog/chathurah
-- Ajith Ranabahu 

Re: [AXIS2] service implementation / clustering

[Ajith Ranabahu]

Hi All,
The init functionality is part of the 'dependency injection' capability of the message receiver. It would be inappropriate to have an interface representing this since the service author is somewhat restricted if he is bound to an interface. It will also not be the proper dependency injection model.

However I agree that our model for scoping is still not complete. We have to work on that (allowing session and application wide service objects) and perhaps on an appropriate destroy method as well. 
On 12/16/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
Tony,Yes, you are right. We need to clean this up. Could you please startwith a JIRA?- I don't think we have an interface corresponding to the init.
- Yes, it is for every operation call.- No, we don't have a destroy() AFAIK.thanks,dimsOn 12/16/05, Tony Dean <[EMAIL PROTECTED]> wrote:> Hi,
>> I have been using the "public void init()" method of my service implemenation to perform one-time initialization.  I can't remember how I stumbled across this functionality, but it would be nice for you to define an implemenation interface that describes this functionality.  Maybe you have and I just do not know about it.  When I tested my service, it appeared that the engine called init() on every operation invocation.  I did not spend much time looking through the code so I'm asking how you conceptually designed these semantics?  In particular, how many instances of a particular service will be instantiated by the engine?  The init() method should only be called once when the service is initally instantiated.  Will the engine be able to quiesce unused service instances?  These are the semantics that are usually derived from the container itself.  Also, suppose I have some initialization code that needs to be done once and can be shared among all of my service instances
> (singleton functionality).  How can I accomplish this... for instance, is there a way to tell how many instances of myself have been instantiated?  Lastly, is there an analogous "public void destroy()" that can be used to release any required resources obtained by my service?
>> Thank you very much.>> Tony Dean> SAS Institute Inc.> 919.531.6704> [EMAIL PROTECTED]>> SAS... The Power to Know
> http://www.sas.com>>--Davanum Srinivas : http://wso2.com/blogs/-- 
Ajith Ranabahu 

Re: [axis2] MessageContext IDs

[iksrazal]

While we're on the subject I'd like to comment since I actually use UUID's. I 
use them to keep track of users who have logged in. AFAIK 
maintainSession(true) doesn't work with multiple services. I'd like to use 
ServiceGroupContext and WS-Addressing to do this. Yet it seems harder then it 
should be and not many people are using it yet. 

The way I use UUID's is to have a service login(), which returns a UUID via a 
complex object. Every service call by that client thereafter passes in the 
UUID. I use java.util.UUID inside the service, although I could just as 
easily use commons-id. 

My whole point here is: 

1) AFAICT since a UUID via a messageContext isn't available to the user of the 
client Stub directly via a public method, I'd have to implement a handler to 
access it. 
2) There's no associated timeout state with the UUID. 
3) I'm reinventing the wheel and not utilizing the UUIDGenerator already being 
used. Yet the solution I'm using is common and is often discussed on the user 
list. 
4) Using mc.setIDGenerator() is doesn't seem any easier than just doing it 
myself as described above. 

A few Simple questions then: Can the MessageContext UUID be used to control 
login state and timeout? Can the implementation be pluggable, ie I want a 
type 4 UUID? And finally is the only way to control the MessageContext UUID 
is via a handler? 

iksrazal

Em Sexta 16 Dezembro 2005 15:31, o Glen Daniels escreveu:
> Hi Sanjiva:
> > Is there any reason why we can't make it so that every message context
> > has an id when its created? I'm fine with having getId() and setId() so
> > that the default ID can be changed but it seems to me that we never use
> > a message context without setting the ID. This avoids repeated code
> > fragments like:
> >
> > if (msgctx.getMessageID() == null) {
> >   String messageID = String.valueOf("uuid:" + UUIDGenerator.getUUID());
> >   msgctx.setMessageID(messageID);
> > }
>
> I'm not sure every MC really needs an ID - for instance, if you're doing
> sync req-resp over HTTP (quite a common case these days), you don't need
> IDs for correlation at all, since you can just keep the objects
> associated with the thread/socket.
>
> For the cases where we do need an ID, I'd like to avoid UUID generation
> unless necessary (even cheap versions are lots more expensive than
> simpler ID schemes).  How about this:
>
> interface IDGenerator {
>   String getID();
> }
>
> class SimpleIDGen implements IDGenerator {
>   static SimpleIDGen singleton() {
> // get singleton
>   }
>
>   static long curMaxID = 0;
>   String getID() {
> // return simple autoincrementing long
> synchronized (singleton) {
>   return Long.toString(curMaxID++);
> }
>   }
> }
>
> class MessageContext {
>   String messageID;
>   IDGenerator idGen = SimpleIDGen.singleton();
>
>   String getMessageID() {
> if (messageID == null) {
>   messageID = idGen.getID();
> }
> return messageID;
>   }
> }
>
> That way, we get usable auto-incrementing IDs by default, delivered only
> on demand, unless someone calls mc.setIDGenerator() with a UUID-based one.
>
> Thoughts?
>
> --Glen

Re: [Axis2 ] Fw: Axis 2 Error

[Ajith Ranabahu]

Hmmm.. Disturbing news indeed. I'm surprised to hear that the document/literal case failed (we added the wrapping support for codegen long time ago but I'm not sure whether its pre-0.92). Unfortunaltely I cannot recommend the newer version (
0.93) since we discovered a serious bug in one of the templates in the distribution (which means codegen would not work properly for WSDL's with SOAPActions).
Will get back to you once I run the codegen with the attached WSDL 
On 12/17/05, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote:
Hi All,This was a feedback I got from some of my collegues inpervasivetechnologyabs when they tried to use Axis2.
Attached is the wsdl they use and the generated classes relating to theproblem.Thanks,Jaliya- Original Message -From: "sima patel" <
[EMAIL PROTECTED]>To: <[EMAIL PROTECTED]>Sent: Friday, December 16, 2005 11:59 AMSubject: Axis 2 Error> Hi,>> I am getting following errors:
> I have one java interface and i wanted to generate wsdl file.> I used axis1.2RC2 version to generate wsdl. and axis0.92 to generated> stubs> and skeletons.> I want to point out following things.
> During wsdl generation, first i used -y"DOCUMENT" and -u"ENCODED"> during java generation i got error that does not support "use:encoded"> then i used -y"DOCUMENT" and -u"LITERAL"
> during java generation i got error stating "we dont support multiple> elements> in part"> finally i used -y"RPC" and -u"LITERAL"> i was able to generate java stubs and skeletons successfully
> but I got 19 compilation errors..> According to me.. it generates faulty code> Example: In the code there is> OMElement.newXMLStreamReader() which does not exist> also> org.apache.axis2.om.OMElement
 emptyObject= org.apach> e.axis2.om.OMElement.Factory.newInstance(); where Factory.newInstance()> does> not exist>> thanks> sima>> ***> compile:
>[javac] Compiling 232 source files to C:\sima\votable3\classes>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldDe> tailsDatabindingSupporter.java:32: cannot resolve symbol
>[javac] symbol  : variable Factory>[javac] location: interface org.apache.axis2.om.OMElement>[javac] return> org.apache.axis2.om.OMElement.Factory.parse> (p
> aram.getXMLStreamReader()) ;>[javac] ^>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldDe> tailsDatabindingSupporter.java
:47: cannot resolve symbol>[javac] symbol  : variable Factory>[javac] location: interface org.apache.axis2.om.OMElement>[javac] org.apache.axis2.om.OMElement emptyObject=
> org.apach> e.axis2.om.OMElement.Factory.newInstance();>[javac]>^>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldDe> tailsDatabindingSupporter.java
:52: incompatible types>[javac] found   : org.apache.axis2.om.OMElement>[javac] required: org.apache.xmlbeans.XmlObject>[javac] return emptyObject;>[javac]^
>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldNa> mesDatabindingSupporter.java:12: cannot resolve symbol>[javac] symbol  : method newXMLStreamReader ()
>[javac] location: interface org.apache.axis2.om.OMElement>[javac]> (org.apache.axis2.om.OMAbstractFactory.getOMFactory(),new> or> g.apache.axis2.clientapi.StreamWrapper(param.newXMLStreamReader
())) ;>[javac]>^>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldNa> mesDatabindingSupporter.java:31: cannot resolve symbol
>[javac] symbol  : variable Factory>[javac] location: interface org.apache.axis2.om.OMElement>[javac] return> org.apache.axis2.om.OMElement.Factory.parse> (p
> aram.getXMLStreamReader()) ;>[javac] ^>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldNa> mesDatabindingSupporter.java
:46: cannot resolve symbol>[javac] symbol  : variable Factory>[javac] location: interface org.apache.axis2.om.OMElement>[javac] org.apache.axis2.om.OMElement emptyObject=
> org.apach> e.axis2.om.OMElement.Factory.newInstance();>[javac]>^>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveFieldNa> mesDatabindingSupporter.java
:51: incompatible types>[javac] found   : org.apache.axis2.om.OMElement>[javac] required: org.apache.xmlbeans.XmlObject>[javac] return emptyObject;>[javac]^
>[javac] C:\sima\votable3\example1> \codegen\databinding\VotableretrieveResourc> eNamesDatabindingSupporter.java:12: cannot resolve symbol>[javac] symbol  : method newXMLStreamReader ()
>[javac] location: interface org.apache.axis2.om.OMElement>[javac]> (org.apache.axis2.om.OMAbstrac

Re: ApacheCon presentation on Synapse

[Paul Fremantle]

FixedSorry!PaulOn 12/16/05, Dan Diephouse <[EMAIL PROTECTED]> wrote:
Hi Paul,I tried opening this in Adobe, but it wouldn't load (on two differentcomputers too). Maybe something went wrong in the upload process?  Cheers,- DanPaul Fremantle wrote:> Hi folks>
> Here is the presentation I gave on Synapse at ApacheCon.> http://fremantle.org/apacheconsynapse.pdf>> Paul>> -->
> Paul Fremantle> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair> "Oxygenating the Web Service Platform", www.wso2.com > [EMAIL PROTECTED] 
[EMAIL PROTECTED]>>--Dan DiephouseEnvoi Solutions LLChttp://netzooid.com-- Paul FremantleVP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle[EMAIL PROTECTED]"Oxygenating the Web Service Platform", 
www.wso2.com

Re: ApacheCon presentation on Synapse

[Dan Diephouse]

Hi Paul,
I tried opening this in Adobe, but it wouldn't load (on two different 
computers too). Maybe something went wrong in the upload process?  Cheers,

- Dan

Paul Fremantle wrote:

Hi folks

Here is the presentation I gave on Synapse at ApacheCon.
http://fremantle.org/apacheconsynapse.pdf

Paul

--

Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
"Oxygenating the Web Service Platform", www.wso2.com 


http://bloglines.com/blog/paulfremantle

[EMAIL PROTECTED] 




--
Dan Diephouse
Envoi Solutions LLC
http://netzooid.com

Re: [axis2] MessageContext IDs

[Glen Daniels]

Hi Sanjiva:

> Is there any reason why we can't make it so that every message context
> has an id when its created? I'm fine with having getId() and setId() so
> that the default ID can be changed but it seems to me that we never use
> a message context without setting the ID. This avoids repeated code
> fragments like:
> 
> if (msgctx.getMessageID() == null) {  
>   String messageID = String.valueOf("uuid:" + UUIDGenerator.getUUID());
>   msgctx.setMessageID(messageID);
> }

I'm not sure every MC really needs an ID - for instance, if you're doing
sync req-resp over HTTP (quite a common case these days), you don't need
IDs for correlation at all, since you can just keep the objects
associated with the thread/socket.

For the cases where we do need an ID, I'd like to avoid UUID generation
unless necessary (even cheap versions are lots more expensive than
simpler ID schemes).  How about this:

interface IDGenerator {
  String getID();
}

class SimpleIDGen implements IDGenerator {
  static SimpleIDGen singleton() {
// get singleton
  }

  static long curMaxID = 0;
  String getID() {
// return simple autoincrementing long
synchronized (singleton) {
  return Long.toString(curMaxID++);
}
  }
}

class MessageContext {
  String messageID;
  IDGenerator idGen = SimpleIDGen.singleton();

  String getMessageID() {
if (messageID == null) {
  messageID = idGen.getID();
}
return messageID;
  }
}

That way, we get usable auto-incrementing IDs by default, delivered only
on demand, unless someone calls mc.setIDGenerator() with a UUID-based one.

Thoughts?

--Glen

[Axis2 ] Fw: Axis 2 Error

[Jaliya Ekanayake]

Hi All,

This was a feedback I got from some of my collegues in 
pervasivetechnologyabs when they tried to use Axis2.
Attached is the wsdl they use and the generated classes relating to the 
problem.


Thanks,

Jaliya
- Original Message - 
From: "sima patel" <[EMAIL PROTECTED]>

To: <[EMAIL PROTECTED]>
Sent: Friday, December 16, 2005 11:59 AM
Subject: Axis 2 Error



Hi,

I am getting following errors:
I have one java interface and i wanted to generate wsdl file.
I used axis1.2RC2 version to generate wsdl. and axis0.92 to generated 
stubs

and skeletons.
I want to point out following things.
During wsdl generation, first i used -y"DOCUMENT" and -u"ENCODED"
during java generation i got error that does not support "use:encoded"
then i used -y"DOCUMENT" and -u"LITERAL"
during java generation i got error stating "we dont support multiple 
elements

in part"
finally i used -y"RPC" and -u"LITERAL"
i was able to generate java stubs and skeletons successfully
but I got 19 compilation errors..
According to me.. it generates faulty code
Example: In the code there is
OMElement.newXMLStreamReader() which does not exist
also
org.apache.axis2.om.OMElement emptyObject= org.apach
e.axis2.om.OMElement.Factory.newInstance(); where Factory.newInstance() 
does

not exist

thanks
sima

***
compile:
   [javac] Compiling 232 source files to C:\sima\votable3\classes
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldDe
tailsDatabindingSupporter.java:32: cannot resolve symbol
   [javac] symbol  : variable Factory
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] return 
org.apache.axis2.om.OMElement.Factory.parse

(p
aram.getXMLStreamReader()) ;
   [javac] ^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldDe
tailsDatabindingSupporter.java:47: cannot resolve symbol
   [javac] symbol  : variable Factory
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] org.apache.axis2.om.OMElement emptyObject=
org.apach
e.axis2.om.OMElement.Factory.newInstance();
   [javac]
   ^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldDe
tailsDatabindingSupporter.java:52: incompatible types
   [javac] found   : org.apache.axis2.om.OMElement
   [javac] required: org.apache.xmlbeans.XmlObject
   [javac] return emptyObject;
   [javac]^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldNa
mesDatabindingSupporter.java:12: cannot resolve symbol
   [javac] symbol  : method newXMLStreamReader ()
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] 
(org.apache.axis2.om.OMAbstractFactory.getOMFactory(),new

or
g.apache.axis2.clientapi.StreamWrapper(param.newXMLStreamReader())) ;
   [javac]
   ^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldNa
mesDatabindingSupporter.java:31: cannot resolve symbol
   [javac] symbol  : variable Factory
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] return 
org.apache.axis2.om.OMElement.Factory.parse

(p
aram.getXMLStreamReader()) ;
   [javac] ^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldNa
mesDatabindingSupporter.java:46: cannot resolve symbol
   [javac] symbol  : variable Factory
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] org.apache.axis2.om.OMElement emptyObject=
org.apach
e.axis2.om.OMElement.Factory.newInstance();
   [javac]
   ^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveFieldNa
mesDatabindingSupporter.java:51: incompatible types
   [javac] found   : org.apache.axis2.om.OMElement
   [javac] required: org.apache.xmlbeans.XmlObject
   [javac] return emptyObject;
   [javac]^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveResourc
eNamesDatabindingSupporter.java:12: cannot resolve symbol
   [javac] symbol  : method newXMLStreamReader ()
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] 
(org.apache.axis2.om.OMAbstractFactory.getOMFactory(),new

or
g.apache.axis2.clientapi.StreamWrapper(param.newXMLStreamReader())) ;
   [javac]
   ^
   [javac] C:\sima\votable3\example1
\codegen\databinding\VotableretrieveResourc
eNamesDatabindingSupporter.java:31: cannot resolve symbol
   [javac] symbol  : variable Factory
   [javac] location: interface org.apache.axis2.om.OMElement
   [javac] return 
org.apache.axis2.om.OMElement.Factory.parse

(p
aram.getXMLStreamReader()) ;
   [javac] ^
   [javac] C:\sima\votable3\example1
\cod

ApacheCon presentation on Synapse

[Paul Fremantle]

Hi folksHere is the presentation I gave on Synapse at ApacheCon.http://fremantle.org/apacheconsynapse.pdfPaul
-- Paul FremantleVP/Technology, WSO2 and OASIS WS-RX TC Co-chair"Oxygenating the Web Service Platform", www.wso2.com
http://bloglines.com/blog/paulfremantle[EMAIL PROTECTED]

[jira] Commented: (AXIS-2272) Duplicated operation names

[Tom Jordahl (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS-2272?page=comments#action_12360599 ] 

Tom Jordahl commented on AXIS-2272:
---

Fair enough.  A simple test case and patches welcome.


> Duplicated operation names
> --
>
>  Key: AXIS-2272
>  URL: http://issues.apache.org/jira/browse/AXIS-2272
>  Project: Apache Axis
> Type: Bug
>   Components: WSDL processing
> Versions: 1.2.1
>  Environment: Server - jakarta tomcat 5.0.28, spring framework 1.2.5
> OS - Windows server 2003
> Java - java full version "1.4.2_07-b05"
> Client - Macromedia flex running in MS IE 6.0
> Reporter: Alex Grivnin
>  Attachments: axis.zip
>
> Axis generates invalid WSDL - more specifically operation names appears to be 
> duplicated in WSDL.
> This happens sporadically and I do not have a specific scenario to reproduce 
> it.  But I'll try to describe the application flow and may be it will provide 
> some hint... 
> Our application runs on a Tomcat server 5.0.28, it uses spring framework 
> 1.2.5 for binding Axis beans which are exposed to the client. See wsdd 
> fragment at the end of the message as well as spring context.
> At some point client (Macromedia flesh) requests wsdl before calling a web 
> service and gets an exception that fetched WSDL is not supported (as it 
> contains duplicated operation names).
> Configuration files:
> --
>  --- WSDD fragment --
>   
>value="com.mercury.onyx.client.services.axis.SpringBeanRPCProvider"/>
>value="deleteFilter,getFilter,saveUserFilter,getUserViews,getUserFilterCategories"/>
>   
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterCategoryVO"
>  qname="ns3:FilterCategoryVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterVO" 
> qname="ns3:FilterVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterDefinitionVO"
>  qname="ns3:FilterDefinitionVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterConstraintVO"
>  qname="ns3:FilterConstraintVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.ViewVO" 
> qname="ns3:ViewVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.AttributeVO" 
> qname="ns3:AttributeVO" xmlns:ns3="someNamespace"/>
>   
>  --- End of WSDD fragment --
>  --- Spring bean context -
>class="com.mercury.onyx.client.services.webservices.FiltersWS">
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  --- End of Spring bean context -

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (AXIS-2343) NoSuchMethodError:javax.xml.namespace.QName.getPrefix with WSDL2Java

[Tom Jordahl (JIRA)]

 [ http://issues.apache.org/jira/browse/AXIS-2343?page=all ]
 
Tom Jordahl closed AXIS-2343:
-

Resolution: Invalid

This indicates you have another version of the QName classes that were loaded 
instead of the ones in jaxrpc.jar.  Older versions old wsdl4j have the older 
classes in them.

> NoSuchMethodError:javax.xml.namespace.QName.getPrefix with WSDL2Java
> 
>
>  Key: AXIS-2343
>  URL: http://issues.apache.org/jira/browse/AXIS-2343
>  Project: Apache Axis
> Type: Bug
>   Components: WSDL processing
> Versions: 1.3
>  Environment: Windows2000, jdk1.4.2, AXIS1.3, bug also with AXIS1.4 nightly 
> built
> Reporter: uwe kraemer

>
> By creating java classes with WSDL2Java occurs a very strange error:
> D:\Java>java org.apache.axis.wsdl.WSDL2Java d:\java\AddressBook.wsdl
> java.lang.NoSuchMethodError: 
> javax.xml.namespace.QName.getPrefix()Ljava/lang/Str
> ing;
> at 
> org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithDifferentL
> ocal(BackslashUtil.java:62)
> at 
> org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithBackslashl
> essLocal(BackslashUtil.java:39)
> at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices(SymbolT
> able.java:3078)
> at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
> a:745)
> at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543
> )
> at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
> a:518)
> at 
> org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
> a:495)
> at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
> at java.lang.Thread.run(Thread.java:534)
> This bug occurs with AXIS1.3 released and also with AXIS1.4 nightly built 
> 16.12.05
> Any ideas, why??? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (AXIS-2272) Duplicated operation names

[Jason Weiss (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS-2272?page=comments#action_12360597 ] 

Jason Weiss commented on AXIS-2272:
---

Tom,

Yes, WSDL 1.1 supports overloaded operations, however; as you can see in my 
pasted Java code- I don't have an overloaded operation.  I have 1 method.  1 
Method that results in WSDL that says I have *two* insert methods.  Clearly, a 
bug.  

package com.cynergysystems.training;

import java.sql.Connection;
import java.sql.PreparedStatement;
import java.sql.SQLException;

import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;

public class IdeaImpl
{

public void insert(IdeaBean bean) throws SQLException
{
try
{
Context ctxt = new InitialContext();
DataSource ds = (DataSource) 
ctxt.lookup("java:comp/env/jdbc/Cynergy");
Connection conn = ds.getConnection();
conn.setAutoCommit(true);

PreparedStatement pstmt = conn.prepareStatement("insert 
into training_idea values (null,?,?,?)");
pstmt.setInt(1, bean.getCategoryId());
pstmt.setString(2, bean.getTopic());
pstmt.setString(3, bean.getDescription());
pstmt.execute();

conn.close();
} catch (SQLException sqle)
{
sqle.printStackTrace();
throw sqle;
} catch (NamingException e)
{
e.printStackTrace();
throw new SQLException(e.getMessage());
}
}

}



> Duplicated operation names
> --
>
>  Key: AXIS-2272
>  URL: http://issues.apache.org/jira/browse/AXIS-2272
>  Project: Apache Axis
> Type: Bug
>   Components: WSDL processing
> Versions: 1.2.1
>  Environment: Server - jakarta tomcat 5.0.28, spring framework 1.2.5
> OS - Windows server 2003
> Java - java full version "1.4.2_07-b05"
> Client - Macromedia flex running in MS IE 6.0
> Reporter: Alex Grivnin
>  Attachments: axis.zip
>
> Axis generates invalid WSDL - more specifically operation names appears to be 
> duplicated in WSDL.
> This happens sporadically and I do not have a specific scenario to reproduce 
> it.  But I'll try to describe the application flow and may be it will provide 
> some hint... 
> Our application runs on a Tomcat server 5.0.28, it uses spring framework 
> 1.2.5 for binding Axis beans which are exposed to the client. See wsdd 
> fragment at the end of the message as well as spring context.
> At some point client (Macromedia flesh) requests wsdl before calling a web 
> service and gets an exception that fetched WSDL is not supported (as it 
> contains duplicated operation names).
> Configuration files:
> --
>  --- WSDD fragment --
>   
>value="com.mercury.onyx.client.services.axis.SpringBeanRPCProvider"/>
>value="deleteFilter,getFilter,saveUserFilter,getUserViews,getUserFilterCategories"/>
>   
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterCategoryVO"
>  qname="ns3:FilterCategoryVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterVO" 
> qname="ns3:FilterVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterDefinitionVO"
>  qname="ns3:FilterDefinitionVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterConstraintVO"
>  qname="ns3:FilterConstraintVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.ViewVO" 
> qname="ns3:ViewVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.AttributeVO" 
> qname="ns3:AttributeVO" xmlns:ns3="someNamespace"/>
>   
>  --- End of WSDD fragment --
>  --- Spring bean context -
>class="com.mercury.onyx.client.services.webservices.FiltersWS">
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  --- End of Spring bean context -

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (AXIS-2272) Duplicated operation names

[Tom Jordahl (JIRA)]

[ 
http://issues.apache.org/jira/browse/AXIS-2272?page=comments#action_12360595 ] 

Tom Jordahl commented on AXIS-2272:
---

Overloaded operations are allowed in WSDL 1.1.  It doesn't sounds like there is 
a bug here.  If the flex/flash client does not support overloaded operations, 
then you need to publish your service with unique operation names.


> Duplicated operation names
> --
>
>  Key: AXIS-2272
>  URL: http://issues.apache.org/jira/browse/AXIS-2272
>  Project: Apache Axis
> Type: Bug
>   Components: WSDL processing
> Versions: 1.2.1
>  Environment: Server - jakarta tomcat 5.0.28, spring framework 1.2.5
> OS - Windows server 2003
> Java - java full version "1.4.2_07-b05"
> Client - Macromedia flex running in MS IE 6.0
> Reporter: Alex Grivnin
>  Attachments: axis.zip
>
> Axis generates invalid WSDL - more specifically operation names appears to be 
> duplicated in WSDL.
> This happens sporadically and I do not have a specific scenario to reproduce 
> it.  But I'll try to describe the application flow and may be it will provide 
> some hint... 
> Our application runs on a Tomcat server 5.0.28, it uses spring framework 
> 1.2.5 for binding Axis beans which are exposed to the client. See wsdd 
> fragment at the end of the message as well as spring context.
> At some point client (Macromedia flesh) requests wsdl before calling a web 
> service and gets an exception that fetched WSDL is not supported (as it 
> contains duplicated operation names).
> Configuration files:
> --
>  --- WSDD fragment --
>   
>value="com.mercury.onyx.client.services.axis.SpringBeanRPCProvider"/>
>value="deleteFilter,getFilter,saveUserFilter,getUserViews,getUserFilterCategories"/>
>   
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterCategoryVO"
>  qname="ns3:FilterCategoryVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterVO" 
> qname="ns3:FilterVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterDefinitionVO"
>  qname="ns3:FilterDefinitionVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.FilterConstraintVO"
>  qname="ns3:FilterConstraintVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.ViewVO" 
> qname="ns3:ViewVO" xmlns:ns3="someNamespace"/>
>languageSpecificType="java:com.mercury.onyx.client.services.vo.AttributeVO" 
> qname="ns3:AttributeVO" xmlns:ns3="someNamespace"/>
>   
>  --- End of WSDD fragment --
>  --- Spring bean context -
>class="com.mercury.onyx.client.services.webservices.FiltersWS">
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>  --- End of Spring bean context -

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (AXIS2-341) service deployment

[Tony Dean (JIRA)]

service deployment
--

 Key: AXIS2-341
 URL: http://issues.apache.org/jira/browse/AXIS2-341
 Project: Apache Axis 2.0 (Axis2)
Type: Improvement
  Components: deployment  
Versions: 0.94
 Environment: not pertinent
Reporter: Tony Dean


Original email:
I have been using the "public void init()" method of my service implemenation 
to perform one-time initialization.  I can't remember how I stumbled across 
this functionality, but it would be nice for you to define an implemenation 
interface that describes this functionality.  Maybe you have and I just do not 
know about it.  When I tested my service, it appeared that the engine called 
init() on every operation invocation.  I did not spend much time looking 
through the code so I'm asking how you conceptually designed these semantics?  
In particular, how many instances of a particular service will be instantiated 
by the engine?  The init() method should only be called once when the service 
is initally instantiated.  Will the engine be able to quiesce unused service 
instances?  These are the semantics that are usually derived from the container 
itself.  Also, suppose I have some initialization code that needs to be done 
once and can be shared among all of my service instances (singleton 
functionality).  How can I accomplish this... for instance, is there a way to 
tell how many instances of myself have been instantiated?  Lastly, is there an 
analogous "public void destroy()" that can be used to release any required 
resources obtained by my service?

I'd like to see the following:
1. ServiceImplInterface
public interface ServiceImplInterface {
   public void init();
   public void destroy();
}

2. init is called when the service is instantiated... should handle one-time 
initialization for the service.  destroy is called when the service is 
undeployed to release any acquired resources.

3. can we be intelligent about the number of instances that are created for a 
particular service?  if not heavily used, we need to reuse existing instances 
instead of creating additional ones.  otherwise, we all should create singleton 
services so that the system does not grow uncontrollable.

4. if we are allowed to create multiple instances of our services, there may be 
times when we want to do one-time initialization for as a whole for all of our 
services instances... is there a way to determine when the last instance is 
being undeployed (destroyed) so that this singleton-type of resource 
acquisition can be destroyed when the last instance is going away?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

RE: [jira] Created: (AXIS-2343) NoSuchMethodError:javax.xml.namespace.QName.getPrefix with WSDL2Java

[Cooper, Jeremy]

I just had the same problem.  Basically I had another version of Qname
in my classpath.  Specifically it was located in my weblogic.jar.  

Ensure that the jaxrpc.jar is first in your classpath.  Also I used the
class below to search the classpath entries to find our where references
were getting resolved.

Hope this helps...
Jeremy


/*
 * Copyright (C) 2001 Clarkware Consulting, Inc.
 * All Rights Reserved.
 * 
 * Redistribution and use in source and binary forms, with or without 
 * modification, are permitted provided that the following conditions 
 * are met:
 *
 *  1. Redistributions of source code must retain the above copyright
 * notice, this list of conditions and the following disclaimer.
 *
 *  2. Redistributions in binary form must reproduce the above copyright

 * notice, this list of conditions and the following disclaimer in
the 
 * documentation and/or other materials provided with the
distribution.
 *
 *  3. Neither the name of Clarkware Consulting, Inc. nor the names of
its 
 * contributors may be used to endorse or promote products derived 
 * from this software without prior written permission. For written 
 * permission, please contact [EMAIL PROTECTED]
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES,
 * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND
 * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL
 * CLARKWARE CONSULTING OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, 
 * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT 
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, 
 * OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF 
 * LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
 * NEGLIGENCE OR OTHERWISE) ARISING IN  ANY WAY OUT OF THE USE OF THIS 
 * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

import java.io.*;
import java.net.URL;
import java.util.StringTokenizer;

/**
 * JWhich is a utility that takes a Java class name 
 * and displays the absolute pathname of the class file that would 
 * be loaded first by the class loader, as prescribed by the
 * class path.
 * 
 * JWhich also validates the class path and reports
 * any non-existent or invalid class path entries.
 * 
 * Usage is similar to the UNIX which command.
 * 
 * Example uses:
 * 
 * 
 *  To find the absolute pathname of
MyClass.class
 *  not in a package:
 *  java JWhich MyClass
 *
 *  To find the absolute pathname of
MyClass.class
 *  in the my.package package:
 *  java JWhich my.package.MyClass
 * 
 *
 * @author mailto:[EMAIL PROTECTED]">Mike Clark
 * @author http://www.clarkware.com";>Clarkware Consulting,
Inc.
 */

public class JWhich {

private static String CLASSPATH;

/**
 * Prints the absolute pathname of the class file 
 * containing the specified class name, as prescribed
 * by the class path.
 *
 * @param className Name of the class.
 */
public static void which(String className) {

URL classUrl = findClass(className);

if (classUrl == null) {
System.out.println("\nClass '" + className + 
"' not found.");
} else {
System.out.println("\nClass '" + className + 
"' found in \n'" + classUrl.getFile() +
"'");
}

validate();

printClasspath();
}

/**
 * Returns the URL of the resource denoted by the specified
 * class name, as prescribed by the class path.
 *
 * @param className Name of the class.
 * @return Class URL, or null of the class was not found.
 */
public static URL findClass(final String className) {
return
JWhich.class.getResource(asResourceName(className));
}

protected static String asResourceName(String resource) {
if (!resource.startsWith("/")) {
resource = "/" + resource;
}
resource = resource.replace('.', '/');
resource = resource + ".class";
return resource;
}

/**
 * Validates the class path and reports any non-existent
 * or invalid class path entries.
 * 
 * Valid class path entries include directories,
.zip 
 * files, and .jar files.
 */
public static void validate() {

StringTokenizer tokenizer = 
new StringTokenizer(getClasspath(),
File.pathSeparator);

while (tokenizer.hasMoreTokens()) {
String element

Re: [AXIS2] service implementation / clustering

[Davanum Srinivas]

Tony,

Yes, you are right. We need to clean this up. Could you please start
with a JIRA?

- I don't think we have an interface corresponding to the init.
- Yes, it is for every operation call.
- No, we don't have a destroy() AFAIK.

thanks,
dims

On 12/16/05, Tony Dean <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have been using the "public void init()" method of my service implemenation 
> to perform one-time initialization.  I can't remember how I stumbled across 
> this functionality, but it would be nice for you to define an implemenation 
> interface that describes this functionality.  Maybe you have and I just do 
> not know about it.  When I tested my service, it appeared that the engine 
> called init() on every operation invocation.  I did not spend much time 
> looking through the code so I'm asking how you conceptually designed these 
> semantics?  In particular, how many instances of a particular service will be 
> instantiated by the engine?  The init() method should only be called once 
> when the service is initally instantiated.  Will the engine be able to 
> quiesce unused service instances?  These are the semantics that are usually 
> derived from the container itself.  Also, suppose I have some initialization 
> code that needs to be done once and can be shared among all of my service 
> instances
> (singleton functionality).  How can I accomplish this... for instance, is 
> there a way to tell how many instances of myself have been instantiated?  
> Lastly, is there an analogous "public void destroy()" that can be used to 
> release any required resources obtained by my service?
>
> Thank you very much.
>
> Tony Dean
> SAS Institute Inc.
> 919.531.6704
> [EMAIL PROTECTED]
>
> SAS... The Power to Know
> http://www.sas.com
>
>


--
Davanum Srinivas : http://wso2.com/blogs/

[jira] Created: (AXIS-2343) NoSuchMethodError:javax.xml.namespace.QName.getPrefix with WSDL2Java

[uwe kraemer (JIRA)]

NoSuchMethodError:javax.xml.namespace.QName.getPrefix with WSDL2Java


 Key: AXIS-2343
 URL: http://issues.apache.org/jira/browse/AXIS-2343
 Project: Apache Axis
Type: Bug
  Components: WSDL processing  
Versions: 1.3
 Environment: Windows2000, jdk1.4.2, AXIS1.3, bug also with AXIS1.4 nightly 
built
Reporter: uwe kraemer


By creating java classes with WSDL2Java occurs a very strange error:

D:\Java>java org.apache.axis.wsdl.WSDL2Java d:\java\AddressBook.wsdl
java.lang.NoSuchMethodError: javax.xml.namespace.QName.getPrefix()Ljava/lang/Str
ing;
at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithDifferentL
ocal(BackslashUtil.java:62)
at org.apache.axis.wsdl.symbolTable.BackslashUtil.getQNameWithBackslashl
essLocal(BackslashUtil.java:39)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populateServices(SymbolT
able.java:3078)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:745)
at org.apache.axis.wsdl.symbolTable.SymbolTable.add(SymbolTable.java:543
)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:518)
at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.jav
a:495)
at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
at java.lang.Thread.run(Thread.java:534)


This bug occurs with AXIS1.3 released and also with AXIS1.4 nightly built 
16.12.05

Any ideas, why??? 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Where do I get hold of CVS and List of libs that I need to compile and run it success.

[Parikh,Pratik]

Title: Where do I get hold of CVS and List of libs that I need to compile and run it success.






Hi Everyone,


    Where do I get hold of CVS and List of libs that I need to compile and run it success.


Thanks,

Parikh, Pratik | Software Engineer | Cerner Corporation | (1)-816-201-1298 | [EMAIL PROTECTED] | www.cerner.com





CONFIDENTIALITY NOTICE

This message and any included attachments
are from Cerner Corporation and are intended
only for the addressee. The information
contained in this message is confidential and
may constitute inside or non-public information
under international, federal, or state
securities laws. Unauthorized forwarding,
printing, copying, distribution, or use of such
information is strictly prohibited and may be
unlawful. If you are not the addressee, please
promptly delete this message and notify the
sender of the delivery error by e-mail or you
may call Cerner's corporate offices in Kansas
City, Missouri, U.S.A at (+1) (816)221-1024.
 --

Re: setBody() and setHeader() problem in Axis 1.2 RC3

[dyemme]

Hi Jaya,

It didn't through the exception in my case but it sets the body and
header empty. Request envelope has both body and header but response
envelope is empty.

Thanks,
Damodar.

On Fri, 2005-12-16 at 17:36 +0530, jayachandra wrote:
> Hi Damodar,
> Did u get some exception like the following...
>  
> javax.xml.soap.SOAPException: javax.xml.soap.SOAPException:
> org.w3c.dom.DOMExcep
> tion: NodeImpl Not found
> at org.apache.axis.message.SOAPBody.setParentElement
> (SOAPBody.java :91)
> at org.apache.axis.message.SOAPEnvelope.setBody
> (SOAPEnvelope.java:309)
> at mytest.soapenvelope.TestSOAPEnvelope.setBody
> (TestSOAPEnvelope.java:16
> )
> at mytest.soapenvelope.TestSOAPEnvelope.main
> (TestSOAPEnvelope.java:40)
> Caused by: javax.xml.soap.SOAPException: org.w3c.dom.DOMException:
> NodeImpl Not
> found
> at org.apache.axis.message.NodeImpl.setParentElement
> (NodeImpl.java:634)
> at org.apache.axis.message.SOAPBody.setParentElement
> (SOAPBody.java:88)
> ... 3 more
> Caused by: org.w3c.dom.DOMException: NodeImpl Not found
> at org.apache.axis.message.NodeImpl.removeChild
> (NodeImpl.java:515)
> at org.apache.axis.message.SOAPEnvelope.removeChild
> (SOAPEnvelope.java:61
> 7)
> at org.apache.axis.message.NodeImpl.detachNode
> (NodeImpl.java:661)
> at org.apache.axis.message.NodeImpl.appendChild
> (NodeImpl.java:493)
> at org.apache.axis.message.NodeImpl.setParent
> (NodeImpl.java:792)
> at org.apache.axis.message.NodeImpl.setParentElement
> (NodeImpl.java:632)
> ... 4 more
> 
> I want to make sure I reproduced your problem properly.
>  
> Thanks
> Jaya
>  
> On 12/15/05, dyemme <[EMAIL PROTECTED]> wrote: 
> Hi Tom,
> 
> It didn't work with Axis 1.3 Final either. It works only with
> Axis 1.2
> Beta and older versions. I don't what changes they made to the
> latest 
> releases.
> 
> Thanks,
> Damodar.
> 
> On Wed, 2005-12-14 at 12:27 -0800, Tom Jordahl wrote:
> > Why don't you try the 1.3 final release or a build of the
> current source
> > tree and see if the problem is fixed. 
> >
> > --
> > Tom Jordahl
> > Adobe ColdFusion Team
> >
> > > -Original Message-
> > > From: dyemme [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, December 14, 2005 10:55 AM 
> > > To: axis-dev@ws.apache.org
> > > Subject: Re: setBody() and setHeader() problem in Axis 1.2
> RC3
> > >
> > > Hi All,
> > >
> > > Can anybody (axis core development team) through some
> light on this 
> > > issue?
> > >
> > > These methods work perfectly in Axis1.2 Beta and not in
> Axis1.2 RC1.3.
> > > It might be a bug or issue in AXIS. Right now these
> methods are
> > setting
> > > null into SOAP Message. 
> > >
> > > Thanks,
> > > Damodar.
> > >
> > > On Tue, 2005-12-13 at 11:47 -0500, dyemme wrote:
> > > > Hi,
> > > >
> > > > I have a problem with two methods in the Axis latest
> release and I 
> > don't
> > > > have this problem in the Axis 1.2 Beta versions. The
> setBody() and
> > > > setHeader() methods in the SOAPEnvelope are not working
> properly in
> > > > latest Axis release. Is there any substitute to this
> methods in the 
> > > > latest release?.
> > > >
> > > > Thanks,
> > > > Damodar.
> > > >
> > > > Here are the details.
> > > >
> > > > public void wsInfraProcessMethod(SOAPEnvelope req,
> SOAPEnvelope 
> > resp) {
> > > > if (req.toString().indexOf(
> > > >  WsrmServiceParameters.getApplicationMessage
> ()) != -1) {
> > > >   SOAPBody soapBody = null;
> > > >   SOAPHeader soapHeader = null; 
> > > >   try {
> > > > soapBody = (SOAPBody) req.getBody();
> > > > soapHeader = (SOAPHeader) req.getHeader();
> > > >   }
> > > >   catch (SOAPException ex) { 
> > > > ex.printStackTrace();
> > > >   }
> > > >
> > > >  resp.setBody(soapBody);
> > > >  resp.setHeader(soapHeader);
> > > >
> > > > 
> > > >   System.out.println
> ( "*");
> > > >   System.out.println(moduleName + " Sending message
> reliably \n"
> > +
> > > > resp); 
> > > >   System.out.println
> (  "*");
> > > > }
> > > > if (req.toString().indexOf(
> > > > Wsrm

java.lang.ClassCastException on invoke()

[Thiasos]

Hi,

 

First of all, excuse me for bad English!

 

We're trying to use Axis 
1.3 with JAXB 1.5 on java 1.4.2_05
 

We receive an error on 
invoke()
:
 

[java] 1750 [main] DEBUG 
org.apache.axis.enterprise  - Mapping Exception to AxisFault
[java] java.lang.ClassCastException

[java] at org.apache.axis.message.SOAPBody.getFirstBody
(SOAPBody.java:163)
[java] at org.apache.axis.message.SOAPEnvelope.getFirstBody
(SOAPEnvelope.java:191)
[java] at org.apache.axis.client.Call.invoke
(Call.java:2701)
[java] at org.apache.axis.client.Call.invoke
(Call.java:1871)
[java] at org.apache.axis.soap.SOAPConnectionImpl.call
(SOAPConnectionImpl.java:90)
[java] at MM7TestNoAuto.testSend
(MM7TestNoAuto.java:73)
…

 

We've created the SOAP Message in this way:

 

private SOAPMessage createSoapMessage() throws Exception {

  SOAPMessage msg;

  TransactionID tid = 
objFactory.createTransactionID();
  tid.setValue("prova");

  AddressType sender = 
objFactory.createAddressType();
  AddressGroupRFC2822AddressType senderAdd = 
objFactory.createAddressGroupRFC2822AddressType();
  ContentReferenceType cRef = 
objFactory.createContentReferenceType();
  cRef.setHref("cid:forecast-location200102-86453");

  senderAdd.setValue("00393357534229");

  sender.setRFC2822Address
(senderAdd);
  DeliverReq deliveryReq = 
objFactory.createDeliverReq();
  deliveryReq.setMM7Version
("6.8.0");
  deliveryReq.setVASID
("Reminder");
  deliveryReq.setVASPID
("TNN");
  deliveryReq.setMMSRelayServerID
("240.110.75.34");
  deliveryReq.setSender
(sender);
  deliveryReq.setContent
(cRef);
  msg = msgFactory.createMessage
();
  mm7Context.createMarshaller
().marshal(tid, msg.getSOAPHeader());
  mm7Context.createMarshaller
().marshal(deliveryReq, msg.getSOAPBody());
  return msg;

}
 

JAXB ignite the Element as MessageElement (that is created by method 
createElement(String tagName)
 in 
SOAPDocumentImpl) in the Body, but on invoke() Axis try to cast to a SOAPBodyElement when prepare the message for send (see the ExceptionStackTrace).

 

The method 

getFirstBody()  do the following:

 

SOAPBodyElement getFirstBody() throws AxisFault

{

    if (!hasChildNodes())

    return null;

    return (SOAPBodyElement)getChildren().get(0);
}
 

 

But all class using the result of the method use only method from MessageElement and not one of SOAPBodyElement.

 

We've solved modifying changing the method signature change return type to MessageElement (and, consequently, the object instance in all class calling this method).

 

This work perfectly but the question is: Is this correct? Why the return type of method is a SOAPBodyElement and not a MessageElement?

 

Any suggestion to solve without Axis source modification? 

 

Thanks in advance,

 

Andrea Lambruschini and Bruno Lombardi

[AXIS2] service implementation / clustering

[Tony Dean]

Hi,

I have been using the "public void init()" method of my service implemenation 
to perform one-time initialization.  I can't remember how I stumbled across 
this functionality, but it would be nice for you to define an implemenation 
interface that describes this functionality.  Maybe you have and I just do not 
know about it.  When I tested my service, it appeared that the engine called 
init() on every operation invocation.  I did not spend much time looking 
through the code so I'm asking how you conceptually designed these semantics?  
In particular, how many instances of a particular service will be instantiated 
by the engine?  The init() method should only be called once when the service 
is initally instantiated.  Will the engine be able to quiesce unused service 
instances?  These are the semantics that are usually derived from the container 
itself.  Also, suppose I have some initialization code that needs to be done 
once and can be shared among all of my service instances
(singleton functionality).  How can I accomplish this... for instance, is there 
a way to tell how many instances of myself have been instantiated?  Lastly, is 
there an analogous "public void destroy()" that can be used to release any 
required resources obtained by my service?

Thank you very much.

Tony Dean
SAS Institute Inc.
919.531.6704
[EMAIL PROTECTED]

SAS... The Power to Know
http://www.sas.com

Trans.: Urgent: Axis 1.3 BasicAuthentication and CommonsHTTPSender problem

[Slimane AMAR]

- Message transféré de Slimane AMAR <[EMAIL PROTECTED]> -
   Date : Fri, 16 Dec 2005 13:41:27 +0100
 De : Slimane AMAR <[EMAIL PROTECTED]>
Adresse de retour :axis-user@ws.apache.org
  Sujet : Urgent: Axis 1.3 BasicAuthentication and CommonsHTTPSender problem
  À : axis-user@ws.apache.org, axis-dev@ws.apache.org

Hello

I have the same problem :
http://marc.theaimsgroup.com/?l=axis-dev&m=111891561125089

The problem is due to commonsHTTPclient.
HttpClient doesn't use by default the preemptive
authentication :
http://jakarta.apache.org/commons/httpclient/authentication.html

To solve this problem the question is :
Is it possible to specify a property to use
the preemptive authentication with commonsHTTPclient
from Axis ?

>I am sending again my problem

>I am using Axis 1.3, tomcat 5.5.12, java 1.5.

>I am using a client-deploy.wsdd that points to CommonHTTPSender
>transport so my axis client can use Http 1.1. I am
>also using commonsHTTPclient-3.0-rc4.jar and commonsCodec-1-3.jar.

>My web service is using those two handlers for authentication:
>
>   type="java:org.apache.axis.handlers.SimpleAuthenticationHandler"/>
>   type="java:org.apache.axis.handlers.SimpleAuthorizationHandler"/>
>.

>I also set the userName and password for my Call object. Also set
>setMaintainSession(true).

>The problem is:

>When the client sends the message it is not authorized (HTTP/1.1 401
>Unauthorized). But the client sends
>automatically the same message again, and now it is authorized.

>Running ethereal I saw in the Http Header that in the first message
>there is not a "Authorization: Basic + some hexadecimal stuff" entry.
>The Http header response has the follow entry: WWW-Authenticate: Basic
>realm="AXIS". I did not set this realm at any place (tomcat
>configuration file or the axis server side).

>At the axis fault string I have: User 'null' not
>authenticated (unknown user).

>As I said I set the user name and password (Ah, the user name and
>password exists at users.lst). Only one detail. Debugging I saw that
>in the messageContext object, at the client side, that the user name
>and password were empty. So in my stub I also set userName and
>password for the messageContext. See the code below:

>_call.getMessageContext().setUsername(userName);

>_call.getMessageContext().setPassword(passWord);

>The second message, that is the first one sent again, goes with the
>Authorization entry at the Http header. The credentials: user name and
>password, are filled. So, the message is authorized.

>At last, when I use http 1.0 and HTTPSender I do not have the
>authentication problem and
>the message´s duplication problem.

>With this problem, when I use http 1.1 (using CommonsHTTPSender)my web
>service is slower than
>with http 1.0 (using HTTPSender) even running it at a local network

>Could anyone help me? What is going on?

>Thx,

>Fabrizzio Cabral de Lacerda


--
Slimane AMAR Mail: [EMAIL PROTECTED]
GENIGRAPHURL : http://www.genigraph.fr
104, rue Castagnary  Tel : +33 01 45 33 64 63
F-75015 PARIS FRANCE Fax : +33 01 45 33 89 63
--

- Fin du message transféré -


--
Slimane AMAR Mail: [EMAIL PROTECTED]
GENIGRAPHURL : http://www.genigraph.fr
104, rue Castagnary  Tel : +33 01 45 33 64 63
F-75015 PARIS FRANCE Fax : +33 01 45 33 89 63
--

Re: setBody() and setHeader() problem in Axis 1.2 RC3

[jayachandra]

Hi Damodar,
Did u get some exception like the following...
 
javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: org.w3c.dom.DOMException: NodeImpl Not found    at org.apache.axis.message.SOAPBody.setParentElement(SOAPBody.java
:91)    at org.apache.axis.message.SOAPEnvelope.setBody(SOAPEnvelope.java:309)    at mytest.soapenvelope.TestSOAPEnvelope.setBody(TestSOAPEnvelope.java:16)    at mytest.soapenvelope.TestSOAPEnvelope.main
(TestSOAPEnvelope.java:40)Caused by: javax.xml.soap.SOAPException: org.w3c.dom.DOMException: NodeImpl Notfound    at org.apache.axis.message.NodeImpl.setParentElement(NodeImpl.java:634)    at org.apache.axis.message.SOAPBody.setParentElement
(SOAPBody.java:88)    ... 3 moreCaused by: org.w3c.dom.DOMException: NodeImpl Not found    at org.apache.axis.message.NodeImpl.removeChild(NodeImpl.java:515)    at org.apache.axis.message.SOAPEnvelope.removeChild
(SOAPEnvelope.java:617)    at org.apache.axis.message.NodeImpl.detachNode(NodeImpl.java:661)    at org.apache.axis.message.NodeImpl.appendChild(NodeImpl.java:493)    at org.apache.axis.message.NodeImpl.setParent
(NodeImpl.java:792)    at org.apache.axis.message.NodeImpl.setParentElement(NodeImpl.java:632)    ... 4 more
I want to make sure I reproduced your problem properly.
 
Thanks
Jaya 
On 12/15/05, dyemme <[EMAIL PROTECTED]> wrote:
Hi Tom,It didn't work with Axis 1.3 Final either. It works only with Axis 1.2Beta and older versions. I don't what changes they made to the latest
releases.Thanks,Damodar.On Wed, 2005-12-14 at 12:27 -0800, Tom Jordahl wrote:> Why don't you try the 1.3 final release or a build of the current source> tree and see if the problem is fixed.
>> --> Tom Jordahl> Adobe ColdFusion Team>> > -Original Message-> > From: dyemme [mailto:[EMAIL PROTECTED]]> > Sent: Wednesday, December 14, 2005 10:55 AM
> > To: axis-dev@ws.apache.org> > Subject: Re: setBody() and setHeader() problem in Axis 1.2 RC3> >> > Hi All,> >> > Can anybody (axis core development team) through some light on this
> > issue?> >> > These methods work perfectly in Axis1.2 Beta and not in Axis1.2 RC1.3.> > It might be a bug or issue in AXIS. Right now these methods are> setting> > null into SOAP Message.
> >> > Thanks,> > Damodar.> >> > On Tue, 2005-12-13 at 11:47 -0500, dyemme wrote:> > > Hi,> > >> > > I have a problem with two methods in the Axis latest release and I
> don't> > > have this problem in the Axis 1.2 Beta versions. The setBody() and> > > setHeader() methods in the SOAPEnvelope are not working properly in> > > latest Axis release. Is there any substitute to this methods in the
> > > latest release?.> > >> > > Thanks,> > > Damodar.> > >> > > Here are the details.> > >> > > public void wsInfraProcessMethod(SOAPEnvelope req, SOAPEnvelope
> resp) {> > > if (req.toString().indexOf(> > >  WsrmServiceParameters.getApplicationMessage()) != -1) {> > >   SOAPBody soapBody = null;> > >   SOAPHeader soapHeader = null;
> > >   try {> > > soapBody = (SOAPBody) req.getBody();> > > soapHeader = (SOAPHeader) req.getHeader();> > >   }> > >   catch (SOAPException ex) {
> > > ex.printStackTrace();> > >   }> > >> > >  resp.setBody(soapBody);> > >  resp.setHeader(soapHeader);> > >> > >
> > >   System.out.println( "*");> > >   System.out.println(moduleName + " Sending message reliably \n"> +> > > resp);
> > >   System.out.println(  "*");> > > }> > > if (req.toString().indexOf(> > > WsrmServiceParameters.getResponseMessage
()) != -1) {> > >> System.out.println("");> > >   System.out.println(moduleName + "  Message has been received> \n"
> > > + req);> > >> System.out.println("*");> > > }> > >   }> > >>
-- -- Jaya 

Re: setBody() and setHeader() problem in Axis 1.2 RC3

[Venkat Reddy]

The five junit test cases inside test.message.TestSOAPEnvelope run
fine for me, so getBody seems to work fine. The test cases might be
missing the issue that you are facing. It will help if you could
submit a test case to reproduce the problem.

thanks
venkat

On 12/15/05, dyemme <[EMAIL PROTECTED]> wrote:
> Hi Tom,
>
> It didn't work with Axis 1.3 Final either. It works only with Axis 1.2
> Beta and older versions. I don't what changes they made to the latest
> releases.
>
> Thanks,
> Damodar.
>
> On Wed, 2005-12-14 at 12:27 -0800, Tom Jordahl wrote:
> > Why don't you try the 1.3 final release or a build of the current source
> > tree and see if the problem is fixed.
> >
> > --
> > Tom Jordahl
> > Adobe ColdFusion Team
> >
> > > -Original Message-
> > > From: dyemme [mailto:[EMAIL PROTECTED]
> > > Sent: Wednesday, December 14, 2005 10:55 AM
> > > To: axis-dev@ws.apache.org
> > > Subject: Re: setBody() and setHeader() problem in Axis 1.2 RC3
> > >
> > > Hi All,
> > >
> > > Can anybody (axis core development team) through some light on this
> > > issue?
> > >
> > > These methods work perfectly in Axis1.2 Beta and not in Axis1.2 RC1.3.
> > > It might be a bug or issue in AXIS. Right now these methods are
> > setting
> > > null into SOAP Message.
> > >
> > > Thanks,
> > > Damodar.
> > >
> > > On Tue, 2005-12-13 at 11:47 -0500, dyemme wrote:
> > > > Hi,
> > > >
> > > > I have a problem with two methods in the Axis latest release and I
> > don't
> > > > have this problem in the Axis 1.2 Beta versions. The setBody() and
> > > > setHeader() methods in the SOAPEnvelope are not working properly in
> > > > latest Axis release. Is there any substitute to this methods in the
> > > > latest release?.
> > > >
> > > > Thanks,
> > > > Damodar.
> > > >
> > > > Here are the details.
> > > >
> > > > public void wsInfraProcessMethod(SOAPEnvelope req, SOAPEnvelope
> > resp) {
> > > > if (req.toString().indexOf(
> > > >  WsrmServiceParameters.getApplicationMessage()) != -1) {
> > > >   SOAPBody soapBody = null;
> > > >   SOAPHeader soapHeader = null;
> > > >   try {
> > > > soapBody = (SOAPBody) req.getBody();
> > > > soapHeader = (SOAPHeader) req.getHeader();
> > > >   }
> > > >   catch (SOAPException ex) {
> > > > ex.printStackTrace();
> > > >   }
> > > >
> > > >  resp.setBody(soapBody);
> > > >  resp.setHeader(soapHeader);
> > > >
> > > >
> > > >   System.out.println( "*");
> > > >   System.out.println(moduleName + " Sending message reliably \n"
> > +
> > > > resp);
> > > >   System.out.println(  "*");
> > > > }
> > > > if (req.toString().indexOf(
> > > > WsrmServiceParameters.getResponseMessage()) != -1) {
> > > >
> > System.out.println("");
> > > >   System.out.println(moduleName + "  Message has been received
> > \n"
> > > > + req);
> > > >
> > System.out.println("*");
> > > > }
> > > >   }
> > > >
> >
>
>