Re: Axis2 Java codegen tool fails to include message parts mapped to SOAP headers
I agree that the tool not at least spitting out a warning is probably
a bug. Please open a JIRA [1] to get that added.
David
[1] https://issues.apache.org/jira/browse/AXIS2
On Wed, Dec 24, 2008 at 7:12 PM, Gilbert Pilz gilbert.p...@oracle.com wrote:
Hi,
I'm new to Axis2 but I sort of know my way around SOAP etc. I'm trying to
build an Axis2 implementation of the Web Services Test Forum (WSTF)
Notify-Echo scenario. The WSDL for this scenario is a little tricky. The
Notify and Echo messages contain two parts, the actual data to be sent and a
SessionData element that provides an app-level session ID. The service is
supposed to concatenate all the notify and echo data from a given session
and return it on the Echo operation. For example:
Notify(foo, session1)
Notify(blub, session2)
Echo(baz, session1) -- returns foobaz
So far, pretty simple. The tricky part is in the SOAP bindings where the
SessionData part is mapped to a SOAP header like so:
wsdl:operation name=Notify
soap12:operation/
wsdl:input
soap12:header use=literal part=SessionData message=tns:Notify/
soap12:body use=literal parts=Notify/
/wsdl:input
/wsdl:operation
When I process this WSDL using the Axis2 codegen task it seems to work fine;
there are no warnings etc. However, the generated Java code doesn't reflect
the presence of SessionData element. Here's the server skeleton for the
Notify method:
/**
* Auto generated method signature
*
* @param notify14
*/
public void Notify(org.wstf.www.docs.scenarios.sc002.Notify notify14)
{
//TODO : fill this with the necessary business logic
}
This just seems wrong to me. I think the tool should either generate code
the accurately reflects the portType (i.e. including all the parts of all
the input and output messages) or it should warn you that it is leaving
something out.
I'm using version 1.4.1 of Axis2. I'm invoking the codegen tool via ant like
so:
taskdef name=codegen
classname=org.apache.axis2.tool.ant.AntCodegenTask
classpathref=axis.classpath/
target name=compile.wsdl
unless=wsdl.compiled
depends=init
codegen wsdlfilename=src/sc003.wsdl
output=generated
serverside=true
generateservicexml=true
portName=soap12port
serverSideInterface=true/
/target
Gilbert Pilz | SOA/WS Technologist | Oracle Corporation
Re: [ANN] Apache Axis2 1.4 Released
You've got the wrong groupid. Try [1] David [1] http://repo1.maven.org/maven2/org/apache/axis2/axis2-kernel/1.4/ On Fri, May 2, 2008 at 6:07 PM, Sharad Baronia [EMAIL PROTECTED] wrote: Hi Dim, According to ur email, we should be able to get latest version of jars from maven2 repository. But when I try to get jar files from the repository, it doesn't find it (here the link: http://repo1.maven.org/maven2/axis2/axis2-kernel/1.4/). Any help or advice would be appreciated. Thanks, Sharad Baronia Market Data / Feed Nexa Technologies, Inc. 8 Pasteur, Suite 100, Irvine, CA 92618 USA Work: 949-885-8711 Fax: 949-885-2194 Email: [EMAIL PROTECTED] -Original Message- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Friday, May 02, 2008 8:55 AM To: Axis developer list; axis-user@ws.apache.org; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: [ANN] Apache Axis2 1.4 Released -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Folks, Just over 8 months since the 1.3 release, we are very proud to announce the release of Apache Axis2 version 1.4. Downloads are available at: ~http://ws.apache.org/axis2/download.cgi The Maven2 main repository has the latest jars as well. Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy addition of plug-in modules that extend its functionality for features such as security and reliability. Modules supporting WS-Security/Secure-Conversation (Apache Rampart), WS-Trust (Apache Rahas), WS-Reliable Messaging (Apache Sandesha) and WS-Eventing (Apache Savan) will be available soon after the Apache Axis2 1.4 release. Please see these projects' own sites for further information. Major Changes Since 1.3: - - Support for JAXWS and JSR 181 Annotations (See 7 samples in the binary distribution) - - Experimental CORBA Support - - Fixed tons of small and not-so-small bugs (See list in release-notes.html in the binary distribution) Known Issues and Limitations in 1.4 Release: - - Need to use wsimport/wsgen tools in JDK1.6 for JAXWS code generation. - - Please see JIRA for the current status of bugs We welcome any and all feedback at: ~axis-user@ws.apache.org (please include [axis2] in the subject, please subscribe first) ~[EMAIL PROTECTED] (please include [axis2] in the subject, please subscribe first) ~http://issues.apache.org/jira/browse/AXIS2 Thank you for your interest in Apache Axis2! The Axis2 Development Team http://ws.apache.org/axis2/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) iD8DBQFIGzk/gNg6eWEDv1kRApJ8AJ0ehHS6I4yGb1veE7Cc/UA2TPE1rQCfR+o+ Km0PhkgghwcSxyeY1G74s2c= =2sDC -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ___ Inbound Email has been scanned by Nexa Technologies Email Security Systems. ___ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Moving Axis2 code base into JDK 1.5
Um, right now I'd be tempted to push out an Axis2 1.4 with JDK 1.4 support soon for existing JDK 1.4 users, then move to 5 for Axis2 1.5. David On Tue, Feb 26, 2008 at 10:35 PM, Amila Suriarachchi [EMAIL PROTECTED] wrote: +1to move to jdk 1.5. thanks, Amila. On Wed, Feb 27, 2008 at 10:01 AM, Lawrence Mandel [EMAIL PROTECTED] wrote: +1 Woden has also discussed a move to Java 5 and the dev team was in favour of this move. As Axis2 depends on Woden we cannot consider this move unless Axis2 also moves. Lawrence Deepal Jayasinghe [EMAIL PROTECTED] 02/26/2008 11:15 PM Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] [EMAIL PROTECTED], axis-user@ws.apache.org axis-user@ws.apache.org cc Subject [Axis2] Moving Axis2 code base into JDK 1.5 Hi all , As you might remember few months back Glen asked the list about moving to JDK 1.5 and I think we got very positive feedback. So I thought of asking again and change the code to work with JDK 1.5 . The main reason behind sending this mail is due the dependency we have for annogen. As I can see that project is dead one and there is no development happening so I do not think it is a good idea to depend on such a project. In the meantime we have few issues with annogen as well ,first inner class problem (I have locally fixed that both in Axis2 and Annogen will commit soon) , second is the final class problem. I request a release from annogen after the changes that Dims did , but we did not get any reply so far. We all know that we get better annotation support from JDK 1.5 so if we move to JDK 1.5 we can get rid of the annogen dependency and we can just use JDK for annotation processing. Other problem is generic support , if we move to JDK 1.5 we can have generic support in our POJOs. In addition to POJO we can get better concurrent support in JDK 1.5 as well. So if we move to JDK 1.5 we can get better support , and I do not think any advantage of staying in 1.4 . If some user want to use Axis2 in JDK 1.4 they can happily use Axis2 1.3 , which is very stable version and working fine in 1.4 and 1.5. If any user or developers have any concern on moving to JDK 1.5 please come forward and reply to this mail that will be very helpful for all of us. Here is my +1 for moving to JDK 1.5 to and release Axis2 1.4 in JDK 1.5 Thank you, Deepal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] DeploymentException during module deployment
On Jan 18, 2008 9:53 AM, Michele Mazzucco [EMAIL PROTECTED] wrote: David, thanks very much, that did the job. you're welcome Michele p.s. Wouldn't it be better to ignore lower/upper case? XML in general is case sensitive, so it makes sense for us to stick to that. Cheers, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] DeploymentException during module deployment
(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:432) Caused by: java.lang.ClassNotFoundException: ncl.qosp.modules.manager.RouterDispatcher at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1355) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1201) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:164) at org.apache.axis2.util.Loader.loadClass(Loader.java:261) at org.apache.axis2.util.Loader.loadClass(Loader.java:229) at org.apache.axis2.deployment.util.Utils.loadHandler(Utils.java:117) ... 33 more Any idea? Thanks in advance, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] java.util.regex.PatternSyntaxException
Hi Michele,
It looks like the problem is that spliting that string results in
invalid regular expressions i.e. * must follow a character.
I added the following to
org.apache.axis2.transport.http.ProxyConfiguration.validateNonProxyHosts(String)
and no longer get the exception and the matching seem to work:
if(a.startsWith(*)){a = .+a;}
However, I'm not sure if this is on a performance critical path, so
please open a JIRA with this information and someone more familar with
the transport should take a look and perhaps come up with a better
fix.
Thanks,
David
On Jan 15, 2008 4:48 PM, Michele Mazzucco [EMAIL PROTECTED] wrote:
David, here it is
localhost|*.localhost|ncl.ac.uk|*.ncl.ac.uk
Michele
p.s. with localhost as first element it works fine in the synchronous
version -- but as soon as I add a callback if fails as well
On 15 Jan 2008, at 16:40, David Illsley wrote:
Michele, could you add code to your client to sysout
System.getProperty(HTTP_NON_PROXY_HOSTS) so it's possible to tell what
regex might be failing?
Thanks,
David
On Jan 15, 2008 4:09 PM, Michele Mazzucco
[EMAIL PROTECTED] wrote:
Some more information. Everything works fine with Axis2 1.2.
Michele
On 15 Jan 2008, at 16:02, Michele Mazzucco wrote:
Hello again,
apparently this problem has already been raised here
http://www.mail-archive.com/axis-user@ws.apache.org/msg35891.html
Any idea?
Thanks,
Michele
On 15 Jan 2008, at 15:30, Michele Mazzucco wrote:
Hi all,
can anybody tell me what's going on here?, the code used to create
the payload and options is the following
SOAPFactory factory = OMAbstractFactory.getSOAP12Factory();
OMNamespace omns = factory.getNamespace();
OMElement payload = factory.createOMElement
(hello, omns);
payload.setText(text);
ServiceClient sender = new ServiceClient
(this.configContext, null);
Options options = new Options();
options.setTo(new EndpointReference(http://
localhost:10001/
axis2/services/EchoXml));
logger.info(Message is going to: + options.getTo
());
options.setTransportInProtocol
(Constants.TRANSPORT_HTTP);
options.setCallTransportCleanup(true);
options.setAction(urn:echo);
sender.setOptions(options);
OMElement result = sender.sendReceive(payload);
try {
result.serialize(System.out);
} catch (XMLStreamException e) {
logger.error(e);
}
Axis2 runs embedded using SimpleHTTPServer while the target EPR is
set to localhost. Why is it complaining about '*'? Where does it
get the domain?
Thanks,
Michele
0 [main] DEBUG org.apache.axiom.om.util.StAXUtils -
XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
229 [main] DEBUG org.apache.axis2.engine.Phase - Handler
RequestURIBasedDispatcher added to Phase Transport
238 [main] DEBUG org.apache.axis2.engine.Phase - Handler
SOAPActionBasedDispatcher added to Phase Transport
242 [main] DEBUG org.apache.axis2.engine.Phase - Handler
AddressingBasedDispatcher added to Phase Addressing
245 [main] DEBUG org.apache.axis2.engine.Phase - Handler
RequestURIBasedDispatcher added to Phase Dispatch
246 [main] DEBUG org.apache.axis2.engine.Phase - Handler
SOAPActionBasedDispatcher added to Phase Dispatch
249 [main] DEBUG org.apache.axis2.engine.Phase - Handler
RequestURIOperationDispatcher added to Phase Dispatch
251 [main] DEBUG org.apache.axis2.engine.Phase - Handler
SOAPMessageBodyBasedDispatcher added to Phase Dispatch
253 [main] DEBUG org.apache.axis2.engine.Phase - Handler
HTTPLocationBasedDispatcher added to Phase Dispatch
254 [main] DEBUG org.apache.axis2.engine.Phase - Handler
AddressingBasedDispatcher added to Phase Addressing
254 [main] DEBUG org.apache.axis2.engine.Phase - Handler
RequestURIBasedDispatcher added to Phase Dispatch
254 [main] DEBUG org.apache.axis2.engine.Phase - Handler
SOAPActionBasedDispatcher added to Phase Dispatch
255 [main] DEBUG org.apache.axis2.engine.Phase - Handler
RequestURIOperationDispatcher added to Phase Dispatch
255 [main] DEBUG org.apache.axis2.engine.Phase - Handler
SOAPMessageBodyBasedDispatcher added to Phase Dispatch
255 [main] DEBUG org.apache.axis2.engine.Phase - Handler
HTTPLocationBasedDispatcher added to Phase Dispatch
437 [main] INFO org.apache.axis2.deployment.util.Utils - Created
temporary file : /tmp/_axis2/axis263443addressing-1.3.mar
476 [main] DEBUG org.apache.axiom.om.util.StAXUtils -
XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
526 [main] DEBUG org.apache.axis2.i18n.ProjectResourceBundle -
getBundle(org.apache.axis2,org.apache.axis2.i18n,resource,null,...)
549 [main] DEBUG org.apache.axis2.i18n.ProjectResourceBundle -
loadBundle
Re: [Axis2] java.util.regex.PatternSyntaxException
) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 JMS Transport to WebSphere MQ
Hi, I don't have any specific suggestions, but I am aware that someone has worked on this before. I suggest searching the Axis2 user and dev archives for the following JIRA (which is the context in which is was discussed previously): https://issues.apache.org/jira/browse/AXIS2-2816 Cheers, David On Jan 10, 2008 4:45 PM, callagc4 [EMAIL PROTECTED] wrote: Hi, We are currently using axis2 in a standalone server. I have been trying to configure axis2 to hook up with websphereMQ. However i am unsure of how to configure axis2 for this as all the examples i have found are for activeMQ. Could anyone tell me how this can be done? My main area of concern is the definition of a jms transportReciever for websphereMQ. Any advice would be much appriciated. My attempts so far have left me here, using the definition below. However this currently does not work. The first issue is that the initial context factory being used is based in websphere not websphereMQ. Secondly how do i configure this jndi resource in websphereMQ, i.e configure jms/QueueConnectionFactory transportReceiver name=jms class=org.apache.axis2.transport.jms.JMSListener parameter name=default parameter name=java.naming.factory.initialcom.ibm.mq.jms.context.WMQInitialContextFactory/parameter parameter name=java.naming.provider.urllocalhost:1414/parameter parameter name=transport.jms.ConnectionFactoryJNDINamejms/QueueConnectionFactory/parameter /parameter /transportReceiver Thanks, Cathal -- View this message in context: http://www.nabble.com/Axis2-JMS-Transport-to-WebSphere-MQ-tp14738492p14738492.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.3 wsa:To header usage
Sure, The WS-A WG didn't really define much on the mlti-hop scenario so the specifications don't help much here. It is worth pointing out that in the interops we did, it became apparent that SOAP Binding 3.5 [1] was interpreted by different people in different ways, and that the 'safest' route is to put the transport address you're sending the message to in the wsa:To. All that said, if you want to raise a JIRA about the fact that the Axis2 WS-A Handlers don't process soap role/actor attributes, (I think a different scenario than you're talking about) I'd be willing to take a look. Cheers, David [1] http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/#soaphdrvtransport On 26/10/2007, Brian De Pradine [EMAIL PROTECTED] wrote: Hello Erwin, The thing about intermediaries is that they are usually there to hide the address of the of the ultimate receiver ( imagine a gateway server or proxy for instance ). In that case flowing the address of the ultimate receiver across the intermediary would tend to make having the intermediary a bit pointless. Anyone else care to chime in? Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Erwin Reinhoud [EMAIL PROTECTED] wrote on 25/10/2007 15:54:10: Hello all, Don't know if this is the correct location to post this, so please let me know if not. I create a client and want to make a call with WS-Addressing headers. What i noticed is that often there is a strong relation between the wsa:To value and the actual http uri being used to send the message to the next hop. I thought the wsa:To could contain the (logical) value of the end destination. So if there are two intermediairies than the wsa:To can stay the same over all hops. Currently this does not seem to be. Is my perception of the wsa:To wrong? ServiceClient client = new ServiceClient(context,null); Options ops = new Options(); Endpointreference to = new Endpointreference(finalDest); ops.setTo(to); Endpointreference epr = new Endpointreference(http: //localhost/axis2/services/myservice); client.setoptions(ops); client.setTargetEpr(epr); The ops.setTo value will be used to dispatch the message. Kind regards, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2/Java - Trouble building Axis2/Java from source
Reason: POM 'org.apache.axis2:axis2-mar-maven-plugin' not found in repository: Unable to download the artifact from any repository org.apache.axis2:axis2-mar-maven-plugin:pom:1.6.2 from the specified remote repositories: apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), eclipse-repo (http://repo1.maven.org/eclipse), ws-zones (http://ws.zones.apache.org/repository2), jibx (http://jibx.sourceforge.net/maven), apache-ws-snapshots2 (http://ws.zones.apache.org/repository2 ), central (http://repo1.maven.org/maven2), apache-incubating (http://people.apache.org/repo/m2-incubating-repository ), tomcat-repository (http://tomcat.apache.org/dev/dist/m2-repository ), java.net ( http://download.java.net/maven/1/), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository ) for project org.apache.axis2:axis2-mar-maven-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 13 seconds [INFO] Finished at: Mon Oct 22 12:18:06 EDT 2007 [INFO] Final Memory: 9M/29M [INFO] Thanks, Mike Michael J Molé Software Engineer IBM Software Group - Rational (781)676-2710 -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.3 wsa:MessageID not in generated service skeleton response
Hi Erwin, At the moment, we omit the wsa:MessageID on the response message as a performance optimisation. It's not really possible for you to force Axis2 to include it at the moment. Please raise a JIRA for a way to toggle this optimisation off if its important to you. Cheers, David On 15/10/2007, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello All, Following the advice below i created my own service having the arguments and returning element being an OMElement. However, what i want is to have the response to include the wsa:MessageId. How do i do this in the service? I need to return the soap:body so i can define the wsa header. Any ideas? Thanks in advance. Kind regards, Erwin -Oorspronkelijk bericht- Van: Erwin Reinhoud Verzonden: dinsdag 9 oktober 2007 8:43 Aan: axis-user@ws.apache.org Onderwerp: RE: axis2 1.3 wsa:MessageID not in generated service skeleton response Hello Deepal, We have to comply with a standard (governmental) that prescribes the use of a messageid in request/response. In case on application level the communbication is with jms the messages can be linked. Until now i have used the contract first principle to make a service, do i have to let that go now? How about that message below, i guess it will not be implemented? Thanks in advance. Kind regards, Erwin -Oorspronkelijk bericht- Van: Deepal jayasinghe [mailto:[EMAIL PROTECTED] Verzonden: maandag 8 oktober 2007 17:23 Aan: axis-user@ws.apache.org Onderwerp: Re: axis2 1.3 wsa:MessageID not in generated service skeleton response Erwin Reinhoud wrote: Hello All, I generated a serviceskeleton with adb and enabled ws-addressing both on service and client. In the response i don't see the MessageID. How do you set your own messageID in the serviceskeleton code? In Axis2 1.3 you do not have a way to set the message ID when you use codegeneration (skel). In the meantime having a message id is not an mandatory , so may I know why do you want this message id ? Thanks Deepal I found this message, but no related issue in jira: http://mail-archives.apache.org/mod_mbox/ode-user/200707.mbox/[EMAIL PROTECTED] Anybody know if there is an issue and how to set a certain value for the wsa:messageid from the serviceskeleton? Thanks in advance. Kind regards, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] 2 Instances of Axis2 running by default in Axis2 WAR?
Lawrence,
This isn't my area of expertise, but looking at AxisAdminServlet and
AxisServlet, it looks like the init(ServletConfig) methods
store/retrieve the first created configuration context from an
attribute on the ServletContext, so only one should be created:
Extract:
this.configContext =
(ConfigurationContext)
servletContext.getAttribute(CONFIGURATION_CONTEXT);
if(configContext == null){
configContext = initConfigContext(config);
config.getServletContext().setAttribute(CONFIGURATION_CONTEXT,
configContext);
}
Does that make sense?
David
On 11/10/2007, Lawrence Mandel [EMAIL PROTECTED] wrote:
I'm trying to understand how Axis2 is initialized. When deploying Axis2 in
a Servlet container (like Tomcat) there are two Servlets that get invoked:
AxisServlet and AxisAdminServlet. Both of these Servlets seem to go
through the same initialization routine setting up Axis2 configurations.
In this way it appears that both Servlets contain their own instance of
Axis2 and therefore their own copies of the running services and modules
and both will probe for new services and modules. It seems to me that
Axis2 should only be configured once and this configuration should be
shared between AxisServlet and AxisAdminServlet.
Am I correct in my assessment above and if so are two instances of Axis2
created intentionally?
Thanks,
Lawrence
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mapActionToOperation() messages
Hi, Yes, it'll be something to do with the WSDL. This isn't actually a problem, hence its status as a DEBUG message. Please just ignore it. David On 07/06/07, Swavek Skret [EMAIL PROTECTED] wrote: Hi, While deploying my axis2 SOAP server aar file, the tomcat debug log tell me that I am trying to map multiple actions to the same operation. Does anyone know what could be causing it? I presume it is a WSDL issue. Below is the log example. Thanks, Swavek 2007-06-07 12:16:14,550 DEBUG org.apache.axis2.description.AxisService - mapActionToOperation: Mapping Action to Operation: action: getSmProvisioning; operation: [EMAIL PROTECTED] 2007-06-07 12:16:14,550 DEBUG org.apache.axis2.description.AxisService - mapActionToOperation: This operation is already mapped to this action: getProvisioning; AxisOperation: [EMAIL PROTECTED] named: getProvisioning 2007-06-07 12:16:14,550 DEBUG org.apache.axis2.description.AxisService - mapActionToOperation: Mapping Action to Operation: action: handleControlRequest; operation: [EMAIL PROTECTED] 2007-06-07 12:16:14,550 DEBUG org.apache.axis2.description.AxisService - mapActionToOperation: This operation is already mapped to this action: handleControlRequest; AxisOperation: [EMAIL PROTECTED] named: handleControlRequest - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Engaging Modules not in Repositories
Try: configContext.getAxisConfiguration().deployModule(path/to/addressing.mar); configContext.getAxisConfiguration().engageModule(addressing); David On 05/06/07, Zachary Marshall [EMAIL PROTECTED] wrote: Yeah, this seems to be a difficult problem. I haven't tried, but I assume I could generate a string with the path of the module since it is always in a subdirectory of whatever directory axis2 is installed in (I'm sure there's a way to find where this is). Suffice to say that I can generate such a string in any circumstance, if not by axis2's location, then by some other means. Then, would there be a way to engage using only the path to the mar? -Zach -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 05, 2007 4:51 PM To: axis-user@ws.apache.org Subject: Re: Engaging Modules not in Repositories Ouch. This is really tricky. I'm fresh out of ideas. I assume you do have a string with the path of the module at least? Paul On 6/5/07, Zachary Marshall [EMAIL PROTECTED] wrote: Hi Paul, Thanks for your response. I'd love to simply drop the mar in the same directory as the axis2 jars, however, I don't have control over where the mar gets installed (I can't make it be installed in the same directory as the axis2-*.jar files) for a couple of reasons. Any other ideas? Thanks! -Zach -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 05, 2007 4:26 PM To: axis-user@ws.apache.org Subject: Re: Engaging Modules not in Repositories Zach We've just been discussing this. It seems like Axis2 looks in the same directory as the axis2-*.jar files, so if you put it in that folder it should work. Paul On 6/5/07, Zachary Marshall [EMAIL PROTECTED] wrote: Is there a way to engage a module (specifically addressing) client side that is neither in the axis2 repository and which is not specified on the classpath? I have limiting development conditions that prohibit me from controlling where the mar files end up on the client's machine. This is strictly a client operation, so there won't be a repository to load the mar from, but the mar will distributed in a subfolder of the folder that contains the axis2 jars. Furthermore, I can't modify the classpath of the program that invokes my code, so I can't add the mar to the classpath. Thanks for any help. Let me know if more details are needed. Zach - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2: How to measure the time taken by Axis2 engine to process the request/reply SOAP messages
Inder, I'm not an expert but I think what the others are getting at is that you'll see much more repsesentative numbers if you time how long it takes to deal with some thousands of requests and divide by the number of requests. One way to approach this is to use one of the test client mentioned. Does that make any sense? David On 06/06/07, Inder Dhillon [EMAIL PROTECTED] wrote: Hello Thanks for all of your comments. But my question was that how can we measure the time taken by axis2 engine to process both incoming and outgoing soap messages. Actually am just running a simple example and have developed some custom handlers and modules, so now I wanted to see how much delay it takes during the invocation of those custom handlers. I'll really appreciate if someone can help me on this. Thanks Inder -Original Message- From: Paul Fremantle [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 06, 2007 5:43 AM To: axis-user@ws.apache.org Subject: Re: Axis2: How to measure the time taken by Axis2 engine to process the request/reply SOAP messages Interesting blog! Thanks for the pointer. I'm not sure I understand the comment about single threading. Certainly AB allows you to send multiple simultaneous requests. If its singlethreaded then its pretty cunning about it. Anyway, part of the HTTPCore project in Apache has a multi-threaded Java version of AB. This also supports chunking and HTTP1.1 keepalive. Unfortunately there isn't a build yet, but we've used it to test Synapse. https://svn.apache.org/repos/asf/jakarta/httpcomponents/httpcore/tags/4.0-al pha4/contrib/src/main/java/org/apache/http/contrib/benchmark/ We will take a look at hosting a build on wso2.org. Paul On 6/6/07, Michele Mazzucco [EMAIL PROTECTED] wrote: Paul, maybe ab is not the best tool to use... http://weblogs.java.net/blog/sdo/archive/2007/03/ab_considered_h.html Michele On Wed, 2007-06-06 at 08:47 +0100, Paul Fremantle wrote: We did some benchmarking of Axis2 here http://wso2.org/library/91 We used ab which is part of the Apache HTTPD project. Paul On 6/6/07, Inder Dhillon [EMAIL PROTECTED] wrote: Hello I'll really appreciate if someone can suggest me how to measure the time taken by Axis2 engine to process the messages? Thanks Inder - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: soap or soapenv
Um, I respectufully disagree. Both messages look like soap 1.1 to me. The xml prefix (soap, soapenv etc) is just a shorthand in xml and the exact chosen by a given framework is immaterial. I struggle to believe that .Net can't accept a message with a different prefix. Can you post the exact error you get back? Thanks, David On 28/05/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: The former is SOAP version 1.2, and the latter is SOAP version 1.1. I'm new to Axis but I'm betting that there is a way to coerce it into using soap 1.1 (or maybe there's a way to coerce .net to use 1.2?) Michael Davis -Original Message- From: Harrie Hazewinkel [mailto:[EMAIL PROTECTED] Sent: Friday, May 25, 2007 6:24 PM To: axis-user@ws.apache.org Subject: soap or soapenv Hallo, I would like to know if someone can tell me the difference between the usage of 'soap' and 'soapenv'? I see the usage of 'soapenv' in the axis2 package, but .NET uses 'soap' and does not accept the 'soapenv'. Is there some parameter one can set for this? message ?xml version=1.0 encoding=utf-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/ envelope/ soapenv:Header . /soapenv:Header soapenv:Body .. /soapenv:Body /soapenv:Envelope and ?xml version=1.0 encoding=utf-8? soap:Envelope xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:soap=http:// schemas.xmlsoap.org/soap/envelope/ soap:Header . /soap:Header soap:Body . /soap:Body /soap:Envelope Thanks by advance, Harrie -- Funambol - Professional Services, Netherlands http://www.funambol.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] axis2-aar-maven-plugin how excludes axis2 jar files from .aar?
As far as I can tell, we currently only support including no
dependences or all dependencies. My gut instinct is that it shouldn't
be hard to add/change an option to only exclude org.apache.axis2 group
dependencies. Please open a Jira [1] about this and someone will
hopefully get to it.
David
[1] https://issues.apache.org/jira/secure/Dashboard.jspa
On 29/05/07, LuCa [EMAIL PROTECTED] wrote:
but I didn't want to exclude all the dependencies jars , only axis2
jar (since I'm sure it's avaiable at the server).
At 17:59 29/5/2007, you wrote:
Did you try includeDependencies = false?
plugin
groupIdorg.apache.axis2/groupId
artifactIdaxis2-aar-maven-plugin/artifactId
version${version}/version
extensionstrue/extensions
configuration
servicesXmlFile${basedir}/src/sample/axisversion/META-INF/services.xml/servicesXmlFile
includeDependenciesfalse/includeDependencies
/configuration
/plugin
On 5/29/07, LuCa [EMAIL PROTECTED] wrote:
I've tried, but it looks like the usage is wrong, cause there is no effect:
the jars are included anyway
fileSets
fileSet
outputDirectory target/aar/lib / outputDirectory
excludes
exclude axis2*.jar / exclude
/ excludes
/ fileSet
/ fileSets
At 17:49 29/5/2007, you wrote:
If you look at the documentation, you'll notice where it talks about
fileSets. You can use it to manage includes/excludes. I've not tried
this, but it should be what you're looking for.
Eddie Bush
Software Analyst
Clinical Reference Laboratory
bushe at crlcorp dot com
-Original Message-
From: LuCa [ mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 29, 2007 3:37 PM
To: axis-user@ws.apache.org
Subject: [Axis2] axis2-aar-maven-plugin how excludes axis2 jar files
from .aar?
When using axis2-aar-maven-plugin to create the .aar deploy file, how
configure the plugin to exclude the axis2*.jar files from the .aar
generated?
tks,
Luciana
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas :: http://davanum.wordpress.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting use of Ws-Addressing header mandatory at service
It is possible, simply put the UsingAddressing element defined in [1] in your service WSDL with wsdl:required=true on it. I hope that helps, David [1] http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#uaee On 24/05/07, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello, I know the client can mandate the use of WS-Addressing bij use of mustUnderstand. But i would like to impose the policy that all clients must add a WS-addressing header on messages to a Axis2 1.1.1 service. I can not find any information how to configure the service that it mandates this. Is it uncommon to have such a policy? Thanks. Kind regards, Erwin -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsa:Action header emitted from client with value
I'll look into the generation problem tomorrow. I know it used to work, but that was a while ago. The urn: thing is not standardised, please, please use something that is refleted in a WSDL e.g. soapAction, wsaw:Action, or in the near future wsam:Action I'm currently sitting an interop testing session for the WS-A Metadata spec and it's going well :-) Hopefully the spec will get finalised soon, and in line with that, I'll put the support for it in Axis2. David On 22/05/07, Jim Alateras [EMAIL PROTECTED] wrote: Steven, if you look through the mailing list you'll see how I was able to resolve this by modifying my wsdl to use soapAction and wsa:Action attributes. Not ideal but it gets around my problem for the time being. cheers /jima Steven E. Harris wrote: Jim Alateras [EMAIL PROTECTED] writes: Is there any way around this aside from editing the generated stub and service.xml file. Not that I know of, and I haven't heard of any movement toward a fix. I'm surprised this problem isn't biting more people. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsa:Action header emitted from client with value
On 20/04/07, Steven E. Harris [EMAIL PROTECTED] wrote: David Illsley [EMAIL PROTECTED] writes: If you look at the now-defunct WS-A WSDL binding spec [1] or its replacement the WS-A Metadata spec [2], the wsa:Action is specified at the abstract level, not the binding level. Just to make sure I follow you, are you saying that a default Action should be constructed from parts of the /interface/ definition, and not the /binding/ definition? That's how I read the specifications you referenced. -- Steven E. Harris Yes, that's my understanding. David -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: wsa:Action header emitted from client with value
Hi Keith, uh... I beg to differ. If you look at the now-defunct WS-A WSDL binding spec [1] or its replacement the WS-A Metadata spec [2], the wsa:Action is specified at the abstract level, not the binding level. [1] http://www.w3.org/TR/2006/CR-ws-addr-wsdl-20060529/#actioninwsdl [2] http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-wsdl.html?content-type=text/html;%20charset=utf-8#actioninwsdl David On 20/04/07, keith chapman [EMAIL PROTECTED] wrote: Hi Steven, Looks like we will have to do this after 1.2 since it might need a bit of refractoring (Too late to go into the 1.2 release). Currently the wsaAction is set to the axisOperation but it should be going into axisBindingOperation instead as the wsaAction is a binding specific property. Will fix it after the 1.2 release. Thanks, Keith. On 4/17/07, Steven E. Harris [EMAIL PROTECTED] wrote: keith chapman [EMAIL PROTECTED] writes: I'll have a look into this. Thanks. Let me know if you need me to supply any additional detail. -- Steven E. Harris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Keith Chapman WSO2 Inc. Oxygen for Web Services Developers. http://wso2.org/ -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis fault accessing WCF web service with WsHttpBinding
;);
_operationClient.getOptions().setExceptionToBeThrownOnSOAPFault(true);
// create SOAP envelope with that payload
org.apache.axiom.soap.SOAPEnvelope env=null;
//Style is Doc.
env =
toEnvelope(getFactory(_operationClient.getOptions().getSoapVersionURI()),
param4,
optimizeContent(new javax.xml.namespace.QName(,
MyOperation1)));
//adding SOAP headers
_serviceClient.addHeadersToEnvelope(env);
// create message context with that soap envelope
org.apache.axis2.context.MessageContext _messageContext = new
org.apache.axis2.context.MessageContext() ;
_messageContext.setEnvelope(env);
// add the message contxt to the operation client
_operationClient.addMessageContext(_messageContext);
_operationClient.setCallback(new
org.apache.axis2.client.async.Callback() {
public void onComplete(
org.apache.axis2.client.async.AsyncResult result) {
java.lang.Object object =
fromOM(result.getResponseEnvelope().getBody().getFirstElement(),
org.tempuri.MyServiceStub.MyOperation1Response.class,
getEnvelopeNamespaces(result.getResponseEnvelope())
);
callback.receiveResultMyOperation1((org.tempuri.MyServiceStub.MyOperation1Response)
object);
}
public void onError(java.lang.Exception e) {
callback.receiveErrorMyOperation1(e);
}
});
org.apache.axis2.util.CallbackReceiver _callbackReceiver = null;
if ( _operations[0].getMessageReceiver()==null
_operationClient.getOptions().isUseSeparateListener()) {
_callbackReceiver = new org.apache.axis2.util.CallbackReceiver();
_operations[0].setMessageReceiver(
_callbackReceiver);
}
//execute the operation client
_operationClient.execute(false);
}
clearly it is sending SOAP Action which is matching with SOAP action
in the wsdl for the method.
Can any one help on this issue?
Thanks
Shantanu
--
Graduate Student
Department of Computer Science,
San Diego State University
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] WS-Addressing WSDL binding
We have support for the WSDL binding spec and I intend to implement the WSA-Metadata spec once it's finalised. There's no problem with having an implementation of both, it's just less than ideal for a JSR. David On 29/03/07, Paul Fremantle [EMAIL PROTECTED] wrote: Angel We are just fine AFAIK Paul On 3/29/07, Angel Todorov [EMAIL PROTECTED] wrote: Hi guys, I just came across this on the JAX-WS homepage: = You might have noticed that JAX-WS 2.1 RI download link takes you to an Error page. We have fixed that to say what is really going on with JAXWS 2.1 specification and RI. So why we have to do this? Well, WS-Addressing WSDL Binding spec was normatively referenced by JAX-WS 2.1 specification and was in CR state when the spec and RI went final few weeks back. After we released JAXWS 2.1 RI and the spec, it came to our attention that WS-Addressing Working Group has decided to drop this spec and instead do WS-Addressing Metadata (a Working Draft now). So in effect the Binding spec is dead and JAXWS 2.1 specification references it! = Is Axis2 also prone to this problem ? Thanks in advance. Regards, Angel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] EndpointReference Serialization
On 28/03/07, Francesco Leone [EMAIL PROTECTED] wrote: Hi! I have some trouble with EndpointReference serialization, in particular when i use an Endpoint Reference with ReferenceParameters, i have a notSerializable exception referred to org.apache.axiom.om.impl.llom .OMElementImpl . I guess that the OMElement used ad ReferenceParameters is the origin of the problem, i just take a look to the EndpointReference source of axis2-1.1.1 but i find that there is a Map to collect the OMElement rappresenting ReferenceParameters but there are not in the class the readObject and writeObject method to permit the serialization of this map of OMElement. One possible solution is to transform EndpointReference in the realtive OMElement (by EndpointReferenceHelper), then serializing with OMElement.serialize() and then, after the deserialization, transforming the OMElement in EndpointReference. A little bit complicated..any suggestions? Thanks Francesco Leone Yes, try Axis2 1.2-RC1. The EndpointReference class now implements read/writeObject which correctly serialises the EPR to/from XML. David -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.1.1 addressing disable replyTo
Can you point me at the specification profile or is it a private one? Which addressing spec level are you using? 2004/08 or 2005/08? Cheers, David On 15/03/07, Erwin Reinhoud [EMAIL PROTECTED] wrote: Hello David, No i do not. But we do need addressing to comply with a certain specification profile. This however does not include the ReplyTo field. Hence the question how to disable this. What Roshan might be the solution. Erwin -Oorspronkelijk bericht- Van: David Illsley [mailto:[EMAIL PROTECTED] Verzonden: woensdag 14 maart 2007 19:06 Aan: axis-user@ws.apache.org Onderwerp: Re: axis2 1.1.1 addressing disable replyTo Hi, Are you using a wire-async invocation (separate connections for request and response)? David On 14/03/07, Punnoose, Roshan [EMAIL PROTECTED] wrote: I'm not exactly sure how you can set a property to disable the replyTo. Anyway, when I had to do something similar, I had to create my own addressing module, which is actually where this is happening, and register it instead of the default addressing module on the client side. (Maybe on the server side too?) Roshan Punnoose Phone: 301-497-6039 From: Erwin Reinhoud [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 12:14 PM To: axis-user@ws.apache.org Subject: axis2 1.1.1 addressing disable replyTo Hello, I cant seem to find how to disable some addressing fields for client or service. In code on client side i set the options for to, from , messageid, but in the send message i also see the ReplyTo field, how do i disable this? As for the sevice side it is enabled, but do not know how to make a distinction here either. Greetings, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2 1.1.1 addressing disable replyTo
Hi, Are you using a wire-async invocation (separate connections for request and response)? David On 14/03/07, Punnoose, Roshan [EMAIL PROTECTED] wrote: I'm not exactly sure how you can set a property to disable the replyTo. Anyway, when I had to do something similar, I had to create my own addressing module, which is actually where this is happening, and register it instead of the default addressing module on the client side. (Maybe on the server side too?) Roshan Punnoose Phone: 301-497-6039 From: Erwin Reinhoud [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 14, 2007 12:14 PM To: axis-user@ws.apache.org Subject: axis2 1.1.1 addressing disable replyTo Hello, I cant seem to find how to disable some addressing fields for client or service. In code on client side i set the options for to, from , messageid, but in the send message i also see the ReplyTo field, how do i disable this? As for the sevice side it is enabled, but do not know how to make a distinction here either. Greetings, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AXIS2: wsaw:Action question in the MTOM sample
Hi Shantanu, The wsaw:Action value on the output element will be used as the wsa:Action header value for response messages for that operation. This is particularly useful in the scenario you describe where the ReplyTo sends the message to another service. In that case the response message must have the correct wsa:Action for that operation. wsaw:Action lets you do that. A marker to state that use of a ReplyTo is mandatory is still under discussion at the W3C I'm afraid. It'll probably be a WS-Policy solution allowing specification that the service supports either 'anonymous ReplyTo' or 'npn-anonymous ReplyTo' or both. Hope that helps, David On 13/03/07, Shantanu Sen [EMAIL PROTECTED] wrote: In the MTOM sample the following wsaw:action is specified in the wsdl for the output message: --- wsdl:output message=tns:AttachmentResponse wsaw:Action=http://schemas.xmlsoap.org/wsdl/MTOMServicePortType/AttachmentResponse; --- What is the significance of this and how does AXIS2 handle this? If I want to use asynchronous invocation of this service which requires the service to send the response message to a different address (using replyTo), how would I change the WSDL? I understand that I would have to change the client to set the wsa:replyTo on the message, but my question is that how can I state in the WSDL that a separate replyTo address need to be specified by the client when invoking the service? Thanks, Shantanu Sen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [axis2] out of memory error
If it's the client, and there's a single CallbackReceiver, I've been suspicious about the code in there which never removes anything from it's callbackStore HashMap. I haven't had a chance to look into this in detail though. David On 13/03/07, Davanum Srinivas [EMAIL PROTECTED] wrote: OOM on the client or on the server? -- dims On 3/13/07, Michele Mazzucco [EMAIL PROTECTED] wrote: Hi all, I'm running a quite-fast asynchronous client (it sends about 2 req/ second) with vm arg. -Xms256m -Xmx1024m, the following configuration context final ConfigurationContext configurationContext = ConfigurationContextFactory.createConfigurationContextFromFileSystem (null, null); HttpClient httpClient = new HttpClient(new MultiThreadedHttpConnectionManager()); configurationContext.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE); configurationContext.setProperty(HTTPConstants.CACHED_HTTP_CLIENT, httpClient); There's only one ServiceClient object sending all requests (and thus it cleans up only at the end) with only one Callback object waiting for all responses, but after some time (about 1 hour) I get a java.lang.OutOfMemoryError. What can I do? Thanks in advance, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 OMElement getAttribute
Can I suggest trying with a QName which includes the xsi namespace value?
David
On 08/03/07, Gul Onural [EMAIL PROTECTED] wrote:
I have an OMElement response coming from my web services written in Axis2.
?xml version=1.0 encoding=UTF-8?
tns:XResponse xmlns:tns=mynamespace
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
tns:myObject xsi:type=tns:Type1_T
tns:nameaName/tns:name
/tns:myObject
/tns:XResponse
On the web services client side, I am trying to determine the xsi:type
attribute value, using following code snippet,
but type (in below code snippet) seems to be null :
// response is the OMElement shown above.
Iterator it = response.getChildElements();
while (it.hasNext()) {
OMElement element = (OMElement) it.next();
if ((element.getLocalName()).compareTo(myObject) == 0) {
OMAttribute type = element.getAttribute(new QName(xsi,
type));
// type is NULL…Why ?
}
Could you please let me know what I am doing wrong ?
Thanks
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing SOAP binding question
No you don't, you just need to confugure the client to 'use a separate listener' and the runtime will do the rest. See the EchoBlockingDualClient sample described at [1] David [1] http://ws.apache.org/axis2/1_1_1/userguide-samples.html On 05/03/07, Jim Alateras [EMAIL PROTECTED] wrote: Callner, David A. wrote: No problem are there any examples of such a scenario? How does this work? Do I need to specify something in the binding section indicating that the response will be sent asynchronously and in a separate connection to that of the request. cheers /jima -Original Message- From: Jim Alateras [mailto:[EMAIL PROTECTED] Sent: Monday, March 05, 2007 1:41 PM To: axis-user@ws.apache.org Subject: Re: WS-Addressing SOAP binding question David Illsley wrote: Hi, What do you mean by support? Hi David. If i have a request reply operation that is bound to SOAP/HTTP and I supply a non-anonymous URI for the ReplyTo address can I get behaviour specified in 5.2.1 below. Will the generated stubs and skeletons work? cheers /jima David On 05/03/07, Jim Alateras [EMAIL PROTECTED] wrote: I was wondering whether axis2 supports the following WS-Addressing SOAP Binding requirements from (http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/) 5.2 Use of Non-Anonymous Addresses in SOAP Response Endpoints 5.2.1 SOAP 1.1/HTTP When http://www.w3.org/2005/08/addressing/anonymous; is not specified for the response endpoint, then the message SHOULD be part of a binding that supports not returning a SOAP envelope in the HTTP response (e.g. see [SOAP 1.1 Request Optional Response HTTP Binding]). Any response message SHOULD be sent using a separate connection and using the address value specified by response endpoint. Note that other specifications MAY define special URIs that have other behaviors (similar to the anonymous URI). 5.2.2 SOAP 1.2 When http://www.w3.org/2005/08/addressing/anonymous; is not specified for the response endpoint, then any response SHOULD NOT be the http://www.w3.org/2003/05/soap/mep/OutboundMessage property of the same instance of the SOAP request-response MEP [SOAP 1.2 Adjuncts]. For instance, a SOAP 1.2 HTTP binding that supports a one-way MEP could put the reply message in a separate one-way MEP and a separate HTTP request. As in SOAP 1.1/HTTP, note that other specifications MAY define special URIs that have other behaviors (similar to the anonymous URI) cheers /jima - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Response SOAP and WSA action
Hi, It depends on how you're configuring Axis2. You can either add a wsaw:Action attribute in your wsdl or an outputActionMapping element to the operation configuration in your services.xml David On 06/03/07, Punnoose, Roshan [EMAIL PROTECTED] wrote: Hi, How do I set up the response of a web service to have a specific SOAP action or a WSA action String? Roshan Punnoose Phone: 301-497-6039 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing SOAP binding question
Hi, What do you mean by support? David On 05/03/07, Jim Alateras [EMAIL PROTECTED] wrote: I was wondering whether axis2 supports the following WS-Addressing SOAP Binding requirements from (http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/) 5.2 Use of Non-Anonymous Addresses in SOAP Response Endpoints 5.2.1 SOAP 1.1/HTTP When http://www.w3.org/2005/08/addressing/anonymous; is not specified for the response endpoint, then the message SHOULD be part of a binding that supports not returning a SOAP envelope in the HTTP response (e.g. see [SOAP 1.1 Request Optional Response HTTP Binding]). Any response message SHOULD be sent using a separate connection and using the address value specified by response endpoint. Note that other specifications MAY define special URIs that have other behaviors (similar to the anonymous URI). 5.2.2 SOAP 1.2 When http://www.w3.org/2005/08/addressing/anonymous; is not specified for the response endpoint, then any response SHOULD NOT be the http://www.w3.org/2003/05/soap/mep/OutboundMessage property of the same instance of the SOAP request-response MEP [SOAP 1.2 Adjuncts]. For instance, a SOAP 1.2 HTTP binding that supports a one-way MEP could put the reply message in a separate one-way MEP and a separate HTTP request. As in SOAP 1.1/HTTP, note that other specifications MAY define special URIs that have other behaviors (similar to the anonymous URI) cheers /jima - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Regarding to next Release.
Deepal, So is this RC a release candidate or a beta? If it's an RC then it should closely reflect what'll be in 1.2 and there should only really be bug fixes in the month of March. Is that the plan? David On 23/02/07, Deepal Jayasinghe [EMAIL PROTECTED] wrote: Hi Dennis ; The date we are targeting is end of march , and hoping to release RC end of this month. Thanks Deepal What is the plan for 1.2, dims? If we can have a target date it'd help me, and other developers, get changes completed in time. - Dennis Davanum Srinivas wrote: Yura, Let's target #1 for 1.2 release. If you can please try the nightly snapshots and log JIRA bugs. That would really help us. As Ajith mentioned we've added more support and need to know what exactly fails in the wsdl/schema to make sure we fix it. thanks, dims On 2/22/07, Yura Tkachenko [EMAIL PROTECTED] wrote: Hi, Axis2 developers. I have a question regarding to such things: Currently ADB binding doesn't supports complex type extensions. Thats absolutely brokes work for Salesforce Apex API 8.0 (partner.wsdl). And I really expect the fix of that. Xbeans databinding support enterprise wsdl of Salesforce, but unfortunatelly it doesn't supports partner wsdl due to xmlbeans databinding doesn't supports xsd:any feature. Although xmlbeans 2.2.0 which is used by Axis2 1.1.1 supports xsd:any (see http://xmlbeans.apache.org/docs/2.0.0/guide/conHandlingAny.html). Is any workaround to make Salesforce Apex API 8.0 (partner wsdl) workable with Axis2. Jibx databinding currently also doesn't support xsd:any. Is it feasible to use JAXB bindings for that? So as I can see Axis2 totally doesn't support Salesforce partner wsdl. Can you provide some approximately estimate when Axis2 will be feasible for Salesforce? P.S.: Expect you kind advise what databinding is the best for WS client/server? I saw very good performance for JAXB bindings (http://wso2.org/library/588). -- Thanks in advance, Yura. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: [Axis2] To many open connections
Hi Ted,
Out of interest, what os/jvm are you using?
Thanks,
David
On 20/02/07, Michele Mazzucco [EMAIL PROTECTED] wrote:
Ted,
if you want more control you can use OperationClient, but it won't give
you more control over connections. Instead you could try something like
this:
// inititalization code
ConfigurationContext multiThreadedConfigurationContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(null,
null);
MultiThreadedHttpConnectionManager connectionManager = new
MultiThreadedHttpConnectionManager();
HttpConnectionManagerParams params = new HttpConnectionManagerParams();
// you can tune these values
params.setDefaultMaxConnectionsPerHost(5);
params.setMaxTotalConnections(200);
params.setStaleCheckingEnabled(true);
connectionManager.setParams(params);
HttpClient httpClient = new HttpClient(connectionManager);
multiThreadedConfigurationContext.setProperty(
HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
multiThreadedConfigurationContext.setProperty(
HTTPConstants.CACHED_HTTP_CLIENT, httpClient);
ServiceClient sender = null;
try {
new ServiceClient(multiThreadedConfigurationContext, null);
// set options end send message
} finally {
if (sender != null) {
try {
sender.cleanup();
} catch (AxisFault e) {
// take the most appropriate action
}
}
}
Michele
On Tue, 2007-02-20 at 11:01 +, [EMAIL PROTECTED]
wrote:
Hi,
thanks for fast reply, yes I'm using a ServiceClient to send my messages. I
tryed out the connection reuse and I called the clean() method after each service
call. It doesn't show any affects, the error is still present and there are still
to many open connections wich leads to the address already in use error. Is there
a way, not to use the ServiceClient for the calls to avoid this Problem and have
more control over the connections?
Thanks again,
Ted
- Ursprüngliche Mail
Von: Michele Mazzucco [EMAIL PROTECTED]
An: axis-user@ws.apache.org
Gesendet: Dienstag, den 20. Februar 2007, 11:21:59 Uhr
Betreff: Re: [Axis2] To many open connections
Ted,
supposing you're using a ServiceClient object so send your messages, do
you call the cleanup() method in a finally block?
BTW, try to have a look here http://wso2.org/library/87 and here
http://wso2.org/library/165
Hope this helps,
Michele
On Tue, 2007-02-20 at 10:11 +, [EMAIL PROTECTED]
wrote:
Hi,
trying to stress an Axis2 implemented application after round about 3960 calls an
Address already in use error occours, because of the huge bunch of open
connections. Is there a way to instruct Axis to close these connections?
Thanks a lot
Ted
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Hacking WS-AddressingConstants to support WSE2.0
I suspect the problem is that the original string constant has been compiled into the class in the mar. I suggest re-building the mar using classes compiled against your patched Constants file. David On 13/02/07, Brecht Yperman [EMAIL PROTECTED] wrote: Hi, I'm trying to communicate with a WSE2.0-enhanced webservice. So far I got the requests 90% equal using this: in my code client.getOptions().setProperty(AddressingConstants.WS_ADDRESSING_VERSION, Submission.WSA_NAMESPACE); in ServiceClient (in sendReceive method) getOptions().setAction(mc.getAxisOperation().getSoapAction()); I'm having but one problem left, I think, and that's the namespace of WS-Addressing. In my example request this is 2004/03, the constant Submission.WSA_NAMESPACE is 2004/08. I tried to change the axis2-kernel-1.1.jar file, changing the constants containing the namespace to http://schemas.xmlsoap.org/ws/2004/03/addressing in the file org.apache.axis2.addressing.AddressingConstants$Submission. In my client code this is used, but in the addressing.mar-file, some other class seems to be used as this: if (Submission.WSA_NAMESPACE.equals(addressingVersionFromCurrentMsgCtxt)) always returns false and the content of addressingVersionFromCurrentMsgCtxt is http://schemas.xmlsoap.org/ws/2004/03/addressing Does anyone know how I can fix this, or is there a proper way to do this, or…? Thanks, Brecht -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: setOperationContext on service
Try: MessageContext.getCurrentMessageContext() The setOperationContext() stuff was removed prior to Axis2 1.1 because it wasn't thread safe. David On 01/02/07, George Stanchev [EMAIL PROTECTED] wrote: Hi Angerl, Yeah, I did this and it works fine. I just wanted to avoid it and use the out-of-the-box mechanism for obtaining the message context since there were several examples out there on the web indicating that setOperationContext should work. After I posted my question on this list I looked around the message receivers code and found out that currently (in 1.1.1) the DependencyManager class which is called inirectly from the invokeBusinessLogic method does attempt to call init method with ServiceContext parameter. This however, does not help me much. After initialization, the service class is cached on the service context and subsequent calls would not invoke the init method. Also I don't know if there is an easy way to get the message context from the service context. I guess I am stuck with my own custom receiver. Thanks! Best Regards, George -Original Message- From: Angel Todorov [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 11:56 AM To: axis-user@ws.apache.org Subject: Re: setOperationContext on service Hi George, You can probably implement a custom message receiver that extends any of the default ones, and inject any object in your service implementation. In this way you basically gain control over the lifecycle of the business logic. Regards, Angel On 2/1/07, George Stanchev [EMAIL PROTECTED] wrote: Hi, How can I get a hold of message context within a service? There are several places on the web that show that if the service implements a void setOprationContext(OperationContext) method, it will get called prior to the operation method. However I have not been successful in getting this method called. Several of the unit tests use void init(MessageContext) But this is not called either. Is there any other way to get a hold of the message context? I have tried the RawXMLInOutMessageReceiver and the RPCMessageReceiver. Has the method signature changed? Has it been removed? Thanks in advance! George ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS Addressing - Not able to Get MessageID in Response.
/ /phaseOrder phaseOrder type=INfaultflow phase name=PreDispatch/ phase name=soapmonitorPhase/ phase name=Dispatch class=org.apache.axis2.engine.DispatchPhase handler name=RequestURIBasedDispatcher class=org.apache.axis2.engine.RequestURIBasedDispatcher order phase=Dispatch/ /handler handler name=SOAPActionBasedDispatcher class=org.apache.axis2.engine.SOAPActionBasedDispatcher order phase=Dispatch/ /handler handler name=AddressingBasedDispatcher class=org.apache.axis2.engine.AddressingBasedDispatcher order phase=Dispatch/ /handler handler name=SOAPMessageBodyBasedDispatcher class=org.apache.axis2.engine.SOAPMessageBodyBasedDispatcher order phase=Dispatch/ /handler handler name=InstanceDispatcher class=org.apache.axis2.engine.InstanceDispatcher order phase=PostDispatch/ /handler /phase !-- user can add his own phases to this area -- phase name=OperationInFaultPhase/ phase name=RMPhase/ /phaseOrder phaseOrder type=Outfaultflow !-- user can add his own phases to this area -- phase name=RMPhase/ phase name=soapmonitorPhase/ phase name=OperationOutFaultPhase/ phase name=PolicyDetermination/ phase name=MessageOut/ /phaseOrder /axisconfig Am I missing anything? Thanks Sunil -Original Message- From: David Illsley [mailto:[EMAIL PROTECTED] Sent: Thursday, December 07, 2006 2:52 PM To: axis-user@ws.apache.org Subject: Re: WS Addressing - Not able to Get MessageID in Response. Hi, Yes, you should get ws-addressing (including a messageid) in the response. My best guess is that the addressing modules isn't engaged on the server (though it obviously is in the client). David On 07/12/06, Sunil Choudhari -X (suchaudh - Satyam at Cisco) [EMAIL PROTECTED] wrote: Hi, Find below my request: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:wsa=http://www.w3.org/2005/08/addressing; soapenv:Header wsa:Tohttp://127.0.0.1:8080/Axis2/services/fromws/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:154D4ED7795855F43111655301223211/wsa:MessageID wsa:ActionechoString/wsa:Action /soapenv:Header soapenv:Body ns1:echoString xmlns:ns1=http://sunilfromws.org/; ns1:Textecho1/ns1:Text ns1:Sequencesequence1/ns1:Sequence /ns1:echoString /soapenv:Body /soapenv:Envelope I am getting following response: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body ns1:echoStringResponse xmlns:ns1=http://sunilfromws.org/; xmlns:tns=http://ws.apache.org/axis2; ns1:EchoStringReturnecho1---sequence1/ns1:EchoStringReturn /ns1:echoStringResponse /soapenv:Body /soapenv:Envelope WS Addressing is engaged and I was expectring MessageID in response. Could any one help me to confirm my assumption? And if it is true , please let me know why I am not receiving same. I am using Axis 2.0 Version 1.0 Thanks, Sunil -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Exception thrown at Predispatch Phase
http://log.illsley.org/2006/10/05/a-required-header-representing-a-message-addressing-property-is-not-present/ David On 06/12/06, korges [EMAIL PROTECTED] wrote: The Exception is: org.apache.axis2.AxisFault: A required header representing a Message Addressing Property is not present What exactly does that mean? Thanks -Original Message- From: Deepal Jayasinghe [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 6. Dezember 2006 21:58 To: axis-user@ws.apache.org Subject: Re: [Axis2] Exception thrown at Predispatch Phase Do you have the exception that you got , if so please post that to the list , otherwise its bot hard me to figure out the issue. Thanks Deepal korges wrote: Hi I'm still trying to get my service work on smtp I got some problems dispatching my message. An Exception is thrown during the Predispatch Phase, after the transport and security phase are passed. I'm not able to clarify where the exception exactly was thrown from. Which handler/ classes are involved in the predispatch phase? Does anybody know what the mistake could be, because http works perfect, only with smtp I got this problem. Thanks a lot for your Help! Best regards Nicholas -Original Message- From: Jim Alateras [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 6. Dezember 2006 20:29 To: axis-user@ws.apache.org Subject: cannot download wsdl2code maven2 plugin I am having problems with the instructions on the wsdl2code maven plugin as specified here (http://ws.apache.org/axis2/tools/1_1/maven-plugins/maven-wsdl2code-plugin. h tml). When I run mvn wsdl2code:wsdl2code I get the following error, indicating that it cannot locate the plugin. C:\projects\maven2\calculatormvn wsdl2code:wsdl2code [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'wsdl2code'. [INFO] artifact org.apache.maven.plugins:maven-wsdl2code-plugin: checking for updates from alternative [INFO] artifact org.apache.maven.plugins:maven-wsdl2code-plugin: checking for updates from central [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-wsdl2code-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Thu Dec 07 06:24:07 EST 2006 [INFO] Final Memory: 1M/3M [INFO] Here is my pom ?xml version=1.0 encoding=UTF-8?project modelVersion4.0.0/modelVersion groupIdcalculator/groupId artifactIdcalculator/artifactId version0.0.1/version descriptionThe calculator service does add/description pluginRepositories pluginRepository idalternative/id nameMaven2 Repository/name urlhttp://people.apache.org/repo/m2-ibiblio-rsync-repository/url /pluginRepository /pluginRepositories build plugins plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId executions execution goals goalwsdl2code/goal /goals /execution /executions configuration packageNamecom.comware.ws.calculator/packageName /configuration /plugin /plugins /build /project Any help would be appreciated. cheers /jima - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Deepal The highest tower is built one brick at a time - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.15.9/573 - Release Date: 05.12.2006 16:07 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.15.9/573 - Release Date: 05.12.2006 16:07 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Best way to log service method accesses?
If this is in Axis2 I'd suggest a handler inserted after the dispatch phase in which case you can get the operation name from the AxisOperation which in turn you can obtain from the MessageContext. In general the SOAPAction can't and shouldn't be relied upon. David On 05/12/06, D. Kreft [EMAIL PROTECTED] wrote: I'm setting up a table in my database to log accesses to my service. I'm grabbing the username, client host and script name from the SOAP header, but I'd also like to log the name of the method called. What's the best way to do this? Can the SOAPAction HTTP header be reliably counted on for this task, or must I pick apart the SOAP body? Or better yet, is there a pre-fabricated solution I could drop into my service to take care of this for me? Surely this has been done before. :-) -dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 1.1.1] accessing context within service skeleton
Hi Nirmit,
There was a threading problem with that model so it was removed and
replaced with access to a ThreadLocal MessageContext from which you
can access the OperationContext.
The code you need is:
org.apache.axis2.context.MessageContext.getCurrentMessageContext().getOperationContext()
David
On 01/12/06, robert lazarski [EMAIL PROTECTED] wrote:
If your goal is to get a param from services.xml, at least one way is
via AxisService. One way these days to get that on startup as you were
doing before is to implement the ServiceLifeCycle interface. See the
spring tutorial for an example:
http://ws.apache.org/axis2/1_1/spring.html#261
HTH,
Robert
On 12/1/06, Nirmit Desai [EMAIL PROTECTED] wrote:
Hi,
I recently switched to the 1.1.1 latest nighty. In my service
implementation, I used to capture the operationContext by implementing the
method:
public void setOperationContext(OperationContext oCtx)
{
}
This was supposedly called before any of the service operation was being
called and it workd fine. However, in the latest nightly this does not
work, this method is not being called.
My purpose is to access a service parameter from my services.xml. Can
anyone tell me how I can do this in the 1.1.1 era?
Thanks,
-Nirmit
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing setReplyto method name namespace
Hi, I'm not an expert on RAD6 by any stretch of the imagination but I don't think it supports operation identification based on the wsa:Action field. If that's the case then you'll need to make the response message body from JBoss look like the request message that RAD6 is expecting. David On 30/11/06, Vaibhav Pandey [EMAIL PROTECTED] wrote: Hi Michele, The process cycle is that: my client sends a message to a service hosted on JBoss with all WS addressing properties like replyTo, faultTo, from, to etc. already mentioned in the request header. Now, the request header in this case has a replyTo set to the address of the service installed on RAD6(service up and running). Now when i start the process then the message as specified goes to the JBoss service and then based on the replyTo address hits the RAD6 server. After this i get a SOAP fault from RAD6 (also shown on the RAD6 console- so this means that my message had reached the destination but then its throwing the SOAP fault that it cannot map the operation name to any operation name in the service). This is absolutely fine as the RAD servie excepts a string type param and the response from JBoss also contains a string param but there is no method name of the destination rad service in this reponse (as a SOAP response does not contain a method name) so its unable to map to the response from Jboss to rad. My basic aim is that i want to simulate a scenario wherein i pass a string (or any data) from a clent to a service (using WS addessing) and then that service after manipulating that data sends it to another sevice hosted somewhere else. Is the way i m implementing it correct or is there any other way ? Also what i feel is that if i want to add the method name in the response of Jboss service then may be will have to use SAAJ api's but think thats not a correct way of doing !! My client uses axis 2 Api's. Kindly guide. Regards, Vaibhav -Original Message- From: Michele Mazzucco [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 29, 2006 9:49 PM To: axis-user@ws.apache.org Subject: Re: WS-Addressing setReplyto method name namespace Hi Vaibhav, Is the message sent by jboss to RAD6 a forward or a result message? In the first case you must be sure the target service is available on RAD6, in the latter one you have to fix the addressing information contained into the SOAP header before the message hits the RAD6 host (by default the replyTo fields is set to the client so if you send the message somewhere else the receiver will fail). And what about the exception your service is throwing? Try to post it and maybe we can help you. Regards, Michele On 29 Nov 2006, at 13:54, Vaibhav Pandey wrote: Hi, need help on an issue relating to WS Addressing: m working on the following configuration with WS addressing using axis2 :- axis2 + Jboss + IBM Rad6 m trying to generate a scenario wherein i send a SOAP request using axis2 to an axis2 WS deployed on JBOSS. Then the reply of this service should be forwarded to another WS hosted on RAD6. Everythng wrks perfectly fine except the fault that i get from RAD6 stating that it could not map the request to a particular operation axis2 client --SOAPReq (over HTTP)-- WS1 (axis2 WS on jboss) -- SOAPRes (over HTTP)-- WS2 (on IBM Rad6) The reason for this is that the SOAP response generated by my WS1 will have the namespace and method response of WS1 and no information pertaining to the WS2, but as the replyto header is set to the WS2 EPR, the request gets forwarded and then the WS2 generates a fault. I tried with all types of WS viz doc/literal, rpc/encoded, rpc/ literal etc but got the same fault !! Is there any way by which i can set these configurations(method name of WS2 and namespace through my client itself or any other way) ?? Kindly guide me as to what m i supposed to do ?? Regards, Vaibhav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Target Resolvers
Hi, I use a TargetResolver when embedding Axis2 in a non-open source project. There is an example TargetResolver in the integration tests [1] if you want to see the kinds of things which are possible, David [1] http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/deployment/ On 14/11/06, Yadav, Yogendra (IT) [EMAIL PROTECTED] wrote: Hi, I found this in sandesh2 source. Are there any target resolver implementations ? DO they work with AXIS2 at the moment ? Can you point me to some ? !-- = -- !-- Target Resolvers -- !-- = -- !-- Uncomment the following and specify the class name for your TargetResolver to add -- !-- a TargetResolver. TargetResolvers are used to process the To EPR for example to -- !-- choose a server in a cluster -- !--targetResolvers-- !--targetResolver class= /-- !--/targetResolvers-- -yogen NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Message Addressing Property is not present
Does the axis2.xml you are specifying engage the addressing module. If it's not engaged then no validation of the WS-Addressing headers occurs so the mission wsa:Action will be ignored. David On 08/11/06, Chris Iken [EMAIL PROTECTED] wrote: Hi David, Thanks for your response. The Axis2 TCP transport puts no wsa:Action element into the message, but it works (see below). So I think my implementation misses something. I recently found out that the TCP transport doesn't work when I add explicitly an axis2.xml (even with the axis2.xml from axis2-kernel-1.1-RC2.jar: System.setProperty(org.apache.axis2.Constants.AXIS2_CONF, G:\\2006\\axis2\\axis2.xml); When adding an axis2.xml I also receive the same exception: A required header representing a Message Addressing Property is not present. With the standard configuration it's working very well: ConfigurationContextFactory .createConfigurationContextFromFileSystem(dir, null) Thanks for any help, Chris ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Totcp://localhost:6060/axis2/services/MyService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous /wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:7736F16A48C252BD5F11629790178581/wsa:MessageID /soapenv:Header soapenv:Body example1:echo xmlns:example1=tcp://localhost:6060/axis2/services/MyService example1:TextAxis2 Echo String /example1:Text /example1:echo /soapenv:Body /soapenv:Envelope -Ursprüngliche Nachricht- Von: David Illsley [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 8. November 2006 09:49 An: axis-user@ws.apache.org Betreff: Re: [Axis2] Message Addressing Property is not present It's not valid to use some WS-Addressing headers but leave out wsa:Action. You should either generate the correct action or turn off WS-Addressing. David On 07/11/06, Chris Iken [EMAIL PROTECTED] wrote: Hi, I try to start my custom transport on axis2 (1.1 RC2, Win XP) with the MyService example. On the receiver side I get the following exception: A required header representing a Message Addressing Property is not present. In detail: wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail/soapenv:Header soapenv:Body soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail/ Obviously, the attribute wsa:Action can't be automatically computed. I take the TCP example as template. Why it works there? Thanks for any hints, Chris Received SOAP on receiver side: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Topure://localhost:5000/axis2/services/MyService/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:5FC41846E89DADC73D11629095719191/wsa:MessageID /soapenv:Header soapenv:Bodyexample1:echo xmlns:example1=pure://localhost:5000/axis2/services/MyService example1:TextAxis2 Echo String /example1:Text /example1:echo /soapenv:Body /soapenv:Envelope Axis2 Fault SOAP: ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:wsa=http://www.w3.org/2005/08/addressing; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsa:Tohttp://www.w3.org/2005/08/addressing/anonymous/wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3.org/2005/08/addressing/none/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid:B7A6B83EC42774F1F311629117150911/wsa:MessageID wsa:Actionhttp://www.w3.org/2005/08/addressing/fault/wsa:Action wsa:RelatesTo wsa:RelationshipType=http://www.w3.org/2005/08/addressing/reply;urn:uuid:D 1FC51978E28C164D011629116118831 /wsa:RelatesTo wsa:FaultDetail wsa:ProblemHeaderQNamewsa:Action/wsa:ProblemHeaderQName /wsa:FaultDetail/soapenv:Header soapenv:Body soapenv:Fault faultcodewsa:MessageAddressingHeaderRequired/faultcode faultstringA required header representing a Message Addressing Property is not present/faultstring detail/ /soapenv:Fault /soapenv:Body /soapenv:Envelope - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development
Re: Axis/Tomcat http timeout
With Axis2 you can use the 'DualClient' programming model to use separate transport connections for request and response [1]. David [1] http://ws.apache.org/axis2/1_0/userguide3.html#EchoNonBlockingDualClient On 30/10/06, xu cai [EMAIL PROTECTED] wrote: Is there any configuration on this ? how to handle long-duration service in Axis ? -thanks xu -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to debug?
Off the top of my head I think the problem is that the server cannot send the response message to the ReplyTo EPR for some reason. If you're setting the ReplyTo explicitly please check that you are getting it right ;-) and if not then check that the server can open a connection to the port that the client is opening (the simplest way to determine the port is to look at the ReplyTo in the request message). David On 24/10/06, Hoskins, Stephen [EMAIL PROTECTED] wrote: Hi all My apologies if this is a naive question. Basically, my Axis2 service is not working and I would like to know how I determine what the problem is. I am using Axis2 1.0 and Tomcat 5.0. My service classes log that they instantiated okay and the Axis admin screens for the service all look correct. But whenever I run a test client against the service I get a stack trace: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService; nested exception is: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService; nested exception is: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService; nested exception is: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:223) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:589) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOper ation.java:328) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisO peration.java:279) at com.logicacmg.gt.testservice.axis.generated.TestServiceStub.viewProduct( TestServiceStub.java:133) at com.logicacmg.gt.testservice.control.SimpleClient.getProduct(SimpleClien t.java:55) at com.logicacmg.gt.testservice.control.SimpleClient.init(SimpleClient.ja va:37) at com.logicacmg.gt.testservice.control.SimpleClient.main(SimpleClient.java :23) Caused by: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService; nested exception is: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:305) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(Common sHTTPTransportSender.java:207) ... 28 more Caused by: org.apache.axis2.AxisFault: Axis2 transport error : /services/TestService at org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSend er.java:117) at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageW ithCommons(CommonsHTTPTransportSender.java:299) ... 29 more There is nothing useful in the logs, the request is not reaching my service classes. This is my second service, the first one worked fine. My current idea is to insert some more log messages into the Axis2 source code to trace what is happening, but surely there must be a better approach? Many thanks Steve Hoskins This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help! Where can I get maven-itest-plugin-1.0.jar
Significant portions of the Apache infrastructure were physically relocated over the weekend. Sorry, but it loooks like ws.zones... isn't back up yet. David On 24/10/06, Stephen Milne [EMAIL PROTECTED] wrote: Chinthaka, http://ws.zones.apache.org/~dims/maven/maven-itest-plugin/plugins/maven-itest-plugin-1.0.jar . doesn't seem to work. Are there any other links I can get this jar from. thanks Stephen Stephen Milne Eran Chinthaka [EMAIL PROTECTED] urce.lk To axis-user@ws.apache.org 20/10/2006 16:08 cc Subject Please respond to Re: Help! Where can I get [EMAIL PROTECTED] maven-itest-plugin-1.0.jar he.org Robert, Seems that particular jars is not available in any of the repos mentioned in plugin download command. I think that is why the mail came from Stephen. Stephen, You might wanna try this : http://ws.zones.apache.org/~dims/maven/maven-itest-plugin/plugins/maven-itest-plugin-1.0.jar . -- Chinthaka robert lazarski wrote: Forgot that the 1.0 docs url does not work anymore ... try this from the soon to be released 1.1 docs: maven plugin:download -DgroupId=maven-itest-plugin -DartifactId=maven-itest-plugin -Dversion=1.0 -Dmaven.repo.remote=http://people.apache.org/repository/maven,http://www.ibiblio.org/maven Robert On 10/20/06, robert lazarski [EMAIL PROTECTED] wrote: Does this help? http://ws.apache.org/axis2/faq.html#d1 Robert On 10/20/06, Stephen Milne [EMAIL PROTECTED] wrote: Hi, I have been trying to compile Axis2 with maven-1.0.2 and fail due to not being able to get maven-itest-plugin-1.0.jar Does anyone know where can I get this jar from. None of the links work in http://maven.apache.org/maven-1.x/plugins/itest/downloads.html http://people.apache.org/repository/maven/plugins/ indicates that it is available as a jar but is infact a zip with no jar. thanks Stephen Milne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] (See attached file: signature.asc) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Urgently need helps - problems with Axis2
Also, please ensure that the addressing module is engaged in both the client and the server. The 'and WSA Action = null;' bit suggests that it is not in one or both places. David On 03/10/06, Brian De Pradine [EMAIL PROTECTED] wrote: Hello, Can you try as._getServiceClient().getOptions().setAction(traceJob); Cheers Brian DePradine Web Services Development IBM Hursley External +44 (0) 1962 816319 Internal 246319 If you can't find the time to do it right the first time, where will you find the time to do it again? Xia Zhao [EMAIL PROTECTED] wrote on 03/10/2006 10:45:16: Hi Thilina, I add as._getServiceClient().getOptions().setAction(urn:traceJob); to my client code, but nothing changed. Still came out with the same error trace. What else could be? Thanks. Xia -Original Message- From: Thilina Gunarathne [mailto:[EMAIL PROTECTED] Sent: 03 October 2006 10:28 To: axis-user@ws.apache.org Subject: Re: Urgently need helps - problems with Axis2 try adding, as._getServiceClient().getOptions().setAction(urn:traceJob); to your client code ~Thilina On 10/3/06, Xia Zhao [EMAIL PROTECTED] wrote: Hi, Sorry to bother you guys again. I really need this help to carry on with rest of my work. Can someone please post me a simple working example or give some hints on my codes? The error trace and codes are posted here: http://issues.apache.org/jira/browse/AXIS2-1283?page=all Thanks very much. Xia -- http://webservices.apache.org/~thilina/ http://thilinag.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing Interoperability Problem
Off the top of my head, if you'd prefer not to modify the generated classes so you can regenerate them easily, you can do: stub._getServiceClient().getOptions().setProperty(...) David On 18/09/06, Anthony Bull [EMAIL PROTECTED] wrote: Thanks, that worked awesome. I was using a code generated client, so I had to go in to the client Stub class and add that line of code to its constructor. Thanks for the quick response. Anthony. David Illsley wrote: You need to do the following to the Options object you use to comfigure your client: options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION, org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE); Which will tell the addressing module to add 2004/08 headers rather than 2005/08 headers. Hope this helps, David On 18/09/06, Anthony Bull [EMAIL PROTECTED] wrote: Hi, I have been working on a proof of concept interoperability project between .NET WSE 3.0 and Axis2 web services for a client. For this I have a .NET WSE 3.0 client and service (written by another vendor) and corresponding Java Axis2 client and service (written by me). Everything is running nearly fine, in all combinations of these apps, including encrypted messages over HTTPS. The one issue I came across that I could not resolve nicely is that the WSE 3.0 service only recognises soap messages with WS-Addressing namespaces of August-2004. Any SOAP messages sent from my Axis 2 Java client to both the Axis 2 service and WSE 3.0 service have a WS-addressing namespace of August-2005 (which if I understand correctly is also the namespace for May-2006 WS-Addressing). The .NET service does not accept these messages, and returns an error. The vendor that wrote the client/server says that WSE 3.0 cannot be upgraded to use the new addressing spec, and that WSE will not officially be updated anytime soon to support it. This leaves the ball in my court only, in order to fix this. The Axis2 service recognises the older addressing specification that the .NET client is sending to it (2004/08), but I have not been able to configure it so I can send Axis2 messages with this older addressing specification. Looking at the Axis2 code, the 2005/08 specification namespace is hard-coded into the Java classes. The only way I could get it to work is to do my own build of the Axis2 addressing module and change the hardcoded namespace to be 2004/08. While this works, it is dodgy and probably won't work correctly when other modules that are built on top of addressing are added. The addressing module page for Axis 2 states that This is an implementation of WS-Addressing submission version (2004-08) and WS-Addressing 2005-08 versions.. My question is, how do I get my Axis2 code to generate messages that use the 2004-08 specification? cheers, Anthony Bull. -- - Anthony Bull Senior Developer Black Coffee Software Ltd Level 13, Compudigm House, 49 Boulcott Street PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mob +64 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - Anthony Bull Senior Developer Black Coffee Software Ltd Level 13, Compudigm House, 49 Boulcott Street PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mob +64 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender
Re: Axis2 and dotNet interoperateability
Looks to me like you need to engage the addressing module in the axis2 server so that there are addressing headers in the response. See the Axis2 documentaton for how to do this. David On 21/09/06, scott ken [EMAIL PROTECTED] wrote: My C# client (.dotNet 2.0 and WSE 3.0) generated the following SOAP message. ?xml version='1.0' encoding='utf-8'? soap:Envelope xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd; xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addressing; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xop=http://www.w3.org/2004/08/xop/include; xmlns:soap=http://schemas.xmlsoap.org/soap/envelope/; xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; soap:Header wsa:Action / wsa:MessageID urn:uuid:8a8309c1-a21d-48ff-aa52-2647bb377cfc /wsa:MessageID wsa:ReplyTo wsa:Address http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous /wsa:Address /wsa:ReplyTo wsa:To http://localhost:8080/axis2/services/CMBWebService /wsa:To wsse:Security wsu:Timestamp wsu:Id=Timestamp-010f1103-934c-44fb-8778-1251c874e66e wsu:Created2006-09-20T23:12:21Z/wsu:Created wsu:Expires2006-09-20T23:17:21Z/wsu:Expires /wsu:Timestamp /wsse:Security /soap:Header soap:Body MyAppRequest /MyAppRequest /soap:Body /soap:Envelope The reply message from Axis2 server is ?xml version='1.0' encoding='utf-8'? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header / soapenv:Body MyAppReply /MyAppReply /soapenv:Body /soapenv:Envelope The C# client encountered this exception Unhandled Exception: Microsoft.Web.Services3.Addressing.AddressingFault: Message Information Header Required --- Micros oft.Web.Services3.Addressing.AddressingFormatException: WSE202: The Action header is required when other address headers are present. --- End of inner exception stack trace --- at Microsoft.Web.Services3.Addressing.AddressingHeaders.CheckValid() at Microsoft.Web.Services3.Addressing.AddressingHeaders.Load(SoapEnvelope envelope) at Microsoft.Web.Services3.SoapEnvelope.PostLoad(Boolean loadAddressing) at Microsoft.Web.Services3.SoapEnvelope.PostLoad() at Microsoft.Web.Services3.SoapEnvelope.Load(XmlReader reader) at Microsoft.Web.Services3.Mime.XopDocument.LoadStartPart(MimePart startPart) at Microsoft.Web.Services3.Mime.XopDocument.LoadFromXopPackage(String contentType, Stream stream) at Microsoft.Web.Services3.Xml.SoapEnvelopeReaderWrapper..ctor(SoapClientMessage message, String messageContentType) at Microsoft.Web.Services3.WebServicesClientProtocol.GetReaderForMessage(SoapClientMessage message, Int32 bufferSize) at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) I guess it's about some configuration on client side or server side. Can someone tell me what the fix is? Thanks in advance, vick Stay in the know. Pulse on the new Yahoo.com. Check it out. -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing Interoperability Problem
You need to do the following to the Options object you use to comfigure your client: options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION, org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE); Which will tell the addressing module to add 2004/08 headers rather than 2005/08 headers. Hope this helps, David On 18/09/06, Anthony Bull [EMAIL PROTECTED] wrote: Hi, I have been working on a proof of concept interoperability project between .NET WSE 3.0 and Axis2 web services for a client. For this I have a .NET WSE 3.0 client and service (written by another vendor) and corresponding Java Axis2 client and service (written by me). Everything is running nearly fine, in all combinations of these apps, including encrypted messages over HTTPS. The one issue I came across that I could not resolve nicely is that the WSE 3.0 service only recognises soap messages with WS-Addressing namespaces of August-2004. Any SOAP messages sent from my Axis 2 Java client to both the Axis 2 service and WSE 3.0 service have a WS-addressing namespace of August-2005 (which if I understand correctly is also the namespace for May-2006 WS-Addressing). The .NET service does not accept these messages, and returns an error. The vendor that wrote the client/server says that WSE 3.0 cannot be upgraded to use the new addressing spec, and that WSE will not officially be updated anytime soon to support it. This leaves the ball in my court only, in order to fix this. The Axis2 service recognises the older addressing specification that the .NET client is sending to it (2004/08), but I have not been able to configure it so I can send Axis2 messages with this older addressing specification. Looking at the Axis2 code, the 2005/08 specification namespace is hard-coded into the Java classes. The only way I could get it to work is to do my own build of the Axis2 addressing module and change the hardcoded namespace to be 2004/08. While this works, it is dodgy and probably won't work correctly when other modules that are built on top of addressing are added. The addressing module page for Axis 2 states that This is an implementation of WS-Addressing submission version (2004-08) and WS-Addressing 2005-08 versions.. My question is, how do I get my Axis2 code to generate messages that use the 2004-08 specification? cheers, Anthony Bull. -- - Anthony Bull Senior Developer Black Coffee Software Ltd Level 13, Compudigm House, 49 Boulcott Street PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mob +64 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Addressing Interoperability Problem
Martin, Both will work but the Options class is the 'official' Client API. David On 18/09/06, Martin Gainty [EMAIL PROTECTED] wrote: David- Are there advantages of using the Options.setProperty over setting properties via MessageContext such as MessageContext.setProperty(WS_ADDRESSING_VERSION,Submission.WSA_NAMESPACE)? Thanks, Martin -- * This email message and any files transmitted with it contain confidential information intended only for the person(s) to whom this email message is addressed. If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the original message without making a copy. Thank you. - Original Message - From: David Illsley [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, September 18, 2006 5:04 AM Subject: Re: WS-Addressing Interoperability Problem You need to do the following to the Options object you use to comfigure your client: options.setProperty(org.apache.axis2.addressing.AddressingConstants.WS_ADDRESSING_VERSION, org.apache.axis2.addressing.AddressingConstants.Submission.WSA_NAMESPACE); Which will tell the addressing module to add 2004/08 headers rather than 2005/08 headers. Hope this helps, David On 18/09/06, Anthony Bull [EMAIL PROTECTED] wrote: Hi, I have been working on a proof of concept interoperability project between .NET WSE 3.0 and Axis2 web services for a client. For this I have a .NET WSE 3.0 client and service (written by another vendor) and corresponding Java Axis2 client and service (written by me). Everything is running nearly fine, in all combinations of these apps, including encrypted messages over HTTPS. The one issue I came across that I could not resolve nicely is that the WSE 3.0 service only recognises soap messages with WS-Addressing namespaces of August-2004. Any SOAP messages sent from my Axis 2 Java client to both the Axis 2 service and WSE 3.0 service have a WS-addressing namespace of August-2005 (which if I understand correctly is also the namespace for May-2006 WS-Addressing). The .NET service does not accept these messages, and returns an error. The vendor that wrote the client/server says that WSE 3.0 cannot be upgraded to use the new addressing spec, and that WSE will not officially be updated anytime soon to support it. This leaves the ball in my court only, in order to fix this. The Axis2 service recognises the older addressing specification that the .NET client is sending to it (2004/08), but I have not been able to configure it so I can send Axis2 messages with this older addressing specification. Looking at the Axis2 code, the 2005/08 specification namespace is hard-coded into the Java classes. The only way I could get it to work is to do my own build of the Axis2 addressing module and change the hardcoded namespace to be 2004/08. While this works, it is dodgy and probably won't work correctly when other modules that are built on top of addressing are added. The addressing module page for Axis 2 states that This is an implementation of WS-Addressing submission version (2004-08) and WS-Addressing 2005-08 versions.. My question is, how do I get my Axis2 code to generate messages that use the 2004-08 specification? cheers, Anthony Bull. -- - Anthony Bull Senior Developer Black Coffee Software Ltd Level 13, Compudigm House, 49 Boulcott Street PO Box 10-192 The Terrace Wellington, New Zealand [EMAIL PROTECTED] Ph +64 4 472 8818 Fax +64 4 472 8811 Mob +64 021 303 692 - www.bcsoft.co.nz --- This email may contain confidential or privileged information, and is intended for use only by the addressee, or addressees. If you are not the intended recipient please advise the sender immediately and do not copy, use or disclose the contents to any other person or organisation. Black Coffee Software Ltd accepts no responsibility for viruses received with this email, or to any changes made to the original content. Any views or opinions expressed in this email may be personal to the sender and are not necessarily those of Black Coffee Software Ltd. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands
Re: [AXIS2] persistence
I don't want to be too glib, but have you thought about a database? Perhaps with Hibernate/Java Persistence? David On 08/08/06, Fabien Couble [EMAIL PROTECTED] wrote: Hi Deepal Thx for your response... but actually I'd like to know how I can implement persistence in Axis. I mean I need to use an object which must be persitent!! Can you advise me on some ways to do that?? This is the description of what I need to do: I'm implementing a protocol in which I have to manage an array of resources. Indeed, I have to add, get or delete resources from that array. Actually, when a web service receives a request from a client, depending on the request, the web service has to get, add or delete the resource in the array. Please, could you help me?? Fabien - Original Message - From: Deepal Jayasinghe [EMAIL PROTECTED] To: axis-user@ws.apache.org Sent: Monday, August 07, 2006 6:07 PM Subject: Re: [AXIS2] persistence Hi Fabien; Please see my comments below; Fabien Couble wrote: Hi all, I have checked that AXIS 2 don't support the persistence by default. Yes , Axis2 does not support persistence. That's why, by surfing on the Web, I have found that to make a service persistent, we have to configure the service.xml file with the following line: Thats wrong , there wont be any change even if you add something like that . In addition to that this is not the way you specify parameter in Axis2 , it should be smt like parameter name=fooMyParaValue/parameter parameter name=scope value=/value// I did that by replacing the word value by application. Normally, that mean that a service will be intanciated for all the requests until the server Tomcat is shutdown. Consequently, the service should be persistent... However, it doesn't work... If you want to deploy your service in application scope then you need to do add an attribute called scope into your services.xml as follows service name=foo scope=application /service Is it the good way to do this? HOw can I do that?? Thx fabien This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- Thanks, Deepal ~Future is Open~ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Illsley - IBM Web Services Development - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2 1.0] MessageContext is null
OK, so I'm a little familiar with this code and there are a couple of
relevant things:
1. it should be init(ServiceContext sc) not MessageContext which may
be why init isn't being called. You may be able to get what you want
from the ServiceContext depending on what you're looking for.
2. DependencyManager.configureBusinessLogicProvider causes
setOperationContext(OperationContext oc) to be called on the
implementation class if it exists. From this you gan get the
associated MessageContext(s).
Hope that helps,
David
On 01/08/06, Nirmit Desai [EMAIL PROTECTED] wrote:
Hi all,
I have generated my implementation class from a WSDL and added the
following method:
private MessageContext msgCtx=null;
public void init(MessageContext ctx){
msgCtx=ctx;
System.out.println(init called..context:+ctx);
}
But, the init method is never called!! (I checked the service logs for
output, and I see other System outs). Due to that the service methods throw
a null pointer exception when trying to access msgCtx.
I read somewhere that a MessageReceiver is supposed to call the init
method. WSDL2Java generates a custom message receiver for every service
(Axis Data binding). I looked inside my message receiver and it does not
seem to be making any calls before calling the service methods except this
one:
//Inject the Message Context if it is asked for
org.apache.axis2.engine.DependencyManager.configureBusinessLogicProvider
(obj, msgContext.getOperationContext());
Any clues why init is not being called?
Thanks,
-Nirmit
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [AXIS2] soap header
Fabien,
If you want access to the SOAPHeader, you can get it through the
MessageContext. You can get this by adding the following method to
your skeleton (I think this works for all MessageReceivers):
...
OperationContext _oc;
public void setOperationContext(OperationContext oc){
_oc = oc;
}
...
and then when invoked get the MessageContext using:
MessageContext mc =_oc.getMessageContext(In);
and then get the SOAPEnvelope from mc.
If you are trying to get a WS-Addressing reference parameter (and are
using WS-Addressing 2005/08) you can just call:
_oc.getMessageContext(In).getTo().getAllReferenceParameters().get(qnameOfReferenceParameter);
David
On 31/07/06, Fabien Couble [EMAIL PROTECTED] wrote:
Hi all,
I'd like to know if it is possible to have access to the SOAP header in the
implementation of the service (skeleton). Actually, I'd like to get some
information.
If it is not possible, I suppose I have to get this information in a module!!?
Thx
Fabien
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
--
David Illsley - IBM Web Services Development
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis1 style=message in Axis2?
On 26/07/06, David Melgar [EMAIL PROTECTED] wrote: Setting the message receiver to RawXMLMessageReceiver still appears to require actionMapping to determine which method to invoke. In axis1, the specified method would receive all messages for that service. Equivalent behavior should be available in axis2 regardless of the value of the wsa:Action header. To further clarrify, the service I'm writing bridges between webservices and a non-Java object invocation mechanism. It dynamically determines what operations are allowed. This services does not know at deployment time what operations are possible. I therefore don't know all the wsa:Action header values that it might be included in request messages. Therefore I cannot declare actionMapping values in the service deployment descriptor. In case you're wondering, this service also dynamically generates WSDL to describe the discovered supported operations. Is there a way to wildcard actionMapping to say that any action maps to a method? Or to avoid the requirement for specifying an actionMapping if RawXMLMessageReceiver is used. Are there other approaches that could be used? What you are trying to do sounds pretty advanced (given that you're dynamically generating WSDL). There are a couple of options I can think of... 1. Remove the dispach phase from your Axis2 configuration and write your own MessageReceiver (which removes the need for an AxisOperation to be identified) 2. Define a single operation for the service and add a handler to the DispatchPhase which selects that operation when the RawXMLInOutReceiver will then invoke on the endpoint object. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WS-Transfer protocol using AXIS2
Hi Fabien, I've had a quick read of the WS-Transfer spec and while I think you could go many directions with the implementation, the fastest was is probably just to implement as a service. This is because the spec defines a number of operations get/put/delete and create which are not logically associated with any other services. Additionally, though the spec mentions headers, these are just WS-Addressing headers which you can get/set using the standard Axis2 addressing apis and you don't need to worry about accessing the headers. Modules are a good fit when you have to add your own handlers to process headers or add new services/operations to existing services but those don't seem to be required for implementing WS-Transfer. WSDL can be a bit ugly but is pretty logical and there is a good start with the wsdl publiushed at [1]. My suggestion is to google for a WSDL tutorial and look at the binding/port/service bit to complete the WSDL already provided (should be pretty straightforward). David [1] http://schemas.xmlsoap.org/ws/2004/09/transfer/transfer.wsdl Fabien Couble [EMAIL PROTECTED] wrote on 07/24/2006 09:18:32 AM: Hi everybody, I'd like advices concerning a project I have to do using Apache AXIS2. Actually, I have to implement the WS-Transfer protocol using Apache AXIS2. I spent time to understand how AXIS2 works and I have some questions. Maybe you could answer to them: First of all, implementing the WS-Transfer protocol consists in formatting messages in a special format and understanting these messages in order to send appropriate responses. After studying AXIS2, I have noticed its extensibility by the addition of modules. These modules can touch the message meaning the header and the body. That is why, I was wondering if it is better to use this concept or declare everything in the WSDL file describing the service? In fact, I also analysed the wsdl language and I have noticed that a SOAP binding exists which permits to specify the message format. That is why, I don't really know which method is preferable and more convenient? Moerover, if you can advise me some good documentations on the WSDL language, I would be glad to take them... Any comment is welcome! Cheers Fabien This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] 1.0 Addressing issues when access ASP.NET2.0
You can set the WSAddressing version in your client to 2004/08 by calling options.setProperty(org.apache.axis2.addressing.AddressingContants. WS_ADDRESSING_VERSION,org.apache.axis2.addressing .AddressingContants.Submission.WSA_NAMESPACE); on your Options object. Hope that helps, David Wang, Jason [EMAIL PROTECTED] wrote on 07/05/2006 12:20:36 AM: Hi, I have a urgent question. I tried to use Axis2 client with WS-Security to call APS.NET2.0 WSE3.0 Web Service. I noticed that Axis2 addressing module created addressing block using wsa= http://www.w3.org/2005/08/addressing, and ASP.NET expect http://schemas.xmlsoap.org/ws/2004/08/addressing. looks like the Axis2 used more recent ws addressing specification. How can I configure the Axis2 addressing module using the same specification as ASP.NET? When the Axis2 client call APS.NET2.0 Web Service, I got following error message from ASP.NET : == org.apache.axis2.AxisFault: System.Web.Services.Protocols. SoapHeaderException: Server unavailable, please try later --- System.ApplicationException: WSE841: An error occured processing an outgoing fault response. --- System.Web.Services.Protocols.SoapHeaderException: Microsoft. Web.Services3.Security.SecurityFault: Header http://schemas.xmlsoap.org/ws/2004/08/addressing:Action for ultimate recipient is required but not present in the message. == And the Soap message send from the client like below, soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xenc=http://www.w3.org/2001/04/xmlenc#; xmlns:wsa=http://www.w3.org/2005/08/addressing; soapenv:Header *** wsa:Tohttp://localhost:4071/dnswebservice/Service.asmx /wsa:To wsa:ReplyTo wsa:Addresshttp://www.w3. org/2005/08/addressing/anonymous/wsa:Address /wsa:ReplyTo wsa:MessageIDurn:uuid: 2284DB461796A2D85611520498383641/wsa:MessageID wsa:Actionhttp://tempuri.org/HelloWorld/wsa:Action /soapenv:Header soapenv:Body xmlns:wsu=http://docs.oasis-open. org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd wsu: Id=id-10973446 ** /soapenv:Body /soapenv:Envelope Please help. Thanks for your time. Jason - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ReplyTo is not working
Yes, I thought the RelatesTo processing was the problem you were running into (sorry for not explaining that to you). I'm glad to hear it works otherwise. I've raised the issue again on the -dev list [1]. David [1] http://marc.theaimsgroup.com/?l=axis-devm=115165383207646w=2 Michele Mazzucco [EMAIL PROTECTED] wrote on 06/30/2006 09:09:55 AM: David, actually it works if before dispatching the response you run a handler which removes the RelatesTo element from the SOAP header. Regards, Michele David Illsley wrote: Munir Badir [EMAIL PROTECTED] wrote on 06/29/2006 03:03:21 PM: Eran, thanks for answering the question. The bottom line is: - I'm trying to use the ReplyTo header. So I'll be more than thankful if you can send me the simplest example for calling a service on HTTP and getting response back via HTTP using the ReplyTo node in WS-Addressing. About the question: - I tried to use the ReplyTo header using the Axis2 userguide samples. In the Axis2 samples\userguide there is an example of a service called MyService which has three methods: echo, ping and pingF package userguide.example1; snip / } I wanted the result of the echo method call to be sent to the MyService service, and call the ping method. So I added the following options.setReplyTo(new EndpointReference(http://localhost: 8080/axis2/services/MyService)); In the EchoNonBlockingDualClient so that the result of the echo call would be sent to MyService service, and changed the result of the echo method to be ping element (for calling the ping method of MyService). snip / Maybe I don?t understand the whole point around the ReplyTo, but I expected that the EchoNonBlockingDualClient will call the MyService. echo() method and the result of this call would be sent to the MyService with the ping action, calling the ping method. But the ping method was not called at all. Thanks, Munir -Original Message- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: Thursday, June 29, 2006 4:23 PM To: axis-user@ws.apache.org Subject: Re: ReplyTo is not working Munir Badir wrote: As a result I expected that the echo method would call the ping method, but it didn?t. Can anyone help? I'm still confused in understanding the question. If you can explain a bit with your code, it will be helpful in answering this question. Thanks, Chinthaka Munir, I think I understand your scenario: You want to invoke a service and have the result sent to (and processed by) another service. I have a couple of comments based on this: 1. For that scenario you don't need a 2-way client as there will never be a response to the client (it should go to the ping service). 2. The scenario isn't currently supported by Axis2. I proposed a patch to support it a while ago that received some objections and I've been meaning to follow it up. This has reminded me about it and I'll follow up soon. 3. There is a ReplyTo based scenario which Axis2 does support, namely an asynchronous 2-way invocation where the response is sent back to the initiating client on a second connection though I don't think this matches what you're trying to do. (I think its what you've based your client on) David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] How to access the soapAction from Handlers
In short, no. The only way to get the wsaddressing action is to read the contents of the wsa:Action element. That probably doesn't help :-( but it's the case. David Illsley Michele Mazzucco [EMAIL PROTECTED] wrote on 06/29/2006 10:24:19 AM: And add urn: before it? Michele Michele Mazzucco wrote: Hi all, I've got a handler running before the transport phase. How can I get the WS addressing action there as the wsa:Action element is created later? Is it enough to get the first element local name of the SOAP body? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ReplyTo is not working
Munir Badir [EMAIL PROTECTED] wrote on 06/29/2006 03:03:21 PM: Eran, thanks for answering the question. The bottom line is: - I'm trying to use the ReplyTo header. So I'll be more than thankful if you can send me the simplest example for calling a service on HTTP and getting response back via HTTP using the ReplyTo node in WS-Addressing. About the question: - I tried to use the ReplyTo header using the Axis2 userguide samples. In the Axis2 samples\userguide there is an example of a service called MyService which has three methods: echo, ping and pingF package userguide.example1; snip / } I wanted the result of the echo method call to be sent to the MyService service, and call the ping method. So I added the following options.setReplyTo(new EndpointReference(http://localhost: 8080/axis2/services/MyService)); In the EchoNonBlockingDualClient so that the result of the echo call would be sent to MyService service, and changed the result of the echo method to be ping element (for calling the ping method of MyService). snip / Maybe I don?t understand the whole point around the ReplyTo, but I expected that the EchoNonBlockingDualClient will call the MyService. echo() method and the result of this call would be sent to the MyService with the ping action, calling the ping method. But the ping method was not called at all. Thanks, Munir -Original Message- From: Eran Chinthaka [mailto:[EMAIL PROTECTED] Sent: Thursday, June 29, 2006 4:23 PM To: axis-user@ws.apache.org Subject: Re: ReplyTo is not working Munir Badir wrote: As a result I expected that the echo method would call the ping method, but it didn?t. Can anyone help? I'm still confused in understanding the question. If you can explain a bit with your code, it will be helpful in answering this question. Thanks, Chinthaka Munir, I think I understand your scenario: You want to invoke a service and have the result sent to (and processed by) another service. I have a couple of comments based on this: 1. For that scenario you don't need a 2-way client as there will never be a response to the client (it should go to the ping service). 2. The scenario isn't currently supported by Axis2. I proposed a patch to support it a while ago that received some objections and I've been meaning to follow it up. This has reminded me about it and I'll follow up soon. 3. There is a ReplyTo based scenario which Axis2 does support, namely an asynchronous 2-way invocation where the response is sent back to the initiating client on a second connection though I don't think this matches what you're trying to do. (I think its what you've based your client on) David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] How to access the soapAction from Handlers
As far as I know you'll have to parse the document. The wsa:Action element will be found in the SOAP Header so I'd expect that due to the wonders of AXIOM the whole document won't be parsed, just the first few elements. I'm not an expert on AXIOM/parsing though.. David Michele Mazzucco [EMAIL PROTECTED] wrote on 06/29/2006 04:42:40 PM: David, can you suggest me the best way to get it from the SOAP envelope? Is parsing the full document the only way to get it? Thanks, Michele Michele Mazzucco wrote: David, I'm sorry, I was wrong. Actually it is available :). Thanks, Michele Michele Michele Mazzucco wrote: David, I realized that the first element local name is actually the operation name, and not the ws action. Thanks, Michele David Illsley wrote: In short, no. The only way to get the wsaddressing action is to read the contents of the wsa:Action element. That probably doesn't help :-( but it's the case. Yes, unfortunately it doesn't help :( since it seems to me that the wsa:Action is not available before the transport/security phase. Regards, Michele David Illsley Michele Mazzucco [EMAIL PROTECTED] wrote on 06/29/2006 10:24:19 AM: And add urn: before it? Michele Michele Mazzucco wrote: Hi all, I've got a handler running before the transport phase. How can I get the WS addressing action there as the wsa:Action element is created later? Is it enough to get the first element local name of the SOAP body? Thanks, Michele - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] What values are allowed for wsa:MessageID?
I'm not an Axis2 expert but I know a bit about WS-Addressing so here goes: Ali Sadik Kumlali [EMAIL PROTECTED] wrote on 13/04/2006 08:29:30: snip According to http://www.w3.org/2005/08/addressing schema, it can be any value. That's not entirely correct, the definition is broad but there are some requirements. The specification text requires [message id] be a valid absolute IRI while the schema requires an xs:anyURI snip 1) I need to write MessageID value to the database and therefore need to know exact size and format of it. Is there a *sender neutral* way of this? No. All you can know is that a conformant message id is an IRI 2) Although http://www.w3.org/2005/08/addressing schema does not mandate for a special format, does Axis2 expect a special pattern? The spec requires an IRI so if it did expect something I'd be more than a little surprised given the interop results. 3) Must I make sure that I can safely write MessageID without contradicting database schema constraints, if it has passed through Axis2? A quick look at the code suggests no :-( I can't see any validation of the MessageID e.g. that it is actually a valid URI/IRI Hope this helps, David
Re: [axis2] ServiceClient.disEngageModule question.
Hi Eran, thanks for the reply. It does however leave me a little confused about what ServiceClient.disEngageModule is supposed to do if not dynamically disengage a module? ;-) Thanks, David Eran Chinthaka [EMAIL PROTECTED] wrote on 11/04/2006 17:34:12: Hi David, Firstly, Axis2 doesn't support dynamic module dis-engagement, just like we do not support hot deployment of modules. This is not a bug and it is by design. Secondly, once a module is engaged globally, it can not be dis-engaged per service/operation basis. But for addressing, we have special case this, as you already know. -- Eran Chinthaka [attachment signature.asc deleted by David Illsley/UK/IBM]
[axis2] ServiceClient.disEngageModule question.
Hi, I have an axis2.xml setup to enable the addressing module globally which is being picked up in my client code. I want to disable the addressing module in the client for some calls and thought that calling MyStub._getServiceClient().disEngageModule(new QName(addressing)); would do this however it doesn't appear to have any effect. I couldn't find any documentation on this topic so am I wrong to expect to ServiceClient.disEngageModule() to disengage a globally engaged module? If so is there any way to disengage a globally engaged module for a single call or are globally engaged modules invulnerable to client code? (I'm aware of the property to disable addressing specifically but this is really a more general question). Thanks, David
Re: [axis2] ServiceClient.disEngageModule question.
Apologies for the HTML mail, with any luck this one isn't! David [EMAIL PROTECTED] wrote on 10/04/2006 17:15:02: Hi, I have an axis2.xml setup to enable the addressing module globally which is being picked up in my client code. I want to disable the addressing module in the client for some calls and thought that calling MyStub._getServiceClient(). disEngageModule(new QName(addressing)); would do this however it doesn't appear to have any effect. I couldn't find any documentation on this topic so am I wrong to expect to ServiceClient.disEngageModule() to disengage a globally engaged module? If so is there any way to disengage a globally engaged module for a single call or are globally engaged modules invulnerable to client code? (I'm aware of the property to disable addressing specifically but this is really a more general question). Thanks, David
