[ http://issues.apache.org/jira/browse/AXIS2-132?page=all ]
Davanum Srinivas resolved AXIS2-132:
Resolution: Fixed
done.
> WS-Addressing versions
> --
>
> Key: AXIS2-132
> URL: http://issues.apache.org/jira
[ http://issues.apache.org/jira/browse/AXIS2-227?page=all ]
Eran Chinthaka resolved AXIS2-227:
--
Fix Version: 0.95
Resolution: Fixed
Completed with the success of WS-A interop done in W3C
> Implement completed WSA 1.0 specification
> -
[ http://issues.apache.org/jira/browse/AXIS2-377?page=all ]
Eran Chinthaka resolved AXIS2-377:
--
Fix Version: 0.95
Resolution: Fixed
Resolved this some time back.
> remove unused/redundant interfaces
> --
>
>
[ http://issues.apache.org/jira/browse/AXIS2-246?page=all ]
Eran Chinthaka resolved AXIS2-246:
--
Resolution: Fixed
> WS-Addressing namespaces not being set up right in wsa:action header
> -
[
http://issues.apache.org/jira/browse/AXIS2-132?page=comments#action_12369807 ]
Eran Chinthaka commented on AXIS2-132:
--
Can we close this as we now support WS-A CR and WS-A 2004/08 ?
> WS-Addressing versions
> --
>
> Key:
[
http://issues.apache.org/jira/browse/AXIS-2054?page=comments#action_12369806 ]
zhou guoku commented on AXIS-2054:
--
I am also facing the same issue whith Axis 1.2.1 Release.For avoid this
problem，what can i do.
By the way, why there is not a Fix Verson.
Hi Tony,
Seems like you have tried to create the faults using SOAP 1.1 api.
You may also agree that the fault hierarchy in SOAP 1.1 and 1.2 are
different. So some time back we decided to have the SOAP 1.2 api across
the engine for consistency and developer convenience. Users must always
create al
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Forwarded to Axis2 Dev list with [Axis2] prefix.
Morten Mortensen wrote:
>
> Hi all developers
>
> Just tried Axis2 0.94 today - or a part of it - and of course installed
> it in a path like -
> C:\Program Files\Apache Software Foundation\Axis2\0.94
The problem is due to stub keep static axisService instance in it
any way this is wt i encountered
Previously when engage a module if it is already engaged then it
just ignore that , but there was a JIRA in the list and when I fixed
that all the security test case were failing with the excepti
[ http://issues.apache.org/jira/browse/AXIS2-378?page=all ]
Deepal Jayasinghe resolved AXIS2-378:
-
Fix Version: 0.95
Resolution: Fixed
done
> Unusual behaviour in Axis2 web app
> --
>
> Key: AXIS2-3
[ http://issues.apache.org/jira/browse/AXIS2-319?page=all ]
Deepal Jayasinghe resolved AXIS2-319:
-
Fix Version: 0.95
Resolution: Fixed
Thx for poiniting out that ,
Now I can see in http://ws.apache.org/ they have put a link to Axis
[ http://issues.apache.org/jira/browse/AXIS2-187?page=all ]
Deepal Jayasinghe resolved AXIS2-187:
-
Fix Version: 0.95
Resolution: Fixed
Done have a look at
AsyncServiceTest
> Need a integration test for the non blocking two channel used
[ http://issues.apache.org/jira/browse/AXIS2-485?page=all ]
Deepal Jayasinghe reassigned AXIS2-485:
---
Assign To: Chatra Nakkawita
Great work (I think you can commite the code since now you are commiter)
> more migration guide docs for databinding
[ http://issues.apache.org/jira/browse/AXIS2-460?page=all ]
Deepal Jayasinghe resolved AXIS2-460:
-
Fix Version: 0.95
Resolution: Fixed
Done ,
if you want to give your host name (complete URL) then add following parameter
into transport sp
XMLBeans truncates dateTime values
--
Key: AXIS2-487
URL: http://issues.apache.org/jira/browse/AXIS2-487
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: databinding
Reporter: Ajith Harshana Ranabahu
Assigned to: Ajith H
Hi,
What is wrong with the following:
SOAPFactory soapFactory = OMAbstractFactory.getSOAP11Factory();
SOAPEnvelope soapEnvelope = soapFactory.createSOAPEnvelope();
SOAPBody soapBody = soapFactory.createSOAPBody(soapEnvelope);
SOAPFau
Axis2 Client does not validate the content type of incoming messages
Key: AXIS2-486
URL: http://issues.apache.org/jira/browse/AXIS2-486
Project: Apache Axis 2.0 (Axis2)
Type: Bug
Components: trans
[ http://issues.apache.org/jira/browse/AXIS2-485?page=all ]
robert lazarski updated AXIS2-485:
--
Attachment: patch2.txt
Just found a minor typo - should be ok now. Please review and apply this patch
instead.
> more migration guide docs for databinding
Title: Request: Quotation of command-line arguments
Hi all developers
Just tried Axis2 0.94 today - or a part of it - and of course installed it in a path like -
C:\Program Files\Apache Software Foundation\Axis2\0.94
- on my Windows machine and set AXIS_HOME accordingly.
I notice, tha
[ http://issues.apache.org/jira/browse/AXIS2-485?page=all ]
robert lazarski updated AXIS2-485:
--
Attachment: patch.txt
Here's the patch. Oh yeah - I tested the axis2 part with the latest svn, built
the war and used that for the examples.
It'd be great
more migration guide docs for databinding
-
Key: AXIS2-485
URL: http://issues.apache.org/jira/browse/AXIS2-485
Project: Apache Axis 2.0 (Axis2)
Type: Improvement
Components: samples, build,site & docs
Versions: 0.95
Title: Access to MessageContext
Can I access MessageContext object from the proxy java code that comes out of wsdl2java? I need it for logging purposes.
Thanks,
Anand
HTTP User-Agent for Axis should be same for both HTTPSender classes
---
Key: AXIS-2432
URL: http://issues.apache.org/jira/browse/AXIS-2432
Project: Apache Axis
Type: Improvement
Versions: 1.3
En
There was a service running at that endpoint (for the
soapbuilders interop testing) it has however been down for quite a while now,
previous attempts to prod people to get the endpoint active again have always
failed.
Perhaps the axis2 folks will put up an interop endpoint
?
Cheers
Simon
On Thu, 2006-03-09 at 22:15 +0600, Ruchith Fernando wrote:
>
> IMHO, for example we should be able to create two instances of the
> _same_ stub within a method and invoke them independently. Before
> modifying those security test cases this is the behaviour that we had.
> Can we make sure we have
Hi Deepal,
Please see my comments below:
On 3/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Author: deepal
> Date: Thu Mar 9 04:33:32 2006
> New Revision: 384499
>
> URL: http://svn.apache.org/viewcvs?rev=384499&view=rev
> Log:
> - I tryie fix the JIRA 379 , then all the test cases were
[
http://issues.apache.org/jira/browse/AXIS-2431?page=comments#action_12369651 ]
Lijun Liao commented on AXIS-2431:
--
The empty namespace will be added by AXIS to the element with non-default
namespace.
A document like
value of a
value of b
will
[ http://issues.apache.org/jira/browse/AXIS-2431?page=all ]
Lijun Liao updated AXIS-2431:
-
Attachment: DocumentWith2NSs.java
> Empty namespace added while serializing document with more than one namespace
> ---
Empty namespace added while serializing document with more than one namespace
-
Key: AXIS-2431
URL: http://issues.apache.org/jira/browse/AXIS-2431
Project: Apache Axis
Type: Bug
Components:
IMHO, for the benefit of the users, if deprecation and obsoleting
policies are defined, it would be great.
I mean, say you define a time period for obsoleting a deprecated
feature, rather than obsoleting in an ad-hoc manner, so that all know
how long a deprecated feature would be there before th
Problem in close_wait with invokeoneway
---
Key: AXIS-2430
URL: http://issues.apache.org/jira/browse/AXIS-2430
Project: Apache Axis
Type: Bug
Components: Basic Architecture
Versions: 1.2.1, 1.3
Environment: Linux suse
Thanks for reply, but this is not the way I can use :-(
I need generate exceptions binding with different names on the server or not
to generate XMLBeans for them ... and question is how to do it.
The best way will be to push AXIS2 generator to generate exception classes
with different name or do
Deepal ..I think you should ask the user list is lot of people using
it. If people had moved to service client you do not need to move them
to scracth .. just delete them. (But judging by the work I had to do
in moving to service client .. I belive there are lot still using it)
Srinath
On 3/9/06
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all;
As you know in the current SVN we have our old client side codes (Call
, InOutMEPClient etc..) and no body is using those, in fact they are
marked as deprecated.
So what if we move them to scratch area , keeping them in the main
source tree m
[
http://issues.apache.org/jira/browse/AXIS-2429?page=comments#action_12369633 ]
Erik Godding Boye commented on AXIS-2429:
-
When I run the generated JUnit test case that tests getting the WSDL file from
the server (TicketCentralTestCase#testTicketCe
Invalid WSDL created
Key: AXIS-2429
URL: http://issues.apache.org/jira/browse/AXIS-2429
Project: Apache Axis
Type: Bug
Versions: 1.2, 1.2.1, 1.3
Reporter: Erik Godding Boye
Priority: Minor
The WSDL created by Axis for my deploye
[ http://issues.apache.org/jira/browse/AXIS2-379?page=all ]
Deepal Jayasinghe resolved AXIS2-379:
-
Fix Version: 0.95
Resolution: Fixed
fixed
> Engaging same module more than once has no indication about it
> ---
[
http://issues.apache.org/jira/browse/AXIS-2348?page=comments#action_12369625 ]
Erik Godding Boye commented on AXIS-2348:
-
I am having similar problems after trying to upgrade from version 1.2.1 to
version 1.3. In my case it is a SOAP response cont
AXIS DIME attachments file
--
Key: AXIS-2428
URL: http://issues.apache.org/jira/browse/AXIS-2428
Project: Apache Axis
Type: Bug
Components: Basic Architecture
Versions: 1.3
Environment: Axis 1.3, Tomcat 5.0.28, JDK1.5.0_06, Window
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kenneth Tam wrote:
> I'm using JDK5 and am still building/testing (including the security
> tests) fine as of a sync in the last day or two.
>
> The security provider setting described in the FAQ is definitely
> necessary. BouncyCastle provides jars t
[
http://issues.apache.org/jira/browse/AXIS2-266?page=comments#action_12369611 ]
Kunal Parmar commented on AXIS2-266:
I am facing same problem.It that any workaround for this problem.
- Deploying module : addressing
org.apache.axis2.om.OMException: java
41 matches
Mail list logo
