Hi all;
I am going to implement module version supporting in Axis2 , meaning that
will allow to have different version of same module to be in the modules
directory and engage different versions to different services (or operations).
As an example there can be two addressing module in the
On Tue, 2005-12-27 at 09:39 +0100, Werner Dittmann wrote:
[X] - Don't switch on sessions by default
Well, I'm not an Axis developer, but makeing web services
statefull (session aware) by default is IMO not a good idea.
If some web services need session it should be done deliberatly
because
On Tue, 2005-12-27 at 14:26 +0600, Eran Chinthaka wrote:
Hi all,
Just wanted to give you an update on Axis2's performance in threading
environment.
I ran simple EchoRawXMLTest multiple times using threads. First I tried
this with the SimpleHTTPServer and then I deployed the service in
+1 for 0.94 release.
Sanjiva.
On Tue, 2005-12-27 at 20:51 +0600, Eran Chinthaka wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
After our last release on 2nd of December, I think we did enough work
to do the next release. We have improved some features during the
hackathon
On Thu, 2005-12-29 at 11:57 +0600, Ajith Ranabahu wrote:
Hi,
Yep, I will Chathura :)
Support for rpc/encoded is somewhat tricky, trickiest part being
supporting all the SOAPenc rules. Our current consensus is to NOT
support the whole set of encoding rules.
However 90% of the time the
On Thu, 2005-12-29 at 22:29 -0500, Srinath Perera wrote:
Hi All;
What does operation Clients do? Sorry if I sound negative.
1) But what is differance with them and the MEPClients?
2) Are they part of Client API? if so why they are necessary?
This is part of the client refactoring I
Hi,
I'm on the No sessions by default camp. My reasonsing is that the
common perception of Web services is that they are stateless. (Am I
wrong to assume that 90% of the services are percieved to be stateless,
at least the clients do not expect them to act in a stateless manner ?)
So if we attach
Hi guys, am thinking aloud here.
On the server side I firmly believe default choice should be 'NO SESSIONS', for the default notion of webservices is they are stateless.
Having said that, coming to the client side we have a couple of options
Option1: Client side sessions (what typeof sessions
Sanjiva,
A VOTE is a VOTE :) let's please live with it.
thanks,
dims
On 12/30/05, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Tue, 2005-12-27 at 09:39 +0100, Werner Dittmann wrote:
[X] - Don't switch on sessions by default
Well, I'm not an Axis developer, but makeing web services
Just noticed thisSorry, the VOTE inluded both sides,
A default server generated by WSDL2Java and a client generated by
WSDL2Java
So it's not just the client.
thanks,
dims
On 12/30/05, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Tue, 2005-12-27 at 09:39 +0100, Werner Dittmann wrote:
Jaya,
The deed is done, let's live with it for 0.94 at least.
thanks,
dims
On 12/30/05, jayachandra [EMAIL PROTECTED] wrote:
Hi guys, am thinking aloud here.
On the server side I firmly believe default choice should be 'NO SESSIONS',
for the default notion of webservices is they are
Sanjiva,
Just to explain a bit :)
A leak is when the method is finished the memory cannot be GC'ed.
consuming the memory unnecessarily means that during a method's
execution, it's taking more than appropriate what is needed :) Example
http://issues.apache.org/jira/browse/AXIS2-264 is not a leak.
How about X.YY.? where X means any thing that starts with X,
X.YY means anything that starts with X.YY and if they want it
super specific, they specify all digits. Also if nothing is specified
then we sort the mar's numerically and pick the latest.
thanks,
dims
On 12/30/05, Deepal Jayasinghe
For example my Windows Messenger is Version 7.5 (Build 7.5.0311) and
Latest HTTPD is 2.0.55 (2.0.5500 in our scheme) and Latest Tomcat is
5.5.12 (5.5.1200 in our scheme)
thanks,
dims
On 12/30/05, Davanum Srinivas [EMAIL PROTECTED] wrote:
How about X.YY.? where X means any thing that starts
On Fri, 2005-12-30 at 08:32 -0500, Davanum Srinivas wrote:
Sanjiva,
Just to explain a bit :)
A leak is when the method is finished the memory cannot be GC'ed.
consuming the memory unnecessarily means that during a method's
execution, it's taking more than appropriate what is needed :)
Already done. Your web site recommends posting patches to the mailing
list, so I did both.
-Original Message-
From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 29, 2005 11:56 PM
To: axis-dev@ws.apache.org
Subject: Re: patch for AXIS-2356
Please post it to JIRA.
Title: AXIS-2351
Hi Dims,
I have been email for this fix for ever, can you please reply and let me know what is going on with this. I need this fix in asap. Please let me know what needs to be done or what is going on??
Thanks,
Parikh, Pratik | Software Engineer | Cerner Corporation |
Pratik,
Sorry for the delay. Jaya and Venkat are chasing the build breakage,
can't do much till we fix the HEAD. If you can help with that it will
speed up things. Basically get ant clean all-tests working. The
branch is slightly better but there are failures there as well
Hi,
I'm trying to convert my previous axis services to axis2 to take
advantage of the async functionalities. Anyhow, I found that the
DeploymentClassLoader used offers very poor performance because it has
to go through all the lib jars for every class even when loading
multiple classes in
Forwarding with proper prefix.
Sanjiva.
---BeginMessage---
Hi,
I'm trying to convert my previous axis services to axis2 to take
advantage of the async functionalities. Anyhow, I found that the
DeploymentClassLoader used offers very poor performance because it has
to go through all the
I'd suggest also allowing the option of the service specifying a given
version *or later*, using something like X.YY+ as the notation. Seems
like that would handle the most common dependency cases, without
requiring a proliferation of specific versions.
- Dennis
Davanum Srinivas wrote:
Sanjiva Weerawarana wrote:
The question Dims asked is about what the default should be for clients.
I disagree with the apparently popular choice of no sessions because if
a service has multiple operations then in most cases the operations have
some relationships between them. The question
On Sat, 2005-12-31 at 17:59 +1300, Dennis Sosnoski wrote:
I'd suggest also allowing the option of the service specifying a given
version *or later*, using something like X.YY+ as the notation. Seems
like that would handle the most common dependency cases, without
requiring a proliferation
+1
On 12/31/05, Sanjiva Weerawarana [EMAIL PROTECTED] wrote:
On Sat, 2005-12-31 at 17:59 +1300, Dennis Sosnoski wrote:
I'd suggest also allowing the option of the service specifying a given
version *or later*, using something like X.YY+ as the notation. Seems
like that would handle the
On Sat, 2005-12-31 at 00:50 -0500, Davanum Srinivas wrote:
just reviewed the original email again...it talks about
xyz-00..mar hence the confusion.
So, we should go with say security-1.23.mar. Right? just to be absolutely
clear.
Right .. or security-1.235486.mar etc... basically we
I know I'm late :)Here are my views:1) Server sessions should be enabled by actual specific action of a developer or deployer2) Client sessions should be enabled by the following model: a) If the programmer repeatedly uses the same instance of the same stub then sessions will be *possible*.
b)
26 matches
Mail list logo
