[
http://issues.apache.org/jira/browse/AXIS2C-216?page=comments#action_12423779 ]
Samisa Abeysinghe commented on AXIS2C-216:
--
Sahan, on point 2; where it should go:
IMHO, it should not go to util, but rather to a new tools subfolder.
[ http://issues.apache.org/jira/browse/AXIS2C-197?page=all ]
Malinda Kaushalye Kapuruge updated AXIS2C-197:
--
Attachment: omxmlsec.tar
Pls add following files to omxmlsec.
Cheers,
Kau
OMXmlSec - The XML Security library for AXIOM [Phase1 :
[
http://issues.apache.org/jira/browse/AXIS2C-216?page=comments#action_12423785 ]
Sahan Gamage commented on AXIS2C-216:
-
So you're suggesting that the path would be $AXIS2_ROOT_DIR/tools/tcpmon ?
Sounds fine with me.
TCP Monitor
[ http://issues.apache.org/jira/browse/AXIS2C-197?page=all ]
Malinda Kaushalye Kapuruge updated AXIS2C-197:
--
Attachment: oxs_patch
Pls apply the following patch.
Cheers,
Kaushalye
OMXmlSec - The XML Security library for AXIOM [Phase1 :
[
http://issues.apache.org/jira/browse/AXIS2C-216?page=comments#action_12423830 ]
Ajith Harshana Ranabahu commented on AXIS2C-216:
Forgive me for barging in here but I guess tcpmon is better off as a generic
tool rather than
[
http://issues.apache.org/jira/browse/AXIS2C-216?page=comments#action_12423882 ]
Sahan Gamage commented on AXIS2C-216:
-
Ajith, the problem here we are facing is that the TCPMon heavily depends on the
util subproject under axis2c. If we
[ http://issues.apache.org/jira/browse/AXISCPP-949?page=all ]
nadir amra closed AXISCPP-949.
--
Resolution: Fixed
I guess one needs to go through the IPv6 leg to hit the problem. So there will
be a problem because if you pass in 36000 for uiPort (declared
Hi Jean;
The best way is
- First create configuration context
- Then create serviceClient / ServiceClients using that
- And use the those serviceClient to invoke the service
- In that case you wont get any exception
PS: Try to share same configurationContext across all the service
Hi,
Thanks I will try this.
Deepal Jayasinghe wrote:
Hi Jean;
The best way is
- First create configuration context
- Then create serviceClient / ServiceClients using that
- And use the those serviceClient to invoke the service
- In that case you wont get any exception
PS: Try
[ http://issues.apache.org/jira/browse/AXIS2-748?page=all ]
Deepal Jayasinghe resolved AXIS2-748.
-
Resolution: Fixed
Fixed in current SVN
AARWSDLLocator incorrect logic - may load incorrect files under certain
scenarios
[
http://issues.apache.org/jira/browse/AXIS2-936?page=comments#action_12423797 ]
Eran Chinthaka commented on AXIS2-936:
--
I just test the build in JDK 1.4 and JDK 1.5. I got the build successful. Can u
please re-check and comment on this?
[
http://issues.apache.org/jira/browse/AXIS2-548?page=comments#action_12423798 ]
Eran Chinthaka commented on AXIS2-548:
--
This patch is for Axis2 0_95 folder which is not in the code base anymore. I do
not see this in 1_0 folder.
Rajith,
[
http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423800 ]
Eran Chinthaka commented on AXIS2-789:
--
Hi,
+1 for the patch, except for the if (null == msgContext.getRelatesTo() ||
!(this instanceof OutInAxisOperation))
[
http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423802 ]
David Illsley commented on AXIS2-789:
-
Well that line is the important one
I agree that most web services start from a WSDL, with operations and
Hi,
After calling my service, instead of using Thread.sleep(1000), I'm
trying to use SandeshaClient.waitUntilSequenceCompleted(serviceClient).
At runtime, this exception is thrown :
org.apache.axis2.AxisFault: Default Sandesha Property Bean is not
available
What does that mean ?
[
http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423803 ]
Eran Chinthaka commented on AXIS2-789:
--
Ok, let me back off a bit :).
Since the spec doesn't say how to understand the relatesTo, I'd rather not
fault even
[
http://issues.apache.org/jira/browse/AXIS2-789?page=comments#action_12423819 ]
Davanum Srinivas commented on AXIS2-789:
Eran,
+1 from me FWIW, there was push back from Sanjiva
[
http://issues.apache.org/jira/browse/AXIS2-936?page=comments#action_12423820 ]
Davanum Srinivas commented on AXIS2-936:
it fails for me 100% of the time when i use JROCKIT 1.5. Basically i need to
run it twice, first to compile the
[ http://issues.apache.org/jira/browse/AXIS2-932?page=all ]
Deepal Jayasinghe reassigned AXIS2-932:
---
Assignee: Deepal Jayasinghe
axis2 doesn't receive null values correctly
---
Key:
Hello,
I work on the OGSA-DAI project and our current release is compatible with
Axis 1.2.1 and Axis 1.2RC3. In our installation guide we provide links
to the Axis download pages, but unfortunately all the download links
for these versions seem to be broken. See the links from these pages:
Please see http://archive.apache.org/
On 7/27/06, Tom Sugden [EMAIL PROTECTED] wrote:
Hello,
I work on the OGSA-DAI project and our current release is compatible with
Axis 1.2.1 and Axis 1.2RC3. In our installation guide we provide links
to the Axis download pages, but unfortunately all the
Title: Could not convert org.apache.axis.attachments.AttachmentPart
Hello!
I have been struggeling with implementing an MMS receiver according to the MM7 specification.
3GPP's MM7 interface defines an MM7 XML schema (namespace is
[
http://issues.apache.org/jira/browse/AXIS2-922?page=comments#action_12423863 ]
Dave Cowing commented on AXIS2-922:
---
Should be closed - not an issue - bad WSDL. Works with section in bindings and
unique elements for the fault messages.
Hi all,
I have posted this note to both the AXIS2 and SANDESHA developer discussion lists, so I apologize in advance to those folks who get multiple copies of this note.
I am investigating how to save and restore the message context in AXIS2. This is functionality that would be used by other
[ http://issues.apache.org/jira/browse/AXIS2-922?page=all ]
Davanum Srinivas resolved AXIS2-922.
Resolution: Invalid
marking as invalid as per reporter's comments.
WSDL2Java generates incorrect code for multiple faults
[ http://issues.apache.org/jira/browse/AXIS2-891?page=all ]
Brian DePradine updated AXIS2-891:
--
Attachment: newerpatch.txt
Hi,
I am attaching an updated patch that simplifies the code, and adds the new
property as a named constant in the
[
http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12423877 ]
Jeff Peterson commented on AXIS2-935:
-
I''ve done some more digging through the code and I am no longer convinced that
this is an issue with the
[
http://issues.apache.org/jira/browse/AXIS2-935?page=comments#action_12423880 ]
Jeff Peterson commented on AXIS2-935:
-
I forgot to mention, I noticed another interesting symptom. If I force the app
server to perform garbage collection
Nicholas,So sorry for the late reply, somehow I have missed it :-(Sorry to jump in the middle here, but
can you explain what the meta annotation is and from which spec files it
would be removed? I'm assuming you're talking about the JSR-181 spec
annotations declarations, but just wanted to make
[
http://issues.apache.org/jira/browse/AXIS-2386?page=comments#action_12423906 ]
Christine Chen commented on AXIS-2386:
--
This problem started to manifest after I switched the style (-y) from RPC to
WRAPPED when running java2wsdl (Axis 1.4)
[ http://issues.apache.org/jira/browse/AXIS2-937?page=all ]
William Ferguson updated AXIS2-937:
---
Attachment: JasperService.wsdl
The WSDL which wotks for Axis2-1.0 but not for the nightly build of 23-jul-06
WSDL2Java not generating parameters for
WSDL2Java not generating parameters for stib methods
Key: AXIS2-937
URL: http://issues.apache.org/jira/browse/AXIS2-937
Project: Apache Axis 2.0 (Axis2)
Issue Type: Bug
Hi,Using Axis 1.4, I generated code from a WSDL that referred to SOAP1.2. The code generated and the service deployed correctly and when I access the service and check the SOAP request/response messages they conform to the SOAP 1.2 standards.But when I try to use the ?wsdl option in the
I have a question regarding retrieving MessageContext with Axis2 in attempt to retrieve ServletContext.I used the following code in Axis1, which worked perfectly:MessageContext = MessageContext.getCurrentContext();HttpServlet servlet = (HttpServlet)
[ http://issues.apache.org/jira/browse/AXIS2-910?page=all ]
Bill Nagy resolved AXIS2-910.
-
Resolution: Fixed
JAXWS: Update AxisInvocationController to use the OperationClient instead of
the ServiceClient
Plugpoint to allow for migration between context and TLS
Key: AXIS2-938
URL: http://issues.apache.org/jira/browse/AXIS2-938
Project: Apache Axis 2.0 (Axis2)
Issue Type: New Feature
[ http://issues.apache.org/jira/browse/AXIS2-938?page=all ]
Bill Nagy updated AXIS2-938:
Attachment: tlsmigrator.patch
Plugpoint to allow for migration between context and TLS
Key:
This took a little longer than I would have liked, but I've opened a
JIRA issue (Axis2-938) and attached my patch. Comments are welcome.
-Bill
On Wed, 2006-07-12 at 14:20 -0400, Bill Nagy wrote:
Hi Sanjiva,
Logically, you can think of them as an extension to the handler
mechanism that runs
[
http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12423995 ]
Davanum Srinivas commented on AXIS2-938:
Here's my train of thought:
- 3 changes to classes under jaxws look ok.
- 3 new classes (ThreadContext*.java) look
Amit Patel wrote:
I have a question regarding retrieving MessageContext with Axis2 in
attempt to retrieve ServletContext.
I used the following code in Axis1, which worked perfectly:
MessageContext = MessageContext.getCurrentContext();
HttpServlet servlet = (HttpServlet) mycontext
40 matches
Mail list logo
