You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Mirza Abbas Raza <ab...@yahoo.com> on 2005/08/01 22:15:36 UTC
Axis fault reported by Sandesha: Cannot initialize URI with empty parameters.
Thanks, Jaliya. That fixed the issue I had mentioned.
However, I am facing another issue.
The test scenario is like I have the web service
client, a POJO, sitting along with an ejb in a jar on
weblogic. The test web service is hosted on
tomcat/axis on the same machine. I run the client
without sandesha and the round trip is successful.
Enter Sandesha. I added the following snippet in the
right place as described in the docs.
SandeshaContext ctx = new SandeshaContext();
ctx.initCall(call, url,
"urn:wsrm:<operation_name>",Constants.ClientProperties.IN_OUT);
Also, I added the last message and end sequence calls
in the right place. When I run the client, an axis
fault is reported:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: Cannot initialize URI with empty
parameters.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:Cannot
initialize URI with empty
parameters.
at
org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at
org.apache.axis.client.Call.invoke(Call.java:2748)
at
org.apache.axis.client.Call.invoke(Call.java:2424)
at
org.apache.axis.client.Call.invoke(Call.java:2347)
at
org.apache.axis.client.Call.invoke(Call.java:1804)
Looks like the exception happened in AddressingHeaders
class, for which I couldn't find the source. I am
guessing that Sandesha is looking for the replyTo
header for ack from the server. If that is the case, I
can't specify the replyTo address since I am just
using the libraries to make a call. The libraries may
using some arbitrary port. I tried passing
Constants.SYNCHRONOUS to SandeshaContext constructor.
However, I got the following exception:
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: ERROR: To perform the operation, ReplyTo
address must be specified
. This EPR will not be the Sandesha end point. If it
should be Sandesha end poin
t, please set the propety 'sync' to false in call.
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:ERROR:
To perform the operation,
ReplyTo address must be specified. This EPR will not
be the Sandesha end point.
If it should be Sandesha end point, please set the
propety 'sync' to false in c
all.
at
org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
y.java:32)
at
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at
org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at
org.apache.axis.client.Call.invoke(Call.java:2748)
at
org.apache.axis.client.Call.invoke(Call.java:2424)
at
org.apache.axis.client.Call.invoke(Call.java:2347)
at
org.apache.axis.client.Call.invoke(Call.java:1804)
Appreciate any help.
Thanks,
Abbas
--- jaliya@opensource.lk wrote:
> Hi Abbas,
>
> Please add the following two lines to the
> client-config.wsdd after the
> </gloabalConfiguration>
>
> <handler name="RMSender"
> type="java:org.apache.sandesha.client.RMSender"/>
> <transport name="RMTransport" pivot="RMSender"/>
>
>
> So the transport section of your client config may
> looks as follows.
>
> .....
> </globalConfiguration>
> <handler name="RMSender"
> type="java:org.apache.sandesha.client.RMSender"/>
> <transport name="java"
>
pivot="java:org.apache.axis.transport.java.JavaSender"/>
> <transport name="http"
>
pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> <transport name="local"
>
pivot="java:org.apache.axis.transport.local.LocalSender"/>
> <transport name="RMTransport" pivot="RMSender"/>
> </deployment>
>
> We will update the documents soon.
>
> Thanks,
>
> Jaliya
>
>
>
>
>
> > Hi,
> >
> > Thanks to all on the Sandesha team for their
> efforts.
> > I a question on Sandesha. However, I am not sure
> which
> > mailing list I should post on.
> >
> > We have an application, which exposes web services
> to
> > our partners and in the same way our application
> > consumes our partners' web services. My question
> here
> > is specifically when we are client to our
> partners'
> > web services.
> >
> > Our environment:
> > OS: Win2k
> > App Server: Weblogic 8.1 sp4
> > SOAP Engine: Axis 1.2.1
> > WSRM Engine: Sandesha 1.0
> >
> > Question:
> > Axis throws a fault "No client transport named
> > 'RMTransport' found!" when the web service call is
> > made. I debugged the code and found that
> > SandeshaContext initializes the Call with
> RMTransport.
> > However, in axis jar wsdd, the transport element
> for
> > RMTransport is not defined. Which class is the
> handler
> > for RMTransport? Could someone please update the
> > documentation?
> >
> > Thanks,
> > Abbas
> >
> > --- Jaliya Ekanayake <ja...@apache.org> wrote:
> >
> >> Apache Sandesha team would like to announce the
> 1.0
> >> release for Apache
> >> Sandesha
> >> WS-ReliableMessaging implementation.
> >>
> >> You can download the releases from:
> >>
> >> Source:
> >>
> >
>
http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-src.zip
> >> Binary:
> >>
> >
>
http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip
> >>
> >> Source Repository :
> >>
> >
>
http://svn.apache.org/repos/asf/webservices/sandesha/trunk/
> >>
> >> It has been three weeks since the release of the
> RC1
> >> version of Apache
> >> Sandesha. The codebase is successfully moved to
> the
> >> SVN. We have fixed
> >> all the issues that we have identified in the RC1
> >> release and the
> >> documents are also updated and the interop tests
> are
> >> tested again.
> >> After all these we would like to announce the 1.0
> >> release for Sandesha.
> >>
> >> Features:
> >>
> >> Following features are available in the release
> of
> >> Sandesha,
> >> (1) Implementation of WS-ReliableMessaging
> >> specification (February
> >> 2005). On top of Axis 1.2
> >> (2) INORDER delivery assurance.
> >> (3) Support for synchronous and asynchronous
> >> reliable exchange of
> >> messages.
> >> (4) A Client API that will make it easy for
> users
> >> to work
> >> simultaneously with different endpoints and
> >> different message
> >> sequences.
> >> (5) Updated documentation.
> >> (6) Support for WS-Policy integration.
> >> (7) Support Custom Web Service Invocation
> >> Strategies.
> >> (7) Interop Endpoint Client
> >>
> >
>
http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp
> >> Server
> >>
> >
>
http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService
> >>
> >> If you have new ideas on messaging middleware and
> >> would like to
> >> contribute to
> >> Apache Sandesha, please join us at
> >> sandesha-dev@ws.apache.org. Any
> >> contribution in the
> >> form of coding, testing, submitting improvements
> to
> >> the documentation, and
> >> reporting bugs is always welcome.
> >>
> >> More information about Sandesha is available from
> >> the Sandesha home:
> >>
> >> http://ws.apache.org/sandesha
> >>
> >> Sandesha Development Team.
> >>
> >>
> >>
> >
>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> sandesha-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail:
> >> sandesha-dev-help@ws.apache.org
> >>
> >>
> >
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Axis fault reported by Sandesha: Cannot initialize URI with empty
parameters.
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Mirza,
Sandesha does not expect users to specify the ReplyTo address
specifically. However to do request/response type web service
invocations, it needs the return EPR and will take automatically from
the Machine. If you initiate the context with Constants.SYNCHRONOUS then
it expect a separate ReplyTo address.
If you have logs please see whether you have UnknownHostException in the
log file. This means that Sandesha could not get the source URL to send
as ReplyTo address when it sends the requests. In any case if you can
send what is there in the log that would be very easy to figure out what
was the problem.
Thanks,
Jaliya
>
> ---------- Forwarded message ----------
> From: *Mirza Abbas Raza* <abbasrazam@yahoo.com
> <ma...@yahoo.com>>
> Date: Aug 2, 2005 2:15 AM
> Subject: Axis fault reported by Sandesha: Cannot initialize URI with
> empty parameters.
> To: sandesha-dev@ws.apache.org <ma...@ws.apache.org>,
> fx-dev@ws.apache.org <ma...@ws.apache.org>
>
> Thanks, Jaliya. That fixed the issue I had mentioned.
> However, I am facing another issue.
>
> The test scenario is like I have the web service
> client, a POJO, sitting along with an ejb in a jar on
> weblogic. The test web service is hosted on
> tomcat/axis on the same machine. I run the client
> without sandesha and the round trip is successful.
>
> Enter Sandesha. I added the following snippet in the
> right place as described in the docs.
>
> SandeshaContext ctx = new SandeshaContext();
> ctx.initCall(call, url,
> "urn:wsrm:<operation_name>",Constants.ClientProperties.IN_OUT);
>
> Also, I added the last message and end sequence calls
> in the right place. When I run the client, an axis
> fault is reported:
>
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
> faultSubcode:
> faultString: Cannot initialize URI with empty
> parameters.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:Cannot
> <http://xml.apache.org/axis/%7DstackTrace:Cannot>
> initialize URI with empty
> parameters.
> at
> org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java :32)
> at
> org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at
> org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java :165)
> at
> org.apache.axis.client.Call.invokeEngine(Call.java:2765)
> at
> org.apache.axis.client.Call.invoke(Call.java:2748)
> at
> org.apache.axis.client.Call.invoke(Call.java:2424)
> at
> org.apache.axis.client.Call.invoke(Call.java:2347)
> at
> org.apache.axis.client.Call.invoke(Call.java:1804)
>
> Looks like the exception happened in AddressingHeaders
> class, for which I couldn't find the source. I am
> guessing that Sandesha is looking for the replyTo
> header for ack from the server. If that is the case, I
> can't specify the replyTo address since I am just
> using the libraries to make a call. The libraries may
> using some arbitrary port. I tried passing
> Constants.SYNCHRONOUS to SandeshaContext constructor.
> However, I got the following exception:
> AxisFault
> faultCode:
> { http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
> faultSubcode:
> faultString: ERROR: To perform the operation, ReplyTo
> address must be specified
> . This EPR will not be the Sandesha end point. If it
> should be Sandesha end poin
> t, please set the propety 'sync' to false in call.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:ERROR
> <http://xml.apache.org/axis/%7DstackTrace:ERROR>:
> To perform the operation,
> ReplyTo address must be specified. This EPR will not
> be the Sandesha end point.
> If it should be Sandesha end point, please set the
> propety 'sync' to false in c
> all.
> at
> org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java:32)
> at
> org.apache.axis.SimpleChain.doVisiting (SimpleChain.java:118)
> at
> org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> at
> org.apache.axis.client.Call.invokeEngine (Call.java:2765)
> at
> org.apache.axis.client.Call.invoke(Call.java:2748)
> at
> org.apache.axis.client.Call.invoke(Call.java:2424)
> at
> org.apache.axis.client.Call.invoke(Call.java:2347)
> at
> org.apache.axis.client.Call.invoke(Call.java:1804)
>
> Appreciate any help.
>
> Thanks,
> Abbas
>
> --- jaliya@opensource.lk <ma...@opensource.lk> wrote:
>
> > Hi Abbas,
> >
> > Please add the following two lines to the
> > client-config.wsdd after the
> > </gloabalConfiguration>
> >
> > <handler name="RMSender"
> > type="java:org.apache.sandesha.client.RMSender "/>
> > <transport name="RMTransport" pivot="RMSender"/>
> >
> >
> > So the transport section of your client config may
> > looks as follows.
> >
> > .....
> > </globalConfiguration>
> > <handler name="RMSender"
> > type="java:org.apache.sandesha.client.RMSender"/>
> > <transport name="java"
> >
> pivot="java: org.apache.axis.transport.java.JavaSender"/>
> > <transport name="http"
> >
> pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> >
> pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="RMTransport" pivot="RMSender"/>
> > </deployment>
> >
> > We will update the documents soon.
> >
> > Thanks,
> >
> > Jaliya
> >
> >
> >
> >
> >
> > > Hi,
> > >
> > > Thanks to all on the Sandesha team for their
> > efforts.
> > > I a question on Sandesha. However, I am not sure
> > which
> > > mailing list I should post on.
> > >
> > > We have an application, which exposes web services
> > to
> > > our partners and in the same way our application
> > > consumes our partners' web services. My question
> > here
> > > is specifically when we are client to our
> > partners'
> > > web services.
> > >
> > > Our environment:
> > > OS: Win2k
> > > App Server: Weblogic 8.1 sp4
> > > SOAP Engine: Axis 1.2.1
> > > WSRM Engine: Sandesha 1.0
> > >
> > > Question:
> > > Axis throws a fault "No client transport named
> > > 'RMTransport' found!" when the web service call is
> > > made. I debugged the code and found that
> > > SandeshaContext initializes the Call with
> > RMTransport.
> > > However, in axis jar wsdd, the transport element
> > for
> > > RMTransport is not defined. Which class is the
> > handler
> > > for RMTransport? Could someone please update the
> > > documentation?
> > >
> > > Thanks,
> > > Abbas
> > >
> > > --- Jaliya Ekanayake < jaliya@apache.org
> <ma...@apache.org>> wrote:
> > >
> > >> Apache Sandesha team would like to announce the
> > 1.0
> > >> release for Apache
> > >> Sandesha
> > >> WS-ReliableMessaging implementation.
> > >>
> > >> You can download the releases from:
> > >>
> > >> Source:
> > >>
> > >
> >
> http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-src.zip
> > >> Binary:
> > >>
> > >
> >
> http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip
> <http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip>
> > >>
> > >> Source Repository :
> > >>
> > >
> >
> http://svn.apache.org/repos/asf/webservices/sandesha/trunk/
> <http://svn.apache.org/repos/asf/webservices/sandesha/trunk/>
> > >>
> > >> It has been three weeks since the release of the
> > RC1
> > >> version of Apache
> > >> Sandesha. The codebase is successfully moved to
> > the
> > >> SVN. We have fixed
> > >> all the issues that we have identified in the RC1
> > >> release and the
> > >> documents are also updated and the interop tests
> > are
> > >> tested again.
> > >> After all these we would like to announce the 1.0
> > >> release for Sandesha.
> > >>
> > >> Features:
> > >>
> > >> Following features are available in the release
> > of
> > >> Sandesha,
> > >> (1) Implementation of WS-ReliableMessaging
> > >> specification (February
> > >> 2005). On top of Axis 1.2
> > >> (2) INORDER delivery assurance.
> > >> (3) Support for synchronous and asynchronous
> > >> reliable exchange of
> > >> messages.
> > >> (4) A Client API that will make it easy for
> > users
> > >> to work
> > >> simultaneously with different endpoints and
> > >> different message
> > >> sequences.
> > >> (5) Updated documentation.
> > >> (6) Support for WS-Policy integration.
> > >> (7) Support Custom Web Service Invocation
> > >> Strategies.
> > >> (7) Interop Endpoint Client
> > >>
> > >
> >
> http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp
> <http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp>
> > >> Server
> > >>
> > >
> >
> http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService
> <http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService>
> > >>
> > >> If you have new ideas on messaging middleware and
> > >> would like to
> > >> contribute to
> > >> Apache Sandesha, please join us at
> > >> sandesha-dev@ws.apache.org <ma...@ws.apache.org>. Any
> > >> contribution in the
> > >> form of coding, testing, submitting improvements
> > to
> > >> the documentation, and
> > >> reporting bugs is always welcome.
> > >>
> > >> More information about Sandesha is available from
> > >> the Sandesha home:
> > >>
> > >> http://ws.apache.org/sandesha <http://ws.apache.org/sandesha>
> > >>
> > >> Sandesha Development Team.
> > >>
> > >>
> > >>
> > >
> >
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> > >> sandesha-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > >> For additional commands, e-mail:
> > >> sandesha-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> --
> "May the SourcE be with u"
> http://www.bloglines.com/blog/thilina
Re: Axis fault reported by Sandesha: Cannot initialize URI with empty
parameters.
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Mirza,
Sandesha does not expect users to specify the ReplyTo address
specifically. However to do request/response type web service
invocations, it needs the return EPR and will take automatically from
the Machine. If you initiate the context with Constants.SYNCHRONOUS then
it expect a separate ReplyTo address.
If you have logs please see whether you have UnknownHostException in the
log file. This means that Sandesha could not get the source URL to send
as ReplyTo address when it sends the requests. In any case if you can
send what is there in the log that would be very easy to figure out what
was the problem.
Thanks,
Jaliya
>
> ---------- Forwarded message ----------
> From: *Mirza Abbas Raza* <abbasrazam@yahoo.com
> <ma...@yahoo.com>>
> Date: Aug 2, 2005 2:15 AM
> Subject: Axis fault reported by Sandesha: Cannot initialize URI with
> empty parameters.
> To: sandesha-dev@ws.apache.org <ma...@ws.apache.org>,
> fx-dev@ws.apache.org <ma...@ws.apache.org>
>
> Thanks, Jaliya. That fixed the issue I had mentioned.
> However, I am facing another issue.
>
> The test scenario is like I have the web service
> client, a POJO, sitting along with an ejb in a jar on
> weblogic. The test web service is hosted on
> tomcat/axis on the same machine. I run the client
> without sandesha and the round trip is successful.
>
> Enter Sandesha. I added the following snippet in the
> right place as described in the docs.
>
> SandeshaContext ctx = new SandeshaContext();
> ctx.initCall(call, url,
> "urn:wsrm:<operation_name>",Constants.ClientProperties.IN_OUT);
>
> Also, I added the last message and end sequence calls
> in the right place. When I run the client, an axis
> fault is reported:
>
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
> faultSubcode:
> faultString: Cannot initialize URI with empty
> parameters.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:Cannot
> <http://xml.apache.org/axis/%7DstackTrace:Cannot>
> initialize URI with empty
> parameters.
> at
> org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java :32)
> at
> org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at
> org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java :165)
> at
> org.apache.axis.client.Call.invokeEngine(Call.java:2765)
> at
> org.apache.axis.client.Call.invoke(Call.java:2748)
> at
> org.apache.axis.client.Call.invoke(Call.java:2424)
> at
> org.apache.axis.client.Call.invoke(Call.java:2347)
> at
> org.apache.axis.client.Call.invoke(Call.java:1804)
>
> Looks like the exception happened in AddressingHeaders
> class, for which I couldn't find the source. I am
> guessing that Sandesha is looking for the replyTo
> header for ack from the server. If that is the case, I
> can't specify the replyTo address since I am just
> using the libraries to make a call. The libraries may
> using some arbitrary port. I tried passing
> Constants.SYNCHRONOUS to SandeshaContext constructor.
> However, I got the following exception:
> AxisFault
> faultCode:
> { http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
> faultSubcode:
> faultString: ERROR: To perform the operation, ReplyTo
> address must be specified
> . This EPR will not be the Sandesha end point. If it
> should be Sandesha end poin
> t, please set the propety 'sync' to false in call.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:ERROR
> <http://xml.apache.org/axis/%7DstackTrace:ERROR>:
> To perform the operation,
> ReplyTo address must be specified. This EPR will not
> be the Sandesha end point.
> If it should be Sandesha end point, please set the
> propety 'sync' to false in c
> all.
> at
> org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java:32)
> at
> org.apache.axis.SimpleChain.doVisiting (SimpleChain.java:118)
> at
> org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> at
> org.apache.axis.client.Call.invokeEngine (Call.java:2765)
> at
> org.apache.axis.client.Call.invoke(Call.java:2748)
> at
> org.apache.axis.client.Call.invoke(Call.java:2424)
> at
> org.apache.axis.client.Call.invoke(Call.java:2347)
> at
> org.apache.axis.client.Call.invoke(Call.java:1804)
>
> Appreciate any help.
>
> Thanks,
> Abbas
>
> --- jaliya@opensource.lk <ma...@opensource.lk> wrote:
>
> > Hi Abbas,
> >
> > Please add the following two lines to the
> > client-config.wsdd after the
> > </gloabalConfiguration>
> >
> > <handler name="RMSender"
> > type="java:org.apache.sandesha.client.RMSender "/>
> > <transport name="RMTransport" pivot="RMSender"/>
> >
> >
> > So the transport section of your client config may
> > looks as follows.
> >
> > .....
> > </globalConfiguration>
> > <handler name="RMSender"
> > type="java:org.apache.sandesha.client.RMSender"/>
> > <transport name="java"
> >
> pivot="java: org.apache.axis.transport.java.JavaSender"/>
> > <transport name="http"
> >
> pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> >
> pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="RMTransport" pivot="RMSender"/>
> > </deployment>
> >
> > We will update the documents soon.
> >
> > Thanks,
> >
> > Jaliya
> >
> >
> >
> >
> >
> > > Hi,
> > >
> > > Thanks to all on the Sandesha team for their
> > efforts.
> > > I a question on Sandesha. However, I am not sure
> > which
> > > mailing list I should post on.
> > >
> > > We have an application, which exposes web services
> > to
> > > our partners and in the same way our application
> > > consumes our partners' web services. My question
> > here
> > > is specifically when we are client to our
> > partners'
> > > web services.
> > >
> > > Our environment:
> > > OS: Win2k
> > > App Server: Weblogic 8.1 sp4
> > > SOAP Engine: Axis 1.2.1
> > > WSRM Engine: Sandesha 1.0
> > >
> > > Question:
> > > Axis throws a fault "No client transport named
> > > 'RMTransport' found!" when the web service call is
> > > made. I debugged the code and found that
> > > SandeshaContext initializes the Call with
> > RMTransport.
> > > However, in axis jar wsdd, the transport element
> > for
> > > RMTransport is not defined. Which class is the
> > handler
> > > for RMTransport? Could someone please update the
> > > documentation?
> > >
> > > Thanks,
> > > Abbas
> > >
> > > --- Jaliya Ekanayake < jaliya@apache.org
> <ma...@apache.org>> wrote:
> > >
> > >> Apache Sandesha team would like to announce the
> > 1.0
> > >> release for Apache
> > >> Sandesha
> > >> WS-ReliableMessaging implementation.
> > >>
> > >> You can download the releases from:
> > >>
> > >> Source:
> > >>
> > >
> >
> http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-src.zip
> > >> Binary:
> > >>
> > >
> >
> http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip
> <http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip>
> > >>
> > >> Source Repository :
> > >>
> > >
> >
> http://svn.apache.org/repos/asf/webservices/sandesha/trunk/
> <http://svn.apache.org/repos/asf/webservices/sandesha/trunk/>
> > >>
> > >> It has been three weeks since the release of the
> > RC1
> > >> version of Apache
> > >> Sandesha. The codebase is successfully moved to
> > the
> > >> SVN. We have fixed
> > >> all the issues that we have identified in the RC1
> > >> release and the
> > >> documents are also updated and the interop tests
> > are
> > >> tested again.
> > >> After all these we would like to announce the 1.0
> > >> release for Sandesha.
> > >>
> > >> Features:
> > >>
> > >> Following features are available in the release
> > of
> > >> Sandesha,
> > >> (1) Implementation of WS-ReliableMessaging
> > >> specification (February
> > >> 2005). On top of Axis 1.2
> > >> (2) INORDER delivery assurance.
> > >> (3) Support for synchronous and asynchronous
> > >> reliable exchange of
> > >> messages.
> > >> (4) A Client API that will make it easy for
> > users
> > >> to work
> > >> simultaneously with different endpoints and
> > >> different message
> > >> sequences.
> > >> (5) Updated documentation.
> > >> (6) Support for WS-Policy integration.
> > >> (7) Support Custom Web Service Invocation
> > >> Strategies.
> > >> (7) Interop Endpoint Client
> > >>
> > >
> >
> http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp
> <http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp>
> > >> Server
> > >>
> > >
> >
> http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService
> <http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService>
> > >>
> > >> If you have new ideas on messaging middleware and
> > >> would like to
> > >> contribute to
> > >> Apache Sandesha, please join us at
> > >> sandesha-dev@ws.apache.org <ma...@ws.apache.org>. Any
> > >> contribution in the
> > >> form of coding, testing, submitting improvements
> > to
> > >> the documentation, and
> > >> reporting bugs is always welcome.
> > >>
> > >> More information about Sandesha is available from
> > >> the Sandesha home:
> > >>
> > >> http://ws.apache.org/sandesha <http://ws.apache.org/sandesha>
> > >>
> > >> Sandesha Development Team.
> > >>
> > >>
> > >>
> > >
> >
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> > >> sandesha-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > >> For additional commands, e-mail:
> > >> sandesha-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> --
> "May the SourcE be with u"
> http://www.bloglines.com/blog/thilina
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: Axis fault reported by Sandesha: Cannot initialize URI with empty
parameters.
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Mirza,
Sandesha does not expect users to specify the ReplyTo address
specifically. However to do request/response type web service
invocations, it needs the return EPR and will take automatically from
the Machine. If you initiate the context with Constants.SYNCHRONOUS then
it expect a separate ReplyTo address.
If you have logs please see whether you have UnknownHostException in the
log file. This means that Sandesha could not get the source URL to send
as ReplyTo address when it sends the requests. In any case if you can
send what is there in the log that would be very easy to figure out what
was the problem.
Thanks,
Jaliya
>
> ---------- Forwarded message ----------
> From: *Mirza Abbas Raza* <abbasrazam@yahoo.com
> <ma...@yahoo.com>>
> Date: Aug 2, 2005 2:15 AM
> Subject: Axis fault reported by Sandesha: Cannot initialize URI with
> empty parameters.
> To: sandesha-dev@ws.apache.org <ma...@ws.apache.org>,
> fx-dev@ws.apache.org <ma...@ws.apache.org>
>
> Thanks, Jaliya. That fixed the issue I had mentioned.
> However, I am facing another issue.
>
> The test scenario is like I have the web service
> client, a POJO, sitting along with an ejb in a jar on
> weblogic. The test web service is hosted on
> tomcat/axis on the same machine. I run the client
> without sandesha and the round trip is successful.
>
> Enter Sandesha. I added the following snippet in the
> right place as described in the docs.
>
> SandeshaContext ctx = new SandeshaContext();
> ctx.initCall(call, url,
> "urn:wsrm:<operation_name>",Constants.ClientProperties.IN_OUT);
>
> Also, I added the last message and end sequence calls
> in the right place. When I run the client, an axis
> fault is reported:
>
> AxisFault
> faultCode:
> {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
> faultSubcode:
> faultString: Cannot initialize URI with empty
> parameters.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:Cannot
> <http://xml.apache.org/axis/%7DstackTrace:Cannot>
> initialize URI with empty
> parameters.
> at
> org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java :32)
> at
> org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at
> org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java :165)
> at
> org.apache.axis.client.Call.invokeEngine(Call.java:2765)
> at
> org.apache.axis.client.Call.invoke(Call.java:2748)
> at
> org.apache.axis.client.Call.invoke(Call.java:2424)
> at
> org.apache.axis.client.Call.invoke(Call.java:2347)
> at
> org.apache.axis.client.Call.invoke(Call.java:1804)
>
> Looks like the exception happened in AddressingHeaders
> class, for which I couldn't find the source. I am
> guessing that Sandesha is looking for the replyTo
> header for ack from the server. If that is the case, I
> can't specify the replyTo address since I am just
> using the libraries to make a call. The libraries may
> using some arbitrary port. I tried passing
> Constants.SYNCHRONOUS to SandeshaContext constructor.
> However, I got the following exception:
> AxisFault
> faultCode:
> { http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
> <http://schemas.xmlsoap.org/soap/envelope/%7DServer.generalException>
> faultSubcode:
> faultString: ERROR: To perform the operation, ReplyTo
> address must be specified
> . This EPR will not be the Sandesha end point. If it
> should be Sandesha end poin
> t, please set the propety 'sync' to false in call.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:ERROR
> <http://xml.apache.org/axis/%7DstackTrace:ERROR>:
> To perform the operation,
> ReplyTo address must be specified. This EPR will not
> be the Sandesha end point.
> If it should be Sandesha end point, please set the
> propety 'sync' to false in c
> all.
> at
> org.apache.sandesha.client.RMSender.invoke(RMSender.java:125)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrateg
> y.java:32)
> at
> org.apache.axis.SimpleChain.doVisiting (SimpleChain.java:118)
> at
> org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at
> org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> at
> org.apache.axis.client.Call.invokeEngine (Call.java:2765)
> at
> org.apache.axis.client.Call.invoke(Call.java:2748)
> at
> org.apache.axis.client.Call.invoke(Call.java:2424)
> at
> org.apache.axis.client.Call.invoke(Call.java:2347)
> at
> org.apache.axis.client.Call.invoke(Call.java:1804)
>
> Appreciate any help.
>
> Thanks,
> Abbas
>
> --- jaliya@opensource.lk <ma...@opensource.lk> wrote:
>
> > Hi Abbas,
> >
> > Please add the following two lines to the
> > client-config.wsdd after the
> > </gloabalConfiguration>
> >
> > <handler name="RMSender"
> > type="java:org.apache.sandesha.client.RMSender "/>
> > <transport name="RMTransport" pivot="RMSender"/>
> >
> >
> > So the transport section of your client config may
> > looks as follows.
> >
> > .....
> > </globalConfiguration>
> > <handler name="RMSender"
> > type="java:org.apache.sandesha.client.RMSender"/>
> > <transport name="java"
> >
> pivot="java: org.apache.axis.transport.java.JavaSender"/>
> > <transport name="http"
> >
> pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> >
> pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="RMTransport" pivot="RMSender"/>
> > </deployment>
> >
> > We will update the documents soon.
> >
> > Thanks,
> >
> > Jaliya
> >
> >
> >
> >
> >
> > > Hi,
> > >
> > > Thanks to all on the Sandesha team for their
> > efforts.
> > > I a question on Sandesha. However, I am not sure
> > which
> > > mailing list I should post on.
> > >
> > > We have an application, which exposes web services
> > to
> > > our partners and in the same way our application
> > > consumes our partners' web services. My question
> > here
> > > is specifically when we are client to our
> > partners'
> > > web services.
> > >
> > > Our environment:
> > > OS: Win2k
> > > App Server: Weblogic 8.1 sp4
> > > SOAP Engine: Axis 1.2.1
> > > WSRM Engine: Sandesha 1.0
> > >
> > > Question:
> > > Axis throws a fault "No client transport named
> > > 'RMTransport' found!" when the web service call is
> > > made. I debugged the code and found that
> > > SandeshaContext initializes the Call with
> > RMTransport.
> > > However, in axis jar wsdd, the transport element
> > for
> > > RMTransport is not defined. Which class is the
> > handler
> > > for RMTransport? Could someone please update the
> > > documentation?
> > >
> > > Thanks,
> > > Abbas
> > >
> > > --- Jaliya Ekanayake < jaliya@apache.org
> <ma...@apache.org>> wrote:
> > >
> > >> Apache Sandesha team would like to announce the
> > 1.0
> > >> release for Apache
> > >> Sandesha
> > >> WS-ReliableMessaging implementation.
> > >>
> > >> You can download the releases from:
> > >>
> > >> Source:
> > >>
> > >
> >
> http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-src.zip
> > >> Binary:
> > >>
> > >
> >
> http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip
> <http://www.apache.org/dist/ws/sandesha/1_0/Sandesha-1.0-bin.zip>
> > >>
> > >> Source Repository :
> > >>
> > >
> >
> http://svn.apache.org/repos/asf/webservices/sandesha/trunk/
> <http://svn.apache.org/repos/asf/webservices/sandesha/trunk/>
> > >>
> > >> It has been three weeks since the release of the
> > RC1
> > >> version of Apache
> > >> Sandesha. The codebase is successfully moved to
> > the
> > >> SVN. We have fixed
> > >> all the issues that we have identified in the RC1
> > >> release and the
> > >> documents are also updated and the interop tests
> > are
> > >> tested again.
> > >> After all these we would like to announce the 1.0
> > >> release for Sandesha.
> > >>
> > >> Features:
> > >>
> > >> Following features are available in the release
> > of
> > >> Sandesha,
> > >> (1) Implementation of WS-ReliableMessaging
> > >> specification (February
> > >> 2005). On top of Axis 1.2
> > >> (2) INORDER delivery assurance.
> > >> (3) Support for synchronous and asynchronous
> > >> reliable exchange of
> > >> messages.
> > >> (4) A Client API that will make it easy for
> > users
> > >> to work
> > >> simultaneously with different endpoints and
> > >> different message
> > >> sequences.
> > >> (5) Updated documentation.
> > >> (6) Support for WS-Policy integration.
> > >> (7) Support Custom Web Service Invocation
> > >> Strategies.
> > >> (7) Interop Endpoint Client
> > >>
> > >
> >
> http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp
> <http://ws.zones.apache.org:7070/sandesha-interop/interop.jsp>
> > >> Server
> > >>
> > >
> >
> http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService
> <http://ws.zones.apache.org:7070/sandesha-interop/services/RMInteropService>
> > >>
> > >> If you have new ideas on messaging middleware and
> > >> would like to
> > >> contribute to
> > >> Apache Sandesha, please join us at
> > >> sandesha-dev@ws.apache.org <ma...@ws.apache.org>. Any
> > >> contribution in the
> > >> form of coding, testing, submitting improvements
> > to
> > >> the documentation, and
> > >> reporting bugs is always welcome.
> > >>
> > >> More information about Sandesha is available from
> > >> the Sandesha home:
> > >>
> > >> http://ws.apache.org/sandesha <http://ws.apache.org/sandesha>
> > >>
> > >> Sandesha Development Team.
> > >>
> > >>
> > >>
> > >
> >
> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail:
> > >> sandesha-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > >> For additional commands, e-mail:
> > >> sandesha-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> --
> "May the SourcE be with u"
> http://www.bloglines.com/blog/thilina
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org