Hello Paul,
The Mail API which I used in the mail Trasnport sender is released under the
NPL licesense[1]. I wrote to mozilla foundataion and they said that if I am
going to use this mail API , then I need to release the part of the code
which use the mail API , under their license(NPL). That is
[
https://issues.apache.org/jira/browse/AXIS2C-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-557.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
Thanks for the explanation!
Paul
On 9/5/07, Rajika Kumarasiri [EMAIL PROTECTED] wrote:
Hello Paul,
The Mail API which I used in the mail Trasnport sender is released under the
NPL licesense[1]. I wrote to mozilla foundataion and they said that if I am
going to use this mail API , then I need
Savan fault handling and filter dialect support
---
Key: AXIS2C-688
URL: https://issues.apache.org/jira/browse/AXIS2C-688
Project: Axis2-C
Issue Type: Improvement
Reporter: Diluka
[
https://issues.apache.org/jira/browse/AXIS2C-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diluka Moratuwage updated AXIS2C-688:
-
Attachment: savan-filtering-faults.patch
Savan fault handling and filter dialect
Hi,
Is there planned support for SwA for the client in Axis2/C within the
very near future? A project I am working on requires that I support SwA,
as it doesn't support MTOM (and redeploying the service is not an
option).
If this is not planned, then would it be possible for you to give me
Jamie Lyon wrote:
Hi,
Is there planned support for SwA for the client in Axis2/C within the
very near future? A project I am working on requires that I support
SwA, as it doesn’t support MTOM (and redeploying the service is not an
option).
We do not have anyone working on it right now,
[
https://issues.apache.org/jira/browse/AXIS2C-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-561.
--
Resolution: Fixed
Fix Version/s: 1.1.0
Please use Axis2/Java 1.3 or later
[
https://issues.apache.org/jira/browse/AXIS2-2995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525010
]
Christian Meyer commented on AXIS2-2995:
I found another problem in the generated code of
[
https://issues.apache.org/jira/browse/AXIS2-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525011
]
Nikolaus Krismer commented on AXIS2-3164:
-
Using -u works. I do not have any problems when using this
Hello,
Here is the wsdl gnerated when I use the ?wsdl. The return object is
GMDSRESPCT, adn the tag containing the byteArray is CONTENT. You will notice
that CONTENT is defined as xsd:string type. This is weird because I generated
the class using WSDL2java and when I first created the wsdl
Hello,
classical case of WSDL first. I'd suggest alter the
type of CONTENT to base64Binary, then generate your
java-code with WSDL2Java and use the resulting classes
Worked with me.
Cheers
--- Thomas Beaujard [EMAIL PROTECTED] wrote:
Hello,
Here is the wsdl gnerated when I use the ?wsdl. The
I'm dealing with a service which sends back a response that's not complying
with the service WSDL. In details, it sometimes sends an attribute set to
(blank) while the attribute itself is defined as integer. The result is a
java.lang.reflect.InvocationTargetException during deserialization
I'm trying to manipulate a response message using DOM on Axis 1.1, but I'm
not sure about the flow I should follow.
I've tried the following:
Message response = msgContext.getResponseMessage();
SOAPEnvelope responseEnvelope = response.getSOAPEnvelope();
SOAPBodyElement sbe = (SOAPBodyElement)
Java Client on Axis Java 1.4
Key: AXIS-2694
URL: https://issues.apache.org/jira/browse/AXIS-2694
Project: Axis
Issue Type: Bug
Affects Versions: 1.4
Environment: Windows
Reporter: Sneha
Do you mean between,
Axis and Axis2
or
Axis2 1.2 and the latest release Axis2 1.3?
If you mean the latter, then the following is taken from the Axis2
1.3release note.
Major Changes Since 1.2:
- Moved to maven2 from maven1
- Significantly improved documentation
- Significantly improved support
[
https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonas Boëthius reopened AXIS2-2389:
---
Still not dispatching correct, now tested on Axis2, version 1.3.
Dispatching based on the SOAP
[
https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525116
]
Jonas Boëthius commented on AXIS2-2389:
---
Correct dispatching (with default configuration) to a service based
[
https://issues.apache.org/jira/browse/AXIS2-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boyan Yurukov updated AXIS2-3159:
-
Description:
I am trying to generate a web service from a wsdl that imports several schemes.
Guys,
I dont know whether this is a AXIS2 problem.
I am trying to get the Image files from the documentum server using web
service.
when i try to get say 4 image files in a go and if the total size of the
file is in some MBs then the JVM goes bm.
i have done follwong things to avoid
1. Set a
JAX-WS: A small performance improvement and some cleanup
Key: AXIS2-3168
URL: https://issues.apache.org/jira/browse/AXIS2-3168
Project: Axis 2.0 (Axis2)
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AXIS2-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-3168.
---
Resolution: Fixed
Committed revision 573047
JAX-WS: A small performance improvement and
JAX-WS: Fix to AsyncResponse to ensure that the returned object is unmarshalled
before reporting it as available
Key: AXIS2-3169
URL:
[
https://issues.apache.org/jira/browse/AXIS2-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-3169.
---
Resolution: Fixed
Committed changes: 573057
JAX-WS: Fix to AsyncResponse to ensure that
Ensure content-type does not have a trailing ':'
Key: AXIS2-3170
URL: https://issues.apache.org/jira/browse/AXIS2-3170
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
[
https://issues.apache.org/jira/browse/AXIS2-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved AXIS2-3170.
---
Resolution: Fixed
Committed the change: 573093
Ensure content-type does not have a
You won't be able to send large data inside the envelope using Base64
binary, as it'll cause Axis2 to load the whole of data in to memory.
You should use MTOM or SwA if your data are large.
Are you getting the error on client or on server side. IIRC in the
service code of your earlier posting you
[
https://issues.apache.org/jira/browse/AXIS2-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525283
]
Amila Chinthaka Suriarachchi commented on AXIS2-3028:
-
can you send the full stack trace if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We do not support 2004/03 version of WS-Addressing. Any possibility of
moving to 2004/08 or 2005/08?
Thanks,
Chinthaka
David Bunzli wrote:
Hi,
I've developed a Java Axis2 1.1 client to talk to a dot net WS. My
client appears to have two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ashique,
First your exception is not that useful to track the problem. Can you
please provide with soap messages exchanged and the wsdl you are using.
Also, I've also encountered this meaningless exception couple of times.
It would be good if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
The problem seems to be with the soap message. Can you post the response
message that you got from the server. It seems to me that SOAP-ENV
namespace is not defined in that.
Chinthaka
Michael Sutter wrote:
Hello list,
I have a problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
http://wso2.org/library/2561
David Bunzli wrote:
Hi,
I've developed my client in Axis2 1.1.
Can anyone point me to information on how to programmatically set my
WS-Addr attributes/values?
Thanks,
David
[
https://issues.apache.org/jira/browse/AXIS2-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525289
]
Amila Chinthaka Suriarachchi commented on AXIS2-2389:
-
I invoke a service with your wsdl with
[
https://issues.apache.org/jira/browse/AXIS-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sneha Jain updated AXIS-2694:
-
Issue Type: Wish (was: Bug)
Java Client on Axis Java 1.4
34 matches
Mail list logo