[
https://issues.apache.org/jira/browse/AXISCPP-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479498
]
Wayne Johnson commented on AXISCPP-1025:
Sorry, poor choice of words on my part. The Java server of which
[
https://issues.apache.org/jira/browse/AXISCPP-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479510
]
nadir amra commented on AXISCPP-1026:
-
I have put everything in SVN except
pSZ.serialize (
[
https://issues.apache.org/jira/browse/AXISCPP-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nadir amra closed AXISCPP-1025.
---
Resolution: Fixed
Code is in SVN, eliminated all occurrences of the use of item in the
[
https://issues.apache.org/jira/browse/AXISCPP-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479516
]
nadir amra commented on AXISCPP-1026:
-
And from http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383522:
[
https://issues.apache.org/jira/browse/AXISCPP-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479517
]
nadir amra commented on AXISCPP-1026:
-
So if we do need to generate something, then I think it would be
Hi,
Trying to create a simple web service with Axis2c and trying to
deploy in IIS, steps followed and getting the error attached.
Can any one suggest how to get rid of the errors?
1. Created a new solution in VC++7.0
2.Created New Project for LL
3 Generated
[
https://issues.apache.org/jira/browse/AXIS2-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chatra Nakkawita resolved AXIS2-2300.
-
Resolution: Fixed
reviewed and committed. Thanks,
Chatra
Reviewed files in xdocs :
In case you didn't see this.
http://www.devx.com/Java/Article/33839
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
[EMAIL PROTECTED]
Oxygenating the Web Service Platform, www.wso2.com
[
https://issues.apache.org/jira/browse/AXIS2-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479283
]
Ole Dalgaard commented on AXIS2-2000:
-
OK, interesting...
I wanted to test the testBad with the latest snapshot
On 07/03/07, Paul Fremantle [EMAIL PROTECTED] wrote:
Yep I guess. If CPL is really an issue for some people maybe we should
prompt IBM to donate as promised and Woden to build a version of
WSDL4J too.
Although this is draft [1], it indicates CPL is ok to ship in binary
form (with conditions)
Hi,
On 3/8/07, Jeremy Hughes [EMAIL PROTECTED] wrote:
On 07/03/07, Paul Fremantle [EMAIL PROTECTED] wrote:
Yep I guess. If CPL is really an issue for some people maybe we should
prompt IBM to donate as promised and Woden to build a version of
WSDL4J too.
Although this is draft [1], it
AFAIK WSDL4J is pretty embedded into Axis2, because Axis2 uses it to
dynamically create WSDL for POJO endpoints.
It would be some significant effort to move to a non-CPL WSDL4J. I've
never heard of anyone complaining about CPL before. Is it a real
objection to CPL or simply its not ASL.
Paul
Hi,
On 3/8/07, Paul Fremantle [EMAIL PROTECTED] wrote:
AFAIK WSDL4J is pretty embedded into Axis2, because Axis2 uses it to
dynamically create WSDL for POJO endpoints.
OK, thanks.
It would be some significant effort to move to a non-CPL WSDL4J. I've
never heard of anyone complaining about
Hi Asankha:
I assume this has already been reported as an Axis2 problem? IMHO we
should just fix this on the A2 side and not write this kind of
bug-compatible code for Synapse.
--Glen
[EMAIL PROTECTED] wrote:
Author: asankha
Date: Thu Mar 8 04:30:44 2007
New Revision: 516022
URL:
Hi Glen,
I think this has been discussed before... the problem is that any
handler may add an OMElement as a child of the SOAPHeader per the
OMElement interface.
If this is to be fixed it's in Axiom, and I think there was some
justification for not changing this when it was brought up before...
Thanks David. I'll look through the archives - but I'd definitely like
to see this fixed unless there's a really compelling reason not to do
so. I'll write again after a quick read. :)
If we want to have an interface that adds a generic OMElement to
SOAPHeader, that's fine... but it's a
wsa 04 version problem - AxisFault Required MessageID in header in Response
---
Key: AXIS2-2301
URL: https://issues.apache.org/jira/browse/AXIS2-2301
Project: Axis 2.0 (Axis2)
Jukka,
There may be a way out...check the JIRA :)
-- dims
On 3/8/07, Jukka Zitting [EMAIL PROTECTED] wrote:
Hi,
On 3/8/07, Paul Fremantle [EMAIL PROTECTED] wrote:
AFAIK WSDL4J is pretty embedded into Axis2, because Axis2 uses it to
dynamically create WSDL for POJO endpoints.
OK, thanks.
Well written article, uses all the axis2 code already in place. If no
one objects I'd like to include the link in the site 'articles'
section.
Robert
On 3/8/07, Paul Fremantle [EMAIL PROTECTED] wrote:
In case you didn't see this.
http://www.devx.com/Java/Article/33839
--
Paul Fremantle
Hi guys ...
On 21/02/07, Paul Fremantle [EMAIL PROTECTED] wrote:
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It seems to me that what you are describing is a case where
the Axis2 engine is not the ultimateReceiver (see 2.7 Relaying SOAP
Messages
[
https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian DePradine reassigned AXIS2-2301:
--
Assignee: Brian DePradine
wsa 04 version problem - AxisFault Required MessageID in
[
https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479320
]
Brian DePradine commented on AXIS2-2301:
Hi Gee,
Can you please provide some more details on the scenario
Jeremy
I think maybe you've misread the spec.
Basically the relay attribute is a red-herring in this case, because I
for one have never seen a relay header. The model is actually
reasonably simple (excluding the relay attribute for the minute):
* headers that are not explicitly marked with a
Paul Fremantle wrote:
* it must fault if there are mustUnderstand headers targeted at its roles
MU headers that it doesn't actually understand, you mean. :)
--G
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Doh! Yep thats what I meant.
Paul
On 3/8/07, Glen Daniels [EMAIL PROTECTED] wrote:
Paul Fremantle wrote:
* it must fault if there are mustUnderstand headers targeted at its roles
MU headers that it doesn't actually understand, you mean. :)
--G
[
https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479327
]
Gee Chia commented on AXIS2-2301:
-
Hi Brian:
Basically, I have a simple web service, ServiceB with start operation.
Paul Fremantle wrote:
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It seems to me that what you are describing is a case where
the Axis2 engine is not the ultimateReceiver (see 2.7 Relaying SOAP
Messages
On 08/03/07, Davanum Srinivas [EMAIL PROTECTED] wrote:
Jukka,
There may be a way out...check the JIRA :)
Maybe it hasn't been clear (sorry) ... the code in the JIRA is a
snapshot of WSDL4J 1.4. Axis2 uses WSDL4J 1.6.2 which isn't
contributed. So, the revisions to WSDL4J since 1.4 haven't been
Cool! I'd love to implement this in Synapse too. Basically have a way
of defining the roles a Synapse node implements.
Paul
On 3/8/07, Glen Daniels [EMAIL PROTECTED] wrote:
Paul Fremantle wrote:
David, Sanjiva
Shouldn't we be using the SOAP role model to handle this kind of
situation. It
Paul Fremantle wrote:
Cool! I'd love to implement this in Synapse too. Basically have a way
of defining the roles a Synapse node implements.
Yup - you'll just configure that in Synapse and then pass it down to Axis.
--G
Paul Fremantle wrote:
David, Sanjiva
Shouldn't we be using the SOAP
Hi devs,
We had a build break in Rampart due to the MessageId addressing
header being absent in the response message. Is this behavior correct?
Thanks,
Ruchith
On 3/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: ruchithf
Date: Thu Mar 8 07:00:53 2007
New Revision: 516065
URL:
resend with the axis2 prefix :-)
On 3/8/07, Ruchith Fernando [EMAIL PROTECTED] wrote:
Hi devs,
We had a build break in Rampart due to the MessageId addressing
header being absent in the response message. Is this behavior correct?
Thanks,
Ruchith
On 3/8/07, [EMAIL PROTECTED] [EMAIL PROTECTED]
No, namespace prefixes are not significant in SOAP messages. They are
just a shorthand.
Axis doesn't preserve them in any way (nor do most other toolkits that I
am aware of).
--
Tom Jordahl
Adobe ColdFusion Team
From: anup bansal [mailto:[EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/AXIS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479356
]
Tom Jordahl commented on AXIS-2635:
---
Axis has always used Xerces, never crimson, so I am not sure why you would see
java.lang.RuntimeException: Can not serialize OM Element Envelope
-
Key: AXIS2-2302
URL: https://issues.apache.org/jira/browse/AXIS2-2302
Project: Axis 2.0 (Axis2)
Issue Type:
[
https://issues.apache.org/jira/browse/AXIS2-2302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federica Ciotti updated AXIS2-2302:
---
Attachment: PublishClient.java
java.lang.RuntimeException: Can not serialize OM Element
Hi Ruchith,
I modified the code recently to only send the message id and the relates
to headers in an async response. It is meant to be a small performance
tweak.
Cheers
Brian DePradine
Web Services Development
IBM Hursley
External +44 (0) 1962 816319 Internal 246319
If you can't
Prefixes are significant when the XML message or a portion thereof is
being signed.
Anup -- you have to make sure you process the signature before Axis
begins to process it. Are you using WSS4J to process the signature?
If the application needs to maintain the contents of the original SOAP
[
https://issues.apache.org/jira/browse/AXIS2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479428
]
Jeff Peterson commented on AXIS2-1220:
--
I think this issue needs to be reopened. With the default
[
https://issues.apache.org/jira/browse/AXIS2-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479449
]
Jeff Peterson commented on AXIS2-1220:
--
I found a work-around for the problem:
* Manually set contextRoot in
I will be out of the office starting 03/08/2007 and will not return until
03/19/2007.
If you need to reach me immediately, please try my personal cell phone at
512-797-6788.
You may also contact Carlton Mason or Ann Robinson, who both know my
backups for all related projects.
Thanks.
Mike
I'm trying to call Axis2 using the LocalTransportReceiver and
LocalTransportSender.
I already have the SOAP request in a string 'text'.
ByteArrayInputStream inboundMessage = new
ByteArrayInputStream(text.getBytes());
LocalTransportReceiver.CONFIG_CONTEXT = myAxisConfigContext;
java2wsdl-maven-plugin throws ClassNotFoundException on execution of java2wsdl
goal
---
Key: AXIS2-2303
URL: https://issues.apache.org/jira/browse/AXIS2-2303
Project:
[
https://issues.apache.org/jira/browse/AXIS2-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shane Isbell updated AXIS2-2303:
Attachment: patch-tests.zip
Tests for the patch.
java2wsdl-maven-plugin throws
44 matches
Mail list logo
