You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by Steve Kruse <sk...@adaptivemethods.com> on 2007/03/08 14:24:41 UTC
New to MUSE and WSN
Hi,
I'm trying to understand Muse, and wsn-notification. Can someone please
answer a couple of questions me?
1) With Muse using wsn, can I have a web service that resides on a
server and a standalone client(java or c) that resides on some other
machine that will receive the notifications via a request to subscribe
to that web service? Does the client need to be setup with a web
service also? I'm a little confused. If this is possible, is there any
place I can go to get an example. I've been going through the Muse
tutorial, but I haven't figured out if it actually shows me how to do
this. Where is the callback on the standalone client side to receive
the notifications?
2) Is there a good spot that someone can point me that has some sort of
architecture diagram of how this could/would be setup?
Thank you very much in advance for any help.....
steve
--
RE: proxy and invoke
Posted by Daniel Jemiolo <da...@us.ibm.com>.
okay, I tried with your WSDL content, got the same error, and then fixed
the code to handle this case. you'll still have an Element generated, but
if you replace it with EndpointReference, the code will work as you expect
it to.
I just realized that we did not document this, but Andrew added a new
(optional) element to the muse.xml schema that allows you to associate
<custom-serializer/>s with XML types, not just Java types. this means that
if you specify a custom serializer in muse.xml and then include that
muse.xml file in your code gen command (wsdl2java -descriptor
/my/project/muse.xml), it will figure out the mapping of XML types -> Java
types -> serializers and make the Java code you want right off the bat.
Not sure if you think it's worth it, but it's there.
Let me know if tonight's build still doesn't work for you.
Thanks,
Dan
<le...@bt.com> wrote on 03/08/2007 10:58:18 AM:
> Sorry Dan, I copied the wrong part of the wsdl, it should have been:
>
> <xsd:schema elementFormDefault="qualified"
> targetNamespace="http://basic.org/test">
> <xsd:element name="CreateFromEprOperation">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
> ref="wsa:EndpointReference" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> <xsd:element
> name="CreateFromEprOperationResponse">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
> ref="wsa:EndpointReference" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
>
> Guess that's what one gets for naming functions with too similar names
> :)
>
> -----Original Message-----
> From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
> Sent: 08 March 2007 15:51
> To: muse-user@ws.apache.org
> Subject: Re: proxy and invoke
>
> hmmm... this looks similar to a bug I fixed last month[1]. I will try
> this
> on the RC build and get back to you.
>
> Dan
>
> [1] http://issues.apache.org/jira/browse/MUSE-202
>
>
> <le...@bt.com> wrote on 03/08/2007 09:24:42 AM:
>
> > Hi guys
> >
> > I'm trying to utilize the proxy to send an EndpointReference parameter
> > to the service and have edited my wsdl to have a wsa:endpointReference
> > parameter.
> > But for some reason the generated code always ends up with a Element
> > param, and even when looking to Daniel Jemiolo email from 15. December
> > 2006 about using:
> >
> > import org.apache.muse.ws.addressing.EndpointReference;
> >
> > ...
> >
> > public void myOperation(EndpointReference epr) {
> > Object[] params = new Object[1];
> > params[0] = epr;
> >
> > ProxyHandler handler = getHandler("myOperation");
> > invoke(handler, params);
> > }
> >
> > My Epr ends up all malformed.
> >
> > The declaration in the wsdl:
> >
> > <xsd:schema elementFormDefault="qualified"
> > targetNamespace="http://basic.org/test">
> > <xsd:element name="CreateWithEprOperation">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element
> > name="ResourceID" type="xsd:string" />
> > <xsd:element
> > name="ResourceType" type="xsd:string" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > <xsd:element
> > name="CreateWithEprOperationResponse">
> > <xsd:complexType>
> > <xsd:sequence>
> > <xsd:element
> > ref="wsa:EndpointReference" />
> > </xsd:sequence>
> > </xsd:complexType>
> > </xsd:element>
> > </xsd:schema>
> >
> > My Epr within the proxy function before the invoke function:
> >
> > <wsa:EndpointReference
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> >
> >
> <wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
> > s>
> > <wsa:ReferenceParameters>
> > <muse-wsa:ResourceId
> >
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
> > ResourceId>
> > </wsa:ReferenceParameters>
> > </wsa:EndpointReference>
> >
> >
> > Soap traces during runtime:
> > [CLIENT TRACE] SOAP envelope contents (outgoing):
> >
> > <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
> > <soap:Header>
> > <wsa:To
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://localhost:1234/W
> > S-Basic/services/WsBasic</wsa:To>
> > <wsa:Action
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://basic.org/test/C
> > reateFromEprOperation</wsa:Action>
> > <wsa:MessageID
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
> > -4cf3-ac268202ac26</wsa:MessageID>
> > <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
> >
> >
> <wsa:Address>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:Ad
> > dress>
> > </wsa:From>
> > </soap:Header>
> > <soap:Body>
> > <pfx0:CreateFromEprOperation
> xmlns:pfx0="http://basic.org/test">
> > <pfx1:EndpointReference
> > xmlns:pfx1="http://www.w3.org/2005/08/addressing">
> > <wsa:ReferenceParameters
> > xmlns:wsa="http://www.w3.org/2005/08/addressing">
> > <muse-wsa:ResourceId
> >
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
> > ResourceId>
> > </wsa:ReferenceParameters>
> > </pfx1:EndpointReference>
> > </pfx0:CreateFromEprOperation>
> > </soap:Body>
> > </soap:Envelope>
> >
> > [CLIENT TRACE] SOAP envelope contents (incoming):
> >
> > <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
> > <soap:Header>
> > <wsa:To
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
> > 08/addressing/role/anonymous</wsa:To>
> > <wsa:Action
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
> > 08/addressing/fault</wsa:Action>
> > <wsa:MessageID
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:c91d1b6a-bbf7-4e1b
> > -0501-5c3a2650ea23</wsa:MessageID>
> > <wsa:RelatesTo RelationshipType="wsa:Reply"
> >
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
> > -4cf3-ac268202ac26</wsa:RelatesTo>
> > <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
> >
> >
> <wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
> > s>
> > </wsa:From>
> > </soap:Header>
> > <soap:Body>
> > <soap:Fault>
> > <soap:Code>
> > <soap:Value>soap:Receiver</soap:Value>
> > </soap:Code>
> > <soap:Reason>
> > <soap:Text/>
> > </soap:Reason>
> > </soap:Fault>
> > </soap:Body>
> > </soap:Envelope>
> >
> > /Lenni
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: muse-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: proxy and invoke
Posted by le...@bt.com.
Sorry Dan, I copied the wrong part of the wsdl, it should have been:
<xsd:schema elementFormDefault="qualified"
targetNamespace="http://basic.org/test">
<xsd:element name="CreateFromEprOperation">
<xsd:complexType>
<xsd:sequence>
<xsd:element
ref="wsa:EndpointReference" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element
name="CreateFromEprOperationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element
ref="wsa:EndpointReference" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
Guess that's what one gets for naming functions with too similar names
:)
-----Original Message-----
From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
Sent: 08 March 2007 15:51
To: muse-user@ws.apache.org
Subject: Re: proxy and invoke
hmmm... this looks similar to a bug I fixed last month[1]. I will try
this
on the RC build and get back to you.
Dan
[1] http://issues.apache.org/jira/browse/MUSE-202
<le...@bt.com> wrote on 03/08/2007 09:24:42 AM:
> Hi guys
>
> I'm trying to utilize the proxy to send an EndpointReference parameter
> to the service and have edited my wsdl to have a wsa:endpointReference
> parameter.
> But for some reason the generated code always ends up with a Element
> param, and even when looking to Daniel Jemiolo email from 15. December
> 2006 about using:
>
> import org.apache.muse.ws.addressing.EndpointReference;
>
> ...
>
> public void myOperation(EndpointReference epr) {
> Object[] params = new Object[1];
> params[0] = epr;
>
> ProxyHandler handler = getHandler("myOperation");
> invoke(handler, params);
> }
>
> My Epr ends up all malformed.
>
> The declaration in the wsdl:
>
> <xsd:schema elementFormDefault="qualified"
> targetNamespace="http://basic.org/test">
> <xsd:element name="CreateWithEprOperation">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
> name="ResourceID" type="xsd:string" />
> <xsd:element
> name="ResourceType" type="xsd:string" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> <xsd:element
> name="CreateWithEprOperationResponse">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
> ref="wsa:EndpointReference" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
>
> My Epr within the proxy function before the invoke function:
>
> <wsa:EndpointReference
xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
>
<wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
> s>
> <wsa:ReferenceParameters>
> <muse-wsa:ResourceId
>
xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
> ResourceId>
> </wsa:ReferenceParameters>
> </wsa:EndpointReference>
>
>
> Soap traces during runtime:
> [CLIENT TRACE] SOAP envelope contents (outgoing):
>
> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
> <soap:Header>
> <wsa:To
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://localhost:1234/W
> S-Basic/services/WsBasic</wsa:To>
> <wsa:Action
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://basic.org/test/C
> reateFromEprOperation</wsa:Action>
> <wsa:MessageID
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
> -4cf3-ac268202ac26</wsa:MessageID>
> <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
>
<wsa:Address>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:Ad
> dress>
> </wsa:From>
> </soap:Header>
> <soap:Body>
> <pfx0:CreateFromEprOperation
xmlns:pfx0="http://basic.org/test">
> <pfx1:EndpointReference
> xmlns:pfx1="http://www.w3.org/2005/08/addressing">
> <wsa:ReferenceParameters
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <muse-wsa:ResourceId
>
xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
> ResourceId>
> </wsa:ReferenceParameters>
> </pfx1:EndpointReference>
> </pfx0:CreateFromEprOperation>
> </soap:Body>
> </soap:Envelope>
>
> [CLIENT TRACE] SOAP envelope contents (incoming):
>
> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
> <soap:Header>
> <wsa:To
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
> 08/addressing/role/anonymous</wsa:To>
> <wsa:Action
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
> 08/addressing/fault</wsa:Action>
> <wsa:MessageID
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:c91d1b6a-bbf7-4e1b
> -0501-5c3a2650ea23</wsa:MessageID>
> <wsa:RelatesTo RelationshipType="wsa:Reply"
>
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
> -4cf3-ac268202ac26</wsa:RelatesTo>
> <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
>
<wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
> s>
> </wsa:From>
> </soap:Header>
> <soap:Body>
> <soap:Fault>
> <soap:Code>
> <soap:Value>soap:Receiver</soap:Value>
> </soap:Code>
> <soap:Reason>
> <soap:Text/>
> </soap:Reason>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
>
> /Lenni
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: proxy and invoke
Posted by Daniel Jemiolo <da...@us.ibm.com>.
hmmm... this looks similar to a bug I fixed last month[1]. I will try this
on the RC build and get back to you.
Dan
[1] http://issues.apache.org/jira/browse/MUSE-202
<le...@bt.com> wrote on 03/08/2007 09:24:42 AM:
> Hi guys
>
> I'm trying to utilize the proxy to send an EndpointReference parameter
> to the service and have edited my wsdl to have a wsa:endpointReference
> parameter.
> But for some reason the generated code always ends up with a Element
> param, and even when looking to Daniel Jemiolo email from 15. December
> 2006 about using:
>
> import org.apache.muse.ws.addressing.EndpointReference;
>
> ...
>
> public void myOperation(EndpointReference epr) {
> Object[] params = new Object[1];
> params[0] = epr;
>
> ProxyHandler handler = getHandler("myOperation");
> invoke(handler, params);
> }
>
> My Epr ends up all malformed.
>
> The declaration in the wsdl:
>
> <xsd:schema elementFormDefault="qualified"
> targetNamespace="http://basic.org/test">
> <xsd:element name="CreateWithEprOperation">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
> name="ResourceID" type="xsd:string" />
> <xsd:element
> name="ResourceType" type="xsd:string" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> <xsd:element
> name="CreateWithEprOperationResponse">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element
> ref="wsa:EndpointReference" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
>
> My Epr within the proxy function before the invoke function:
>
> <wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
> <wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
> s>
> <wsa:ReferenceParameters>
> <muse-wsa:ResourceId
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
> ResourceId>
> </wsa:ReferenceParameters>
> </wsa:EndpointReference>
>
>
> Soap traces during runtime:
> [CLIENT TRACE] SOAP envelope contents (outgoing):
>
> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
> <soap:Header>
> <wsa:To
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://localhost:1234/W
> S-Basic/services/WsBasic</wsa:To>
> <wsa:Action
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://basic.org/test/C
> reateFromEprOperation</wsa:Action>
> <wsa:MessageID
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
> -4cf3-ac268202ac26</wsa:MessageID>
> <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
> <wsa:Address>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:Ad
> dress>
> </wsa:From>
> </soap:Header>
> <soap:Body>
> <pfx0:CreateFromEprOperation xmlns:pfx0="http://basic.org/test">
> <pfx1:EndpointReference
> xmlns:pfx1="http://www.w3.org/2005/08/addressing">
> <wsa:ReferenceParameters
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <muse-wsa:ResourceId
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
> ResourceId>
> </wsa:ReferenceParameters>
> </pfx1:EndpointReference>
> </pfx0:CreateFromEprOperation>
> </soap:Body>
> </soap:Envelope>
>
> [CLIENT TRACE] SOAP envelope contents (incoming):
>
> <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
> <soap:Header>
> <wsa:To
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
> 08/addressing/role/anonymous</wsa:To>
> <wsa:Action
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
> 08/addressing/fault</wsa:Action>
> <wsa:MessageID
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:c91d1b6a-bbf7-4e1b
> -0501-5c3a2650ea23</wsa:MessageID>
> <wsa:RelatesTo RelationshipType="wsa:Reply"
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
> -4cf3-ac268202ac26</wsa:RelatesTo>
> <wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
> <wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
> s>
> </wsa:From>
> </soap:Header>
> <soap:Body>
> <soap:Fault>
> <soap:Code>
> <soap:Value>soap:Receiver</soap:Value>
> </soap:Code>
> <soap:Reason>
> <soap:Text/>
> </soap:Reason>
> </soap:Fault>
> </soap:Body>
> </soap:Envelope>
>
> /Lenni
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
proxy and invoke
Posted by le...@bt.com.
Hi guys
I'm trying to utilize the proxy to send an EndpointReference parameter
to the service and have edited my wsdl to have a wsa:endpointReference
parameter.
But for some reason the generated code always ends up with a Element
param, and even when looking to Daniel Jemiolo email from 15. December
2006 about using:
import org.apache.muse.ws.addressing.EndpointReference;
...
public void myOperation(EndpointReference epr) {
Object[] params = new Object[1];
params[0] = epr;
ProxyHandler handler = getHandler("myOperation");
invoke(handler, params);
}
My Epr ends up all malformed.
The declaration in the wsdl:
<xsd:schema elementFormDefault="qualified"
targetNamespace="http://basic.org/test">
<xsd:element name="CreateWithEprOperation">
<xsd:complexType>
<xsd:sequence>
<xsd:element
name="ResourceID" type="xsd:string" />
<xsd:element
name="ResourceType" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element
name="CreateWithEprOperationResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element
ref="wsa:EndpointReference" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
My Epr within the proxy function before the invoke function:
<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
s>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
ResourceId>
</wsa:ReferenceParameters>
</wsa:EndpointReference>
Soap traces during runtime:
[CLIENT TRACE] SOAP envelope contents (outgoing):
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<wsa:To
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://localhost:1234/W
S-Basic/services/WsBasic</wsa:To>
<wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://basic.org/test/C
reateFromEprOperation</wsa:Action>
<wsa:MessageID
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
-4cf3-ac268202ac26</wsa:MessageID>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://www.w3.org/2005/08/addressing/role/anonymous</wsa:Ad
dress>
</wsa:From>
</soap:Header>
<soap:Body>
<pfx0:CreateFromEprOperation xmlns:pfx0="http://basic.org/test">
<pfx1:EndpointReference
xmlns:pfx1="http://www.w3.org/2005/08/addressing">
<wsa:ReferenceParameters
xmlns:wsa="http://www.w3.org/2005/08/addressing">
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing">test0r1</muse-wsa:
ResourceId>
</wsa:ReferenceParameters>
</pfx1:EndpointReference>
</pfx0:CreateFromEprOperation>
</soap:Body>
</soap:Envelope>
[CLIENT TRACE] SOAP envelope contents (incoming):
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
<soap:Header>
<wsa:To
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
08/addressing/role/anonymous</wsa:To>
<wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://www.w3.org/2005/
08/addressing/fault</wsa:Action>
<wsa:MessageID
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:c91d1b6a-bbf7-4e1b
-0501-5c3a2650ea23</wsa:MessageID>
<wsa:RelatesTo RelationshipType="wsa:Reply"
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:b44093a2-fb8a-3abd
-4cf3-ac268202ac26</wsa:RelatesTo>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://localhost:1234/WS-Basic/services/WsBasic</wsa:Addres
s>
</wsa:From>
</soap:Header>
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Receiver</soap:Value>
</soap:Code>
<soap:Reason>
<soap:Text/>
</soap:Reason>
</soap:Fault>
</soap:Body>
</soap:Envelope>
/Lenni
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
Re: OSGi-based WSN consumer with a standalone GUI
Posted by Balan Subramanian <bs...@us.ibm.com>.
Steve,
Please take a look at the managed agent explorer in Eclipse TPTP
(http://www.eclipse.org/tptp/home/downloads/?ver=4.4.0) particularly the
Build to Manage tooling
(http://www.eclipse.org/tptp/monitoring/documents/tutorials/tptp_wsdm_setup_4.3.html).
Here is an article that show what the MAX looks like etc.:
http://www.eclipse.org/tptp/monitoring/documents/tutorials/using_managed_agent_explorer_4_2_2.htm.
We have recently added WS-N notification support by providing an OSGi
based endpoint within the Eclipse workbench which can be used by any other
plugin for making subscriptions and getting the notifications. THis can
also be used by RCP applications as the endpoint plugin itself does not
have a lot of depedencies on anything other than core Eclipse/Equinox
plugins.
If you interested please followup on the TPTP newsgroup for questions on
using the MAX or building a GUI that uses the WS-N consumer embedded in
the workbench. The TPTP newsgroup is at
http://www.eclipse.org/newsportal/thread.php?group=eclipse.tptp
Thanks,
Balan
Balan Subramanian
Autonomic Computing, IBM, RTP, NC
919.543.0197 | bsubram@us.ibm.com
"Steve Kruse" <sk...@adaptivemethods.com>
03/09/2007 08:40 AM
Please respond to
muse-user@ws.apache.org
To
<mu...@ws.apache.org>
cc
Subject
OSGi-based WSN consumer with a standalone GUI
Thanks a lot Dan. Is there anyone out there that could share some
knowledge/examples of how to integrate an OSGi-based WSN consumer with a
standalone GUI? Any info would be appreciated.
Thanks,
Steve
-----Original Message-----
From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
Sent: Thursday, March 08, 2007 5:33 PM
To: muse-user@ws.apache.org
Subject: RE: New to MUSE and WSN
The delay between the time the producer publishes the message and when
the
consumer gets is depends on network latency and how many other messages
(unrelated to WSN) the consumer is handling. In just a simple scenario
between producer/consumer, there's no delay on the producer side (like a
message queue or batch processing or something).
The example consumer shows you how to set up message listeners on the
consumer side - you can add as many message listeners as you want, and
each can target different types of notifications (this filtering is part
of the listener API). The sample listener just prints out the
notification
content, but you could, for example, use Muse's WEF API to parse the
notifications into WEF events and process them that way.
The closest thing to a 'standalone client' that also does WS-* is the
OSGi/Mini option - yes, you have to add the OSGi framework, but that is
tiny (the Apache XML libraries are bigger than OSGi). If you want a true
standalone client, you'll have to set up your own HTTP listener/server
and
SOAP engine and then figure out how to "deploy" Muse into it. That's a
lot
of work. If you're looking for help in integrating an OSGi-based WSN
consumer with a GUI, there are developers on this list that have
experience with that and can help you out.
Dan
"Steve Kruse" <sk...@adaptivemethods.com> wrote on 03/08/2007 05:10:39
PM:
> Dan,
>
> Thanks to you and Lenni for the info so far. I think it sounds like I
> would want to use the OSGi/Mini SOAP engine. Is it realistic to think
> that I can setup a web service using wsn and get pretty timely results
> at the consumer end if I am sending out a pretty consistent flow of
> messages from the produccer. Does the example consumer actually give
an
> example of getting a notifications message from the producer? I need
to
> implement a listener on the client, I would think, how would I
implement
> this? Do you know of any examples I could find to implement the Mini
> SOAP engine inside of my J2SE standalone client. Any help and
examples
> would be greatly appreciated...
>
> Thanks,
> steve
>
>
> -----Original Message-----
> From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
> Sent: Thursday, March 08, 2007 11:43 AM
> To: muse-user@ws.apache.org
> Subject: RE: New to MUSE and WSN
>
> To add to what Lenni said: yes, you need a web service to receive
> notifications that are sent over HTTP/SOAP; however, there's no reason
> that consumer service has to be large. If you use the OSGi/Mini SOAP
> engine option when building services with wsdl2java, you will get an
> application that can run on J2ME/J2SE and is quite small. If you're a
> J2EE-only guy, you can use embedded Tomcat (5-6 MB last time I
checked)
> and use the J2EE/Mini option to create a WAR that will only add
another
> 1.5 MB. The OSGi option might be better if you plan to incorporate the
> consumer into some kind of rich client - OSGi will allow you to load
> your
> Muse-based applications and your other client code in the same JVM. We
> have done this in the past to create resource/message browsers in
> Eclipse.
>
> Dan
>
>
>
> <le...@bt.com> wrote on 03/08/2007 09:18:29 AM:
>
> > Hi Steve
> >
> > I'll do my best to make it a bit more clear as it seems to be a
common
> > question about WSN.
> >
> > 1) Both your Client and service needs to be run as web services. A
> > simplified example can be found in the downloadable binary
> distribution
> > of Muse from http://ws.apache.org/muse/download.html, the examples
are
> > as follows: client <-> Wsn-comsumer, service <-> Wsn-producer
> > These should work out of the box.
> >
> > /Lenni
> >
> > -----Original Message-----
> > From: Steve Kruse [mailto:skruse@adaptivemethods.com]
> > Sent: 08 March 2007 13:25
> > To: muse-user@ws.apache.org
> > Subject: New to MUSE and WSN
> >
> > Hi,
> >
> > I'm trying to understand Muse, and wsn-notification. Can someone
> please
> > answer a couple of questions me?
> >
> > 1) With Muse using wsn, can I have a web service that resides on a
> > server and a standalone client(java or c) that resides on some
other
> > machine that will receive the notifications via a request to
subscribe
> > to that web service? Does the client need to be setup with a web
> > service also? I'm a little confused. If this is possible, is there
> any
> > place I can go to get an example. I've been going through the Muse
> > tutorial, but I haven't figured out if it actually shows me how to
do
> > this. Where is the callback on the standalone client side to
receive
> > the notifications?
> >
> > 2) Is there a good spot that someone can point me that has some sort
> of
> > architecture diagram of how this could/would be setup?
> >
> > Thank you very much in advance for any help.....
> >
> > steve
> >
> > --
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: muse-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
OSGi-based WSN consumer with a standalone GUI
Posted by Steve Kruse <sk...@adaptivemethods.com>.
Thanks a lot Dan. Is there anyone out there that could share some
knowledge/examples of how to integrate an OSGi-based WSN consumer with a
standalone GUI? Any info would be appreciated.
Thanks,
Steve
-----Original Message-----
From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
Sent: Thursday, March 08, 2007 5:33 PM
To: muse-user@ws.apache.org
Subject: RE: New to MUSE and WSN
The delay between the time the producer publishes the message and when
the
consumer gets is depends on network latency and how many other messages
(unrelated to WSN) the consumer is handling. In just a simple scenario
between producer/consumer, there's no delay on the producer side (like a
message queue or batch processing or something).
The example consumer shows you how to set up message listeners on the
consumer side - you can add as many message listeners as you want, and
each can target different types of notifications (this filtering is part
of the listener API). The sample listener just prints out the
notification
content, but you could, for example, use Muse's WEF API to parse the
notifications into WEF events and process them that way.
The closest thing to a 'standalone client' that also does WS-* is the
OSGi/Mini option - yes, you have to add the OSGi framework, but that is
tiny (the Apache XML libraries are bigger than OSGi). If you want a true
standalone client, you'll have to set up your own HTTP listener/server
and
SOAP engine and then figure out how to "deploy" Muse into it. That's a
lot
of work. If you're looking for help in integrating an OSGi-based WSN
consumer with a GUI, there are developers on this list that have
experience with that and can help you out.
Dan
"Steve Kruse" <sk...@adaptivemethods.com> wrote on 03/08/2007 05:10:39
PM:
> Dan,
>
> Thanks to you and Lenni for the info so far. I think it sounds like I
> would want to use the OSGi/Mini SOAP engine. Is it realistic to think
> that I can setup a web service using wsn and get pretty timely results
> at the consumer end if I am sending out a pretty consistent flow of
> messages from the produccer. Does the example consumer actually give
an
> example of getting a notifications message from the producer? I need
to
> implement a listener on the client, I would think, how would I
implement
> this? Do you know of any examples I could find to implement the Mini
> SOAP engine inside of my J2SE standalone client. Any help and
examples
> would be greatly appreciated...
>
> Thanks,
> steve
>
>
> -----Original Message-----
> From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
> Sent: Thursday, March 08, 2007 11:43 AM
> To: muse-user@ws.apache.org
> Subject: RE: New to MUSE and WSN
>
> To add to what Lenni said: yes, you need a web service to receive
> notifications that are sent over HTTP/SOAP; however, there's no reason
> that consumer service has to be large. If you use the OSGi/Mini SOAP
> engine option when building services with wsdl2java, you will get an
> application that can run on J2ME/J2SE and is quite small. If you're a
> J2EE-only guy, you can use embedded Tomcat (5-6 MB last time I
checked)
> and use the J2EE/Mini option to create a WAR that will only add
another
> 1.5 MB. The OSGi option might be better if you plan to incorporate the
> consumer into some kind of rich client - OSGi will allow you to load
> your
> Muse-based applications and your other client code in the same JVM. We
> have done this in the past to create resource/message browsers in
> Eclipse.
>
> Dan
>
>
>
> <le...@bt.com> wrote on 03/08/2007 09:18:29 AM:
>
> > Hi Steve
> >
> > I'll do my best to make it a bit more clear as it seems to be a
common
> > question about WSN.
> >
> > 1) Both your Client and service needs to be run as web services. A
> > simplified example can be found in the downloadable binary
> distribution
> > of Muse from http://ws.apache.org/muse/download.html, the examples
are
> > as follows: client <-> Wsn-comsumer, service <-> Wsn-producer
> > These should work out of the box.
> >
> > /Lenni
> >
> > -----Original Message-----
> > From: Steve Kruse [mailto:skruse@adaptivemethods.com]
> > Sent: 08 March 2007 13:25
> > To: muse-user@ws.apache.org
> > Subject: New to MUSE and WSN
> >
> > Hi,
> >
> > I'm trying to understand Muse, and wsn-notification. Can someone
> please
> > answer a couple of questions me?
> >
> > 1) With Muse using wsn, can I have a web service that resides on a
> > server and a standalone client(java or c) that resides on some
other
> > machine that will receive the notifications via a request to
subscribe
> > to that web service? Does the client need to be setup with a web
> > service also? I'm a little confused. If this is possible, is there
> any
> > place I can go to get an example. I've been going through the Muse
> > tutorial, but I haven't figured out if it actually shows me how to
do
> > this. Where is the callback on the standalone client side to
receive
> > the notifications?
> >
> > 2) Is there a good spot that someone can point me that has some sort
> of
> > architecture diagram of how this could/would be setup?
> >
> > Thank you very much in advance for any help.....
> >
> > steve
> >
> > --
> >
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: muse-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: New to MUSE and WSN
Posted by Daniel Jemiolo <da...@us.ibm.com>.
The delay between the time the producer publishes the message and when the
consumer gets is depends on network latency and how many other messages
(unrelated to WSN) the consumer is handling. In just a simple scenario
between producer/consumer, there's no delay on the producer side (like a
message queue or batch processing or something).
The example consumer shows you how to set up message listeners on the
consumer side - you can add as many message listeners as you want, and
each can target different types of notifications (this filtering is part
of the listener API). The sample listener just prints out the notification
content, but you could, for example, use Muse's WEF API to parse the
notifications into WEF events and process them that way.
The closest thing to a 'standalone client' that also does WS-* is the
OSGi/Mini option - yes, you have to add the OSGi framework, but that is
tiny (the Apache XML libraries are bigger than OSGi). If you want a true
standalone client, you'll have to set up your own HTTP listener/server and
SOAP engine and then figure out how to "deploy" Muse into it. That's a lot
of work. If you're looking for help in integrating an OSGi-based WSN
consumer with a GUI, there are developers on this list that have
experience with that and can help you out.
Dan
"Steve Kruse" <sk...@adaptivemethods.com> wrote on 03/08/2007 05:10:39
PM:
> Dan,
>
> Thanks to you and Lenni for the info so far. I think it sounds like I
> would want to use the OSGi/Mini SOAP engine. Is it realistic to think
> that I can setup a web service using wsn and get pretty timely results
> at the consumer end if I am sending out a pretty consistent flow of
> messages from the produccer. Does the example consumer actually give an
> example of getting a notifications message from the producer? I need to
> implement a listener on the client, I would think, how would I implement
> this? Do you know of any examples I could find to implement the Mini
> SOAP engine inside of my J2SE standalone client. Any help and examples
> would be greatly appreciated...
>
> Thanks,
> steve
>
>
> -----Original Message-----
> From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
> Sent: Thursday, March 08, 2007 11:43 AM
> To: muse-user@ws.apache.org
> Subject: RE: New to MUSE and WSN
>
> To add to what Lenni said: yes, you need a web service to receive
> notifications that are sent over HTTP/SOAP; however, there's no reason
> that consumer service has to be large. If you use the OSGi/Mini SOAP
> engine option when building services with wsdl2java, you will get an
> application that can run on J2ME/J2SE and is quite small. If you're a
> J2EE-only guy, you can use embedded Tomcat (5-6 MB last time I checked)
> and use the J2EE/Mini option to create a WAR that will only add another
> 1.5 MB. The OSGi option might be better if you plan to incorporate the
> consumer into some kind of rich client - OSGi will allow you to load
> your
> Muse-based applications and your other client code in the same JVM. We
> have done this in the past to create resource/message browsers in
> Eclipse.
>
> Dan
>
>
>
> <le...@bt.com> wrote on 03/08/2007 09:18:29 AM:
>
> > Hi Steve
> >
> > I'll do my best to make it a bit more clear as it seems to be a common
> > question about WSN.
> >
> > 1) Both your Client and service needs to be run as web services. A
> > simplified example can be found in the downloadable binary
> distribution
> > of Muse from http://ws.apache.org/muse/download.html, the examples are
> > as follows: client <-> Wsn-comsumer, service <-> Wsn-producer
> > These should work out of the box.
> >
> > /Lenni
> >
> > -----Original Message-----
> > From: Steve Kruse [mailto:skruse@adaptivemethods.com]
> > Sent: 08 March 2007 13:25
> > To: muse-user@ws.apache.org
> > Subject: New to MUSE and WSN
> >
> > Hi,
> >
> > I'm trying to understand Muse, and wsn-notification. Can someone
> please
> > answer a couple of questions me?
> >
> > 1) With Muse using wsn, can I have a web service that resides on a
> > server and a standalone client(java or c) that resides on some other
> > machine that will receive the notifications via a request to subscribe
> > to that web service? Does the client need to be setup with a web
> > service also? I'm a little confused. If this is possible, is there
> any
> > place I can go to get an example. I've been going through the Muse
> > tutorial, but I haven't figured out if it actually shows me how to do
> > this. Where is the callback on the standalone client side to receive
> > the notifications?
> >
> > 2) Is there a good spot that someone can point me that has some sort
> of
> > architecture diagram of how this could/would be setup?
> >
> > Thank you very much in advance for any help.....
> >
> > steve
> >
> > --
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: muse-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: New to MUSE and WSN
Posted by Steve Kruse <sk...@adaptivemethods.com>.
Dan,
Thanks to you and Lenni for the info so far. I think it sounds like I
would want to use the OSGi/Mini SOAP engine. Is it realistic to think
that I can setup a web service using wsn and get pretty timely results
at the consumer end if I am sending out a pretty consistent flow of
messages from the produccer. Does the example consumer actually give an
example of getting a notifications message from the producer? I need to
implement a listener on the client, I would think, how would I implement
this? Do you know of any examples I could find to implement the Mini
SOAP engine inside of my J2SE standalone client. Any help and examples
would be greatly appreciated...
Thanks,
steve
-----Original Message-----
From: Daniel Jemiolo [mailto:danjemiolo@us.ibm.com]
Sent: Thursday, March 08, 2007 11:43 AM
To: muse-user@ws.apache.org
Subject: RE: New to MUSE and WSN
To add to what Lenni said: yes, you need a web service to receive
notifications that are sent over HTTP/SOAP; however, there's no reason
that consumer service has to be large. If you use the OSGi/Mini SOAP
engine option when building services with wsdl2java, you will get an
application that can run on J2ME/J2SE and is quite small. If you're a
J2EE-only guy, you can use embedded Tomcat (5-6 MB last time I checked)
and use the J2EE/Mini option to create a WAR that will only add another
1.5 MB. The OSGi option might be better if you plan to incorporate the
consumer into some kind of rich client - OSGi will allow you to load
your
Muse-based applications and your other client code in the same JVM. We
have done this in the past to create resource/message browsers in
Eclipse.
Dan
<le...@bt.com> wrote on 03/08/2007 09:18:29 AM:
> Hi Steve
>
> I'll do my best to make it a bit more clear as it seems to be a common
> question about WSN.
>
> 1) Both your Client and service needs to be run as web services. A
> simplified example can be found in the downloadable binary
distribution
> of Muse from http://ws.apache.org/muse/download.html, the examples are
> as follows: client <-> Wsn-comsumer, service <-> Wsn-producer
> These should work out of the box.
>
> /Lenni
>
> -----Original Message-----
> From: Steve Kruse [mailto:skruse@adaptivemethods.com]
> Sent: 08 March 2007 13:25
> To: muse-user@ws.apache.org
> Subject: New to MUSE and WSN
>
> Hi,
>
> I'm trying to understand Muse, and wsn-notification. Can someone
please
> answer a couple of questions me?
>
> 1) With Muse using wsn, can I have a web service that resides on a
> server and a standalone client(java or c) that resides on some other
> machine that will receive the notifications via a request to subscribe
> to that web service? Does the client need to be setup with a web
> service also? I'm a little confused. If this is possible, is there
any
> place I can go to get an example. I've been going through the Muse
> tutorial, but I haven't figured out if it actually shows me how to do
> this. Where is the callback on the standalone client side to receive
> the notifications?
>
> 2) Is there a good spot that someone can point me that has some sort
of
> architecture diagram of how this could/would be setup?
>
> Thank you very much in advance for any help.....
>
> steve
>
> --
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: New to MUSE and WSN
Posted by Daniel Jemiolo <da...@us.ibm.com>.
To add to what Lenni said: yes, you need a web service to receive
notifications that are sent over HTTP/SOAP; however, there's no reason
that consumer service has to be large. If you use the OSGi/Mini SOAP
engine option when building services with wsdl2java, you will get an
application that can run on J2ME/J2SE and is quite small. If you're a
J2EE-only guy, you can use embedded Tomcat (5-6 MB last time I checked)
and use the J2EE/Mini option to create a WAR that will only add another
1.5 MB. The OSGi option might be better if you plan to incorporate the
consumer into some kind of rich client - OSGi will allow you to load your
Muse-based applications and your other client code in the same JVM. We
have done this in the past to create resource/message browsers in Eclipse.
Dan
<le...@bt.com> wrote on 03/08/2007 09:18:29 AM:
> Hi Steve
>
> I'll do my best to make it a bit more clear as it seems to be a common
> question about WSN.
>
> 1) Both your Client and service needs to be run as web services. A
> simplified example can be found in the downloadable binary distribution
> of Muse from http://ws.apache.org/muse/download.html, the examples are
> as follows: client <-> Wsn-comsumer, service <-> Wsn-producer
> These should work out of the box.
>
> /Lenni
>
> -----Original Message-----
> From: Steve Kruse [mailto:skruse@adaptivemethods.com]
> Sent: 08 March 2007 13:25
> To: muse-user@ws.apache.org
> Subject: New to MUSE and WSN
>
> Hi,
>
> I'm trying to understand Muse, and wsn-notification. Can someone please
> answer a couple of questions me?
>
> 1) With Muse using wsn, can I have a web service that resides on a
> server and a standalone client(java or c) that resides on some other
> machine that will receive the notifications via a request to subscribe
> to that web service? Does the client need to be setup with a web
> service also? I'm a little confused. If this is possible, is there any
> place I can go to get an example. I've been going through the Muse
> tutorial, but I haven't figured out if it actually shows me how to do
> this. Where is the callback on the standalone client side to receive
> the notifications?
>
> 2) Is there a good spot that someone can point me that has some sort of
> architecture diagram of how this could/would be setup?
>
> Thank you very much in advance for any help.....
>
> steve
>
> --
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: muse-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org
RE: New to MUSE and WSN
Posted by le...@bt.com.
Hi Steve
I'll do my best to make it a bit more clear as it seems to be a common
question about WSN.
1) Both your Client and service needs to be run as web services. A
simplified example can be found in the downloadable binary distribution
of Muse from http://ws.apache.org/muse/download.html, the examples are
as follows: client <-> Wsn-comsumer, service <-> Wsn-producer
These should work out of the box.
/Lenni
-----Original Message-----
From: Steve Kruse [mailto:skruse@adaptivemethods.com]
Sent: 08 March 2007 13:25
To: muse-user@ws.apache.org
Subject: New to MUSE and WSN
Hi,
I'm trying to understand Muse, and wsn-notification. Can someone please
answer a couple of questions me?
1) With Muse using wsn, can I have a web service that resides on a
server and a standalone client(java or c) that resides on some other
machine that will receive the notifications via a request to subscribe
to that web service? Does the client need to be setup with a web
service also? I'm a little confused. If this is possible, is there any
place I can go to get an example. I've been going through the Muse
tutorial, but I haven't figured out if it actually shows me how to do
this. Where is the callback on the standalone client side to receive
the notifications?
2) Is there a good spot that someone can point me that has some sort of
architecture diagram of how this could/would be setup?
Thank you very much in advance for any help.....
steve
--
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-user-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-user-help@ws.apache.org