performance benchmarks

[Mark Hansen]

Are there any performance benchmarks for Axis2 1.0 vs. Axis1 1.3 ??

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

Re: performance benchmarks

[Mark Hansen]

Congrats - that is an impressive performance improvement.  What is the 
primary reason for the big improvment?  Is it the Axiom pull parsing?  
Or just being smarter about minimizing the number of times a DOM gets 
copied?


Chathura Herath wrote:


http://www.wso2.net/2006/05/axis2_performance_testing_round_1

On 5/24/06, Mark Hansen [EMAIL PROTECTED] wrote:


Are there any performance benchmarks for Axis2 1.0 vs. Axis1 1.3 ??

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

schema for SOAP 1.2 ??

[Mark Hansen]

Sorry if this is slightly off-topic, but ...

Does anybody know where I can find an XML Schema definition of SOAP 1.2 ?

difference between rpc/lit and doc/lit

[Mark Hansen]

Is the only difference between rpc/lit and doc/lit that the rpc/lit 
style wraps the parameters (parts) in the method (operation) name?  Is 
the purpose of the rpc/lit style to use the method wrapper as a way to 
implement the WSDL allowed mapping of multiple binding ports to a single 
URL?


Thanks for any clarification,

Mark

Re: Axis vs Other App Containers

[Mark Hansen]

Axis is a great choice because if you switch
containers again, you can stick with Axis.  Also, it
is a lot simpler than dealing with all the overhead of
managing and deploying web services in a big bulky
J2EE container ... (my personal bias ...).

However, if you must manage your web services within
the container, say as EJBs, then have a look at the
the WSEE v1.1 specification (JSR-109).  Web Services
built and packaged this way should run in any J2EE
container.  Here is an article about it -
http://www-106.ibm.com/developerworks/webservices/library/ws-jsrart/

P.S.  you shouldn't have to regenerate the skeleton
classes for each new container as long as the entire
application - including the generated classes - are
packaged in your EAR.  Of course, if you change your
WSDL and regnerate using the tools from the new
container, then the results will be incompatible with
the older container's stuff.

--- Kiran Kumar [EMAIL PROTECTED] wrote:
 Hello friends, I need to provide some webservices in
 my web-application. Currently this application is on
 oracle 9iAS. They have plans to migrate this
 application on weblogic 8.1, but in near future. 
  
 I want to build the web services such a way that
 when I migrate to a different container, I don't
 have to change any code. 
  
 But once I generate the skeleton classes (server
 side) using 9iAS tools (Jbuilder..), I will edit the
 impl classes to call my business logic.. When I
 eventually switch to a different container, I will
 again have to generate the skeleton classes and may
 need to edit the impl classes and they may generate
 different class names also.
  
 So If I choose Axis, I won't have these problems. I
 just have to deploy the war file without changing
 any code. But I will be limited to what Axis
 provides, I will not be able to utilize any extra
 features provided by the container.
  
 I want to take your opinion whether to go with Axis
 in my scenario or put the effort to configure the
 web services when I switch to a different container.
  
 Sorry for long mail. I appreciate your help and
 time.
  
 Thanks
 Kiran
 
 
 
 This e-mail, and any attachments thereto, is
 confidential and is intended only for the
 individual(s) named.  If you are not the intended
 recipient, please let us know by e-mail reply and
 delete it from your system; do not copy/save this
 e-mail or disclose its contents to anyone.  E-mail
 transmissions cannot be guaranteed to be secure or
 error-free as the transmission could be interrupted,
 corrupted, lost, destroyed, altered, arrive late or
 contain viruses.  ObjectWave does not accept
 liability for any errors or omissions in the
 contents of this e-mail which arise as a result of
 e-mail transmission.  The views expressed in this
 e-mail do not necessarily reflect those of
 ObjectWave or its affiliates.
 
 
 
 
 

Re: Amazon and Axis

[Mark Hansen]

With respect to this issue:

 The problem was supposed to have been fixed some time ago:
 http://issues.apache.org/jira/browse/AXIS-530 :-)  Unfortunately the fix
 doesn't work, as can be seen by the above results from RC3. :-(  From
 this and other experiences with Axis releases (including the 1 year
 cycle for a point release) I'm starting to wonder if Axis has just
 gotten to be such a mess of spaghetti code that it's no longer usable in
 production. I've been training developers on Axis for some time. It's
 embarrassing to have to spend much of the training time discussing known
 issues and ways to work around them, but there doesn't appear to be any
 alternative at present.

Why don't you submit a patch?  There are more committers working on
Axis than there seem to have been in a while.  Like you, I've been
frustrated in the past, but things seem to be improving a bit.  Its
only going to get better if people like yourself, who understand the
inner workings of Axis, continue to submit patches.

-- Mark