Hi Josef:
Good question. :) We just had this very conversation on the WS dev list, and
the plan is indeed to put links from the WS site to the Axis project, so that
people will understand where things have gone and the history behind the
move. We'll get this in place sometime soon.
To clarify, A
Josef,
Please see below for answers:
> What if your server supports both SOAP protocols 1.1 and 1.2?
I am not too sure if it matters what the server supports as the below
o/p is captured using tpcmon. If the server has any issue with client
trying SOAP 1.2 while the server does not support it, the
>From the ServiceClient you can get the response message context.
serviceclient.getLastOperationContext().getMessageContext("In");
Deepal
On 11/8/2010 12:17 PM, Christopher Johnson wrote:
> All -
>
> I have a WS that responds with message using SOAP with attachments.
> In Axis1 you would get th
>
> No, dude, *you're* the one who appears to be claiming that there are
> many scenarios where Axis2 is "hugely better than CXF". I don't know
> what these scenarios are, and when I've asked for any kind of specifics
> you've said you're not going to waste your time helping me figure those
> out.
On Tue, Nov 2, 2010 at 11:13 PM, Dennis Sosnoski wrote:
> If the consensus of the Axis2 developers is to avoid any discussion of other
> alternatives on these lists I'll certainly respect that. But unless there is
> a policy to that effect I'll continue to mention other open source
> alternatives
Another Apache project is using Neethi and has support for
WS-Addressing 1.5. I haven't checked into the details of their
implementation, but they're currently distributing Neethi 2.0.4.
- Dennis
Also looks like its not even supported in Neethi yet .. and is on the
roadmap for Neethi 3.
Hi Katherine,
There's very little difference between the two, from what I've seen
(except for the namespace). But it'd be good to support both versions,
for compatibility with other tools. I'll add the Jira.
- Dennis
Hi Dennis,
I don't think the work has been done
to support
All -
I have a WS that responds with message using SOAP with attachments. In
Axis1 you would get the response message context from the MessageContext.
How do I go about retrieving the response message context to set attachments
in Axis2?
Thanks in advance!
..Chris
I do follow that list but I don't remember seeing it. Anyway, I will go through
the archives.
Thanks!
From: Sanjiva Weerawarana [mailto:sanj...@opensource.lk]
Sent: Monday, November 08, 2010 9:14 AM
To: java-user@axis.apache.org
Subject: Re: Axis2 code gen with WS-Policy 1.5?
Neethi is discusse
Neethi is discussed on d...@ws.apache.org .. there was a recent thread on 3.0
and alternative policies IIRC. Please ask there!
Sanjiva.
On Mon, Nov 8, 2010 at 9:13 PM, George Stanchev wrote:
> Neethi hasn’t had a release for almost 2 years now. Is there a publically
> available roadmap for 3.0?
Neethi hasn't had a release for almost 2 years now. Is there a publically
available roadmap for 3.0? Plans? I am looking forward support for alternative
policies which Neethi has been lacking.
From: Sanjiva Weerawarana [mailto:sanj...@opensource.lk]
Sent: Monday, November 08, 2010 8:37 AM
To: ja
Also looks like its not even supported in Neethi yet .. and is on the
roadmap for Neethi 3.0?
Sanjiva.
On Mon, Nov 8, 2010 at 9:01 PM, Katherine Sanders <
katherine_sand...@uk.ibm.com> wrote:
> Hi Dennis,
>
> I don't think the work has been done to support WS-Policy 1.5 in Axis2
> because the do
Hi Dennis,
I don't think the work has been done to support WS-Policy 1.5 in Axis2
because the documentation references the older WS-Policy 1.2 specification
(see the resources at the bottom of this page
http://ws.apache.org/axis2/1_5_1/WS_policy.html). Perhaps you could open
a Jira for this f
Allow me 3 questions:
What if your server supports both SOAP protocols 1.1 and 1.2?
Would then your client need to say which protocol shall be used actually?
What if your server allows to bind only to one SOAP 1.1 protocol?
Josef
-Ursprüngliche Nachricht-
Von: Prateek Asthana [mailto
Hello everyone,
In our project we have the exact same problem as the one described by
Josef in the e-mail below. I did not find any replies to his message.
Has this topic been addressed somewhere else? Is there a solution to
enforce soap session termination?
Thx
But why are you not keeping a link from Web Services to Axis2 unless the Axis2
by itself is done well?
OR is Axis2 not any longer considered a project belonging to Web Sercvice such
as Axisom é all others do?
Josef
-Ursprüngliche Nachricht-
Von: hemap...@gmail.com [mailto:hemap...@gmai
Hi,
I am trying to make my client use SOAP 1.2 but it always using the
SOAP 1.1. Below are more details Can someone please let me know the
use/intention of Options.setSoapVersionURI().
For the below client code:
public static void main(String[] args) throws MalformedURLException {
On Sun, Nov 7, 2010 at 12:00 PM, Dennis Sosnoski wrote:
>
> I don't know why you've reacted in this way, but you've disparaged my
professional reputation by accusing me of writing "articles that are
> intentionally damaging to Axis2." I'd like to see some substance to back
> up that statement.
>
hi Surya,
Both will use SOAP and will agree at the XML level. I do not see any
problems of having different versions for server and stubs.
--Srinath
On Sat, Nov 6, 2010 at 3:50 AM, Surya Subbiah wrote:
> Hi
> I recently upgraded my Axis2 client stubs from 1.4.1 to 1.5.2. Our webserver
> is runni
19 matches
Mail list logo
