Nabble - Apache Muse

Saurabh Dravid is out of the office.

2009-10-22T07:40:45Z

I will be out of the office starting 10/15/2009 and will not return until
10/27/2009.

Thanks for your email. I will be back to work only on 27-Oct-2009 and will
respond once I return. For any urgent issues contact my manager "Ramsy V
Pinto " (rvpinto@...).

From forum: Muse User

Problem with OSGI examples in muse 2.2

2009-10-22T07:36:23Z

Dear all,

I have the same problem posted in this thread

http://marc.info/?l=muse-user&m=119309002714648&w=2
<http://marc.info/?l=muse-user&m=119309002714648&w=2>

and as I can't find a reply for such problem, I just asking your help...

Thank you in advance...

Sincerely,
M.El-Gayyar

From forum: Muse User

Re: Extra headers not working

2009-10-05T03:57:28Z

ahh.. in that case, you forgot to cleanup, let me try to explain.

This is how I think your program is working in rough steps:

1) call clientprpxy
2) clientproxy initializes a server-instance
3) you make some calls to the server-instance

4) you call the clientproxy again (same epr)
5) the cleintproxy tries to instantiate a new server-instance at the
same EPR (alreay in use -> instantiation fails), with muse-resource
param
<muse-wsa:ResourceId xmlns:muse-wsa="http://ws.apache.org/muse/addressing
">MuseResource-2</muse-wsa:ResourceId>

possible test solution(s):
A) try a new EPR (hint: make sure you don't reuse the same
MuseResource-2)
B) restart the server-side apache (if using two different apache
servers)

permanent solution if A) works make sure you call <instance>.shutdown
(); to remove the initialized instance at the EPR

/Lenni
On Oct 5, 2009, at 12:24 GMT+02:00, <juanluis.prietomartinez@...>
wrote:

> The think is that it works the first time that I run it after I
> deploy it, but afterwards that is the error, as far as I know the
> epr shouldn't change at all.
>
> -----Original Message-----
> From: Chris Twiner [mailto:chris.twiner@...]
> Sent: 05 October 2009 11:09
> To: muse-user@...
> Subject: Re: Extra headers not working
>
> Unless I'm missing something you aren't using the right epr. As the
> error message is telling you :
>
> <wsa:ReferenceParameters
>> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>> <muse-wsa:ResourceId
>> xmlns:muse-wsa="http://ws.apache.org/muse/
>> addressing">MuseResource-2</
>> mu
>> se-wsa:ResourceId>
>> </wsa:ReferenceParameters>
>
> seems to be missing.
>
> epr.addParameter(WsaConstants.DEFAULT_RESOURCE_ID_QNAME,
> "MuseResource-" + x);
>
> should help.
>
> On Mon, Oct 5, 2009 at 11:27 AM, <juanluis.prietomartinez@...>
> wrote:
>> Hi all,
>>
>> I have built a client for my muse app with wsd2java and I have added
>> the flag -headers to be able to add headers to the call that I need
>> to
>> extract with another component.
>>
>> The proxy has been generated w/out any problem and it has the new
>> parameter Element[] in all the methods. To test it I am putting null
>> just to make a normal call to the webapp and I am having this issue.
>>
>> This is the call I am doing:
>>
>> public void testCreate() throws SoapFault {
>> proxy = new WsSongStoreProxy(new
>> EndpointReference(URI.create(providerUrl)), null);
>> proxy = new WsSongStoreProxy (elemToEpr
>> (proxy.createOperation(null)), null);
>> proxy.setTrace(true);
>> }
>>
>> And this is the trace with the error I am getting.
>>
>> org.apache.muse.ws.addressing.soap.SoapFault: [ID =
>> 'DestinationUnreachable'] There is no resource available at the given
>> EPR:
>>
>> <wsa:EndpointReference
>> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>>
>> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/
>> WsSongStore</w
>> sa
>> :Address>
>> </wsa:EndpointReference>
>>
>> The existing EPRs hosted by this endpoint are:
>>
>> <wsa:EndpointReference
>> xmlns:wsa="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">MuseResource-2</
>> mu
>> se-wsa:ResourceId>
>> </wsa:ReferenceParameters>
>>
>> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/
>> WsSongStore</w
>> sa
>> :Address>
>> </wsa:EndpointReference>
>>
>> <wsa:EndpointReference
>> xmlns:wsa="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">MuseResource-3</
>> mu
>> se-wsa:ResourceId>
>> </wsa:ReferenceParameters>
>>
>> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/
>> WsSongStore</w
>> sa
>> :Address>
>> </wsa:EndpointReference>
>> at
>> org.apache.muse.core.AbstractResourceClient.invoke
>> (AbstractResourceCli
>> en
>> t.java:298)
>> at
>> org.apache.muse.core.AbstractResourceClient.invoke
>> (AbstractResourceCli
>> en
>> t.java:232)
>> at
>> test.proxy.WsSongStoreProxy.createOperation(WsSongStoreProxy.java:
>> 131)
>> at core.testHeaders.testCreate(testHeaders.java:26)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.j
>> av
>> a:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccess
>> or
>> Impl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at junit.framework.TestCase.runTest(TestCase.java:164)
>> at junit.framework.TestCase.runBare(TestCase.java:130)
>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>> at junit.framework.TestResult.runProtected(TestResult.java:
>> 124)
>> at junit.framework.TestResult.run(TestResult.java:109)
>> at junit.framework.TestCase.run(TestCase.java:120)
>> at junit.framework.TestSuite.runTest(TestSuite.java:230)
>> at junit.framework.TestSuite.run(TestSuite.java:225)
>> at
>> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run
>> (J
>> Un
>> it3TestReference.java:130)
>> at
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run
>> (TestExecution.
>> ja
>> va:38)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
>> (Remote
>> Te
>> stRunner.java:467)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests
>> (Remote
>> Te
>> stRunner.java:683)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run
>> (RemoteTestR
>> un
>> ner.java:390)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main
>> (RemoteTest
>> Ru
>> nner.java:197)
>>
>> Thanks
>>
>> JuanLu
>>

Lenni Madsen

Security Architect,
Dip. Eng. m. IDA.

Danish Defence IT
Helseholmen 1
2650 Hvidovre

Tel: (+45) 4567 7236
Mob: (+45) 2621 0011
Email: l.madsen@...

From forum: Muse User

Re: Extra headers not working

2009-10-05T03:53:29Z

Ah ok, that unfortunately makes sense. If you want persisted routing
entries you have to enable them, see the wsn-consumer examples.

<persistence>
<java-persistence-class>org.apache.muse.core.routing.RouterFilePersistence</java-persistence-class>
<persistence-location>router-entries</persistence-location>
</persistence>

must be enabled in muse.xml and the router-entries must be set out
similar to the wsn example. If you want to have a different
persistence scheme you can provide your own persistence class.

With the default you must ensure that the numbering of the file names
are unique but after that you can add/remove the actual number
parameters to not require reference params eg.

<?xml version="1.0" encoding="UTF-8"?>
<wsa:ReferenceParameters xmlns:wsa="http://www.w3.org/2005/08/addressing"/>

in the resource-instance-X.xml file.

If you do not enable persistence then each resource will get an
incremental reference parameter associated with it, which can be less
than helpful because - as you've found - the reference paremeter
number could change with each change in the muse (add remove of
resources for example).

Its also worth noting that you seem to have two instances running at
the same address, if this is intentional you should definitely look at
customising the reference params to indicate which resource is which.
For example each store could have its id as a reference.

On Mon, Oct 5, 2009 at 12:24 PM, <juanluis.prietomartinez@...> wrote:

> The think is that it works the first time that I run it after I deploy it, but afterwards that is the error, as far as I know the epr shouldn't change at all.
>
> -----Original Message-----
> From: Chris Twiner [mailto:chris.twiner@...]
> Sent: 05 October 2009 11:09
> To: muse-user@...
> Subject: Re: Extra headers not working
>
> Unless I'm missing something you aren't using the right epr. As the error message is telling you :
>
> <wsa:ReferenceParameters
>> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>> <muse-wsa:ResourceId
>> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">MuseResource-2</
>> mu
>> se-wsa:ResourceId>
>> </wsa:ReferenceParameters>
>
> seems to be missing.
>
> epr.addParameter(WsaConstants.DEFAULT_RESOURCE_ID_QNAME, "MuseResource-" + x);
>
> should help.
>
> On Mon, Oct 5, 2009 at 11:27 AM, <juanluis.prietomartinez@...> wrote:
>> Hi all,
>>
>> I have built a client for my muse app with wsd2java and I have added
>> the flag -headers to be able to add headers to the call that I need to
>> extract with another component.
>>
>> The proxy has been generated w/out any problem and it has the new
>> parameter Element[] in all the methods. To test it I am putting null
>> just to make a normal call to the webapp and I am having this issue.
>>
>> This is the call I am doing:
>>
>> public void testCreate() throws SoapFault {
>> proxy = new WsSongStoreProxy(new
>> EndpointReference(URI.create(providerUrl)), null);
>> proxy = new WsSongStoreProxy (elemToEpr
>> (proxy.createOperation(null)), null);
>> proxy.setTrace(true);
>> }
>>
>> And this is the trace with the error I am getting.
>>
>> org.apache.muse.ws.addressing.soap.SoapFault: [ID =
>> 'DestinationUnreachable'] There is no resource available at the given
>> EPR:
>>
>> <wsa:EndpointReference
>> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>>
>> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</w
>> sa
>> :Address>
>> </wsa:EndpointReference>
>>
>> The existing EPRs hosted by this endpoint are:
>>
>> <wsa:EndpointReference
>> xmlns:wsa="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">MuseResource-2</
>> mu
>> se-wsa:ResourceId>
>> </wsa:ReferenceParameters>
>>
>> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</w
>> sa
>> :Address>
>> </wsa:EndpointReference>
>>
>> <wsa:EndpointReference
>> xmlns:wsa="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">MuseResource-3</
>> mu
>> se-wsa:ResourceId>
>> </wsa:ReferenceParameters>
>>
>> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</w
>> sa
>> :Address>
>> </wsa:EndpointReference>
>> at
>> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceCli
>> en
>> t.java:298)
>> at
>> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceCli
>> en
>> t.java:232)
>> at
>> test.proxy.WsSongStoreProxy.createOperation(WsSongStoreProxy.java:131)
>> at core.testHeaders.testCreate(testHeaders.java:26)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
>> av
>> a:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
>> or
>> Impl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>> at junit.framework.TestCase.runTest(TestCase.java:164)
>> at junit.framework.TestCase.runBare(TestCase.java:130)
>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>> at junit.framework.TestResult.runProtected(TestResult.java:124)
>> at junit.framework.TestResult.run(TestResult.java:109)
>> at junit.framework.TestCase.run(TestCase.java:120)
>> at junit.framework.TestSuite.runTest(TestSuite.java:230)
>> at junit.framework.TestSuite.run(TestSuite.java:225)
>> at
>> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(J
>> Un
>> it3TestReference.java:130)
>> at
>> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.
>> ja
>> va:38)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remote
>> Te
>> stRunner.java:467)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remote
>> Te
>> stRunner.java:683)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestR
>> un
>> ner.java:390)
>> at
>> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTest
>> Ru
>> nner.java:197)
>>
>> Thanks
>>
>> JuanLu
>>
>

From forum: Muse User

RE: Extra headers not working

2009-10-05T03:24:12Z

The think is that it works the first time that I run it after I deploy it, but afterwards that is the error, as far as I know the epr shouldn't change at all.

-----Original Message-----
From: Chris Twiner [mailto:chris.twiner@...]
Sent: 05 October 2009 11:09
To: muse-user@...
Subject: Re: Extra headers not working

Unless I'm missing something you aren't using the right epr. As the error message is telling you :

<wsa:ReferenceParameters
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <muse-wsa:ResourceId
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">MuseResource-2</
> mu
> se-wsa:ResourceId>
> </wsa:ReferenceParameters>

seems to be missing.

epr.addParameter(WsaConstants.DEFAULT_RESOURCE_ID_QNAME, "MuseResource-" + x);

should help.

On Mon, Oct 5, 2009 at 11:27 AM, <juanluis.prietomartinez@...> wrote:

> Hi all,
>
> I have built a client for my muse app with wsd2java and I have added
> the flag -headers to be able to add headers to the call that I need to
> extract with another component.
>
> The proxy has been generated w/out any problem and it has the new
> parameter Element[] in all the methods. To test it I am putting null
> just to make a normal call to the webapp and I am having this issue.
>
> This is the call I am doing:
>
> public void testCreate() throws SoapFault {
> proxy = new WsSongStoreProxy(new
> EndpointReference(URI.create(providerUrl)), null);
> proxy = new WsSongStoreProxy (elemToEpr
> (proxy.createOperation(null)), null);
> proxy.setTrace(true);
> }
>
> And this is the trace with the error I am getting.
>
> org.apache.muse.ws.addressing.soap.SoapFault: [ID =
> 'DestinationUnreachable'] There is no resource available at the given
> EPR:
>
> <wsa:EndpointReference
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</w
> sa
> :Address>
> </wsa:EndpointReference>
>
> The existing EPRs hosted by this endpoint are:
>
> <wsa:EndpointReference
> xmlns:wsa="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">MuseResource-2</
> mu
> se-wsa:ResourceId>
> </wsa:ReferenceParameters>
>
> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</w
> sa
> :Address>
> </wsa:EndpointReference>
>
> <wsa:EndpointReference
> xmlns:wsa="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">MuseResource-3</
> mu
> se-wsa:ResourceId>
> </wsa:ReferenceParameters>
>
> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</w
> sa
> :Address>
> </wsa:EndpointReference>
> at
> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceCli
> en
> t.java:298)
> at
> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceCli
> en
> t.java:232)
> at
> test.proxy.WsSongStoreProxy.createOperation(WsSongStoreProxy.java:131)
> at core.testHeaders.testCreate(testHeaders.java:26)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> av
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> or
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(J
> Un
> it3TestReference.java:130)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.
> ja
> va:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remote
> Te
> stRunner.java:467)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(Remote
> Te
> stRunner.java:683)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestR
> un
> ner.java:390)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTest
> Ru
> nner.java:197)
>
> Thanks
>
> JuanLu
>

From forum: Muse User

Re: Extra headers not working

2009-10-05T03:09:26Z

Unless I'm missing something you aren't using the right epr. As the
error message is telling you :

<wsa:ReferenceParameters
> xmlns:wsa="http://www.w3.org/2005/08/addressing">
> <muse-wsa:ResourceId
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing">MuseResource-2</mu
> se-wsa:ResourceId>
> </wsa:ReferenceParameters>

seems to be missing.

epr.addParameter(WsaConstants.DEFAULT_RESOURCE_ID_QNAME, "MuseResource-" + x);

should help.

On Mon, Oct 5, 2009 at 11:27 AM, <juanluis.prietomartinez@...> wrote:

> Hi all,
>
> I have built a client for my muse app with wsd2java and I have added the
> flag -headers to be able to add headers to the call that I need to
> extract with another component.
>
> The proxy has been generated w/out any problem and it has the new
> parameter Element[] in all the methods. To test it I am putting null
> just to make a normal call to the webapp and I am having this issue.
>
> This is the call I am doing:
>
> public void testCreate() throws SoapFault {
> proxy = new WsSongStoreProxy(new
> EndpointReference(URI.create(providerUrl)), null);
> proxy = new WsSongStoreProxy (elemToEpr
> (proxy.createOperation(null)), null);
> proxy.setTrace(true);
> }
>
> And this is the trace with the error I am getting.
>
> org.apache.muse.ws.addressing.soap.SoapFault: [ID =
> 'DestinationUnreachable'] There is no resource available at the given
> EPR:
>
> <wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">
>
> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</wsa
> :Address>
> </wsa:EndpointReference>
>
> The existing EPRs hosted by this endpoint are:
>
> <wsa:EndpointReference xmlns:wsa="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">MuseResource-2</mu
> se-wsa:ResourceId>
> </wsa:ReferenceParameters>
>
> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</wsa
> :Address>
> </wsa:EndpointReference>
>
> <wsa:EndpointReference xmlns:wsa="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">MuseResource-3</mu
> se-wsa:ResourceId>
> </wsa:ReferenceParameters>
>
> <wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</wsa
> :Address>
> </wsa:EndpointReference>
> at
> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
> t.java:298)
> at
> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
> t.java:232)
> at
> test.proxy.WsSongStoreProxy.createOperation(WsSongStoreProxy.java:131)
> at core.testHeaders.testCreate(testHeaders.java:26)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
> a:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
> Impl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.runTest(TestSuite.java:230)
> at junit.framework.TestSuite.run(TestSuite.java:225)
> at
> org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUn
> it3TestReference.java:130)
> at
> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja
> va:38)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
> stRunner.java:467)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
> stRunner.java:683)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun
> ner.java:390)
> at
> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu
> nner.java:197)
>
> Thanks
>
> JuanLu
>

From forum: Muse User

Extra headers not working

2009-10-05T02:27:29Z

Hi all,

I have built a client for my muse app with wsd2java and I have added the
flag -headers to be able to add headers to the call that I need to
extract with another component.

The proxy has been generated w/out any problem and it has the new
parameter Element[] in all the methods. To test it I am putting null
just to make a normal call to the webapp and I am having this issue.

This is the call I am doing:

public void testCreate() throws SoapFault {
proxy = new WsSongStoreProxy(new
EndpointReference(URI.create(providerUrl)), null);
proxy = new WsSongStoreProxy (elemToEpr
(proxy.createOperation(null)), null);
proxy.setTrace(true);
}

And this is the trace with the error I am getting.

org.apache.muse.ws.addressing.soap.SoapFault: [ID =
'DestinationUnreachable'] There is no resource available at the given
EPR:

<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing">

<wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</wsa
:Address>
</wsa:EndpointReference>

The existing EPRs hosted by this endpoint are:

<wsa:EndpointReference xmlns:wsa="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">MuseResource-2</mu
se-wsa:ResourceId>
</wsa:ReferenceParameters>

<wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</wsa
:Address>
</wsa:EndpointReference>

<wsa:EndpointReference xmlns:wsa="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">MuseResource-3</mu
se-wsa:ResourceId>
</wsa:ReferenceParameters>

<wsa:Address>http://127.0.0.1:8080/WsSongStore/services/WsSongStore</wsa
:Address>
</wsa:EndpointReference>
at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
t.java:298)
at
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClien
t.java:232)
at
test.proxy.WsSongStoreProxy.createOperation(WsSongStoreProxy.java:131)
at core.testHeaders.testCreate(testHeaders.java:26)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUn
it3TestReference.java:130)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.ja
va:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
stRunner.java:467)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTe
stRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRun
ner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRu
nner.java:197)

Thanks

JuanLu

From forum: Muse User

Re: Add element to header

2009-09-30T21:31:11Z

Hi JuanLu,

Creating your own SoapClient is probably the best way to get full
control of what is sent from a generated client. The default simply
sends the xml that the client constructs, your version could
manipulate headers / perform encryption etc.

cheers,
Chris

On Wed, Sep 30, 2009 at 11:21 AM, <juanluis.prietomartinez@...> wrote:

> Hi all,
>
> I am having an issue trying to add an element to a header in my muse
> call.
> I have seen how to do it reading the value from the muse.xml but that
> means that the webapp of the service does it, whereas I want to do it by
> using the proxy in my client.
> This is an example of how the request should look like once the header
> has been added.
>
> Can anybody please help me?
>
> <?xml version="1.0" encoding="UTF-8"?>
> <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://ec2-79-125-39-81
> .eu-west-1.compute.amazonaws.com:8080/songstore</wsa:To>
> <wsa:Action
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://songstore.org/ca
> p/mgmt/CreateOperation</wsa:Action>
> <wsa:MessageID
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:d35df355-0c0e-6024
> -b5af-33bf7addc976</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>
> <newHeader>HEADERVALUE</newHeader>
> </soap:Header>
> <soap:Body>
> <pfx1:CreateOperation
> xmlns:pfx1="http://songstore.org/cap/mgmt"/>
> </soap:Body>
> </soap:Envelope>
>
> Thanks,
> JuanLu
>

From forum: Muse User

Add element to header

2009-09-30T02:21:02Z

Hi all,

I am having an issue trying to add an element to a header in my muse
call.
I have seen how to do it reading the value from the muse.xml but that
means that the webapp of the service does it, whereas I want to do it by
using the proxy in my client.
This is an example of how the request should look like once the header
has been added.

Can anybody please help me?

<?xml version="1.0" encoding="UTF-8"?>
<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://ec2-79-125-39-81
.eu-west-1.compute.amazonaws.com:8080/songstore</wsa:To>
<wsa:Action
xmlns:wsa="http://www.w3.org/2005/08/addressing">http://songstore.org/ca
p/mgmt/CreateOperation</wsa:Action>
<wsa:MessageID
xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:d35df355-0c0e-6024
-b5af-33bf7addc976</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>
<newHeader>HEADERVALUE</newHeader>
</soap:Header>
<soap:Body>
<pfx1:CreateOperation
xmlns:pfx1="http://songstore.org/cap/mgmt"/>
</soap:Body>
</soap:Envelope>

Thanks,
JuanLu

From forum: Muse User

[jira] Resolved: (MUSE-239) response name should come from the wsdl

2009-09-28T12:11:16Z

[ https://issues.apache.org/jira/browse/MUSE-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner resolved MUSE-239.
-------------------------------

Resolution: Fixed

Fixed the bug itself, in two files, added a host of others to test. Kept Axis prefix "muse-op" in the fix. The old code is still present, just not called. 2.3.0 will clean that out.

> response name should come from the wsdl
> ---------------------------------------
>
> Key: MUSE-239
> URL: https://issues.apache.org/jira/browse/MUSE-239
> Project: Muse
> Issue Type: Bug
> Components: Core Engine - Routing and Serialization
> Environment: Muse 2.2.0, Eclipse 3.2.1
> Reporter: Vinh Nguyen
> Assignee: Chris Twiner
> Fix For: 2.2.1
>
>
> When generating the client proxies, wsdl2java properly reads the response names from the wsdl and stores them in the proxy metadata section. But on the server, Muse actually creates the response name based on the request name, and doesn't look at the wsdl for the actual response name.
> I found this error when not using the "normal" naming convention like MyOperationRequest and MyOperationResponse. Instead, I had it as SomeResponse, so the client threw an error because the server was returning a different response name than expected.
> The bug is in AbstractMessageHandler.createResponseName(). It takes the properties from the request QName, and then creates a new one with "Response" appended.
> Also, the method's javadoc says that "users can override this method to change the response name", but the method itself is private. So to override, users must override the class constructor itself.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

From forum: Muse - Dev

[jira] Resolved: (MUSE-293) XPath filter gets Namespaces from NotificationMessage

2009-09-28T05:14:16Z

[ https://issues.apache.org/jira/browse/MUSE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner resolved MUSE-293.
-------------------------------

Resolution: Fixed

Code added, tests temporarily in the cunningly named tests folder.

Attempts have been made to keep it binary compatible.

> XPath filter gets Namespaces from NotificationMessage
> -----------------------------------------------------
>
> Key: MUSE-293
> URL: https://issues.apache.org/jira/browse/MUSE-293
> Project: Muse
> Issue Type: Bug
> Components: Utilities - General, QName, and XML
> Affects Versions: 2.2.0
> Reporter: Matthes Rieke
> Assignee: Chris Twiner
> Priority: Minor
> Fix For: 2.2.1
>
> Attachments: XPathFilterNamespaceTest.java
>
>
> I have stumbled across a problem when trying to filter a NotificationMessage with an XPath expression containing namespace declarations (e.G. //om:Observation/om:procedure - where om is "http://www.opengis.net/om/1.0").
> Perhaps I made some mistake while subscribing with this filter, but to me it seems, that the MessagePatternFilter just invokes XPathUtils.isMatch(). isMatch itself invokes XPathAPI.eval(context, xpath) [from apache xalan api] and that method has no parameter for the namespaceNode. This has the result that the XPath expression takes its namespaces from the NotificationMessage, which of course may differ from the ones specified in my subscribe request.
> Also I noticed that namespaces in a MessagePatternFilter xml file (see below) just get erased when parsing the xml with the FilterFactory.
> Filter to parse:
> <wsnt:Filter xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
> <wsnt:MessageContent Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"
> xmlns:om="http://www.opengis.net/om/1.0">
> //om:Observation/om:procedure/@xlink:href='urn:ogc:object:procedure:CITE:WeatherService:LGA'
> </wsnt:MessageContent>
> </wsnt:Filter>
> this gets parsed in the subscribe operation of NotificationProducer (I assume this is done before in the FilterFactory):
> <wsnt:Filter xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
> <wsnt:MessageContent Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">//om:Observation/om:procedure/@xlink:href='urn:ogc:object:procedure:CITE:WeatherService:LGA'</wsnt:MessageContent>
> </wsnt:Filter>
> As you can see the namespace "om:...." is removed.

From forum: Muse - Dev

[jira] Resolved: (MUSE-299) SOAP responses are not logged

2009-09-28T05:10:16Z

[ https://issues.apache.org/jira/browse/MUSE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner resolved MUSE-299.
-------------------------------

Resolution: Fixed
Fix Version/s: (was: 2.3.0)

added the logging, only AxisIsolationLayer is affected.

> SOAP responses are not logged
> -----------------------------
>
> Key: MUSE-299
> URL: https://issues.apache.org/jira/browse/MUSE-299
> Project: Muse
> Issue Type: Bug
> Components: Deployment - Axis2
> Affects Versions: 2.2.0
> Reporter: Francesco Scandelli
> Assignee: Chris Twiner
> Fix For: 2.2.1
>
>
> The documentation (http://ws.apache.org/muse/docs/2.2.0/manual/architecture/deployment-descriptor.html) says that setting the logging level to FINE will cause Muse to record every SOAP request and response that it processes but actually only the requests are traced (look at org.apache.muse.core.platform.axis2.AxisIsolationLayer).

From forum: Muse - Dev

[jira] Commented: (MUSE-299) SOAP responses are not logged

2009-09-22T13:04:16Z

[ https://issues.apache.org/jira/browse/MUSE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758402#action_12758402 ]

Chris Twiner commented on MUSE-299:
-----------------------------------

just added after the invoke:

// HACK part two (issue 299) log the response
if (router.getLog().getLevel() == Level.FINE && soapResponse != null)
{
LoggingUtils.logMessage(router.getLog(), soapResponse, false);
}

> SOAP responses are not logged
> -----------------------------
>
> Key: MUSE-299
> URL: https://issues.apache.org/jira/browse/MUSE-299
> Project: Muse
> Issue Type: Bug
> Components: Deployment - Axis2
> Affects Versions: 2.2.0
> Reporter: Francesco Scandelli
> Assignee: Chris Twiner
> Fix For: 2.2.1, 2.3.0
>
>
> The documentation (http://ws.apache.org/muse/docs/2.2.0/manual/architecture/deployment-descriptor.html) says that setting the logging level to FINE will cause Muse to record every SOAP request and response that it processes but actually only the requests are traced (look at org.apache.muse.core.platform.axis2.AxisIsolationLayer).

From forum: Muse - Dev

[jira] Assigned: (MUSE-299) SOAP responses are not logged

2009-09-22T13:02:17Z

[ https://issues.apache.org/jira/browse/MUSE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner reassigned MUSE-299:
---------------------------------

Assignee: Chris Twiner (was: Dan Jemiolo)

> SOAP responses are not logged
> -----------------------------
>
> Key: MUSE-299
> URL: https://issues.apache.org/jira/browse/MUSE-299
> Project: Muse
> Issue Type: Bug
> Components: Deployment - Axis2
> Affects Versions: 2.2.0
> Reporter: Francesco Scandelli
> Assignee: Chris Twiner
> Fix For: 2.2.1, 2.3.0
>
>
> The documentation (http://ws.apache.org/muse/docs/2.2.0/manual/architecture/deployment-descriptor.html) says that setting the logging level to FINE will cause Muse to record every SOAP request and response that it processes but actually only the requests are traced (look at org.apache.muse.core.platform.axis2.AxisIsolationLayer).

From forum: Muse - Dev

[jira] Commented: (MUSE-293) XPath filter gets Namespaces from NotificationMessage

2009-09-22T12:54:16Z

[ https://issues.apache.org/jira/browse/MUSE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758397#action_12758397 ]

Chris Twiner commented on MUSE-293:
-----------------------------------

coding done, checking tests into a temporary location (until a Maven friendly way is found). In particular toXML writes out the correct namespace prefixes (allowing persistence of subscriptions etc).

From forum: Muse - Dev

[jira] Commented: (MUSE-293) XPath filter gets Namespaces from NotificationMessage

2009-09-22T08:28:16Z

[ https://issues.apache.org/jira/browse/MUSE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758270#action_12758270 ]

Chris Twiner commented on MUSE-293:
-----------------------------------

NOTE this does not adjust either ProducerPropertiesFilter or TopicFilters use of XPathUtils.isMatch. The reason being topicfilters shouldn't really be doing xpath filtering anyway (thats messagefilters job) and the other filter should probably be using the generated producer properties.

If either of these is an issue in the future it should be easy to remedy them.

From forum: Muse - Dev

[jira] Commented: (MUSE-293) XPath filter gets Namespaces from NotificationMessage

2009-09-22T08:00:16Z

[ https://issues.apache.org/jira/browse/MUSE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758262#action_12758262 ]

Chris Twiner commented on MUSE-293:
-----------------------------------

In order to maintain binary compatibility for the 2.2.1 release I'm adding a new constructor, the other will simply be deprecated.

From forum: Muse - Dev

Show wsdl

2009-09-15T04:27:16Z

Hi all,

I am trying to show the wsdl of a muse web service on the browser, the
parameters and the location of the wsdl within the webapp are as I
describe below.

The wsdl is within a folder called wsdl
(webapps\WsSongStore\WEB-INF\classes\wsdl) and in the muse.xml you can
read this:

<wsdl>
<wsdl-file>/wsdl/WsSongStore.wsdl</wsdl-file>
<wsdl-port-type
xmlns:pfx="http://songstore.org/tns">pfx:WsSongStorePortType</wsdl-port-
type>
</wsdl>

But when I do a
http://localhost:8080/WsSongStore/services/WsSongStore?wsdl what I get
back is a 405 telling me that get method is not allowed. It is urgent to
fix this because I need to show the wsdl to expose it to the gateway.

Can you please help me with this?

Thanks

JuanLu

From forum: Muse User

Question on the Consumer

2009-09-04T07:44:49Z

Hi,

I have a WSN consumer based on the Muse Project.

With a apache muse based producer, the consumer can handle the requests
perfectly fine. But when I receive request from another server where
apache muse is not being used, following SOAP Response being sent from the
muse server.

<soap:Text>[ID = 'ActionNotSupported'] The resource at 'consumer' does
not expose an operation with the WS-Action
'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify' through
any of its capabilities.</soap:Text>
</soap:Reason>

Things I tried :

1. Add capability-uri "
http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify" and the
impl class is SimpleNotificationConsumer.

2. Tried to add another port type and a binding where I defined the
SoapAction and Action for the operation to be the "
http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer/Notify"

Hopefully this is just a configuration issue. Please let me know what I
can do to get this working on different producers.

FYI: I am using muse 2.1.0 , and Mini Servlet as my entry point.

Thanks and Regards
Sudhakar

______________________________________________________________________________________
Sudhakar V Chellam
e-mail : svelkant@...
Phone : 919-224-1179 [ Tie line - 687 - 1179 ]

From forum: Muse User

[jira] Resolved: (MUSE-268) SoapFault(Element) constructor retrieves code but loses namespace

2009-08-20T16:04:14Z

[ https://issues.apache.org/jira/browse/MUSE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Twiner resolved MUSE-268.
-------------------------------

Resolution: Invalid

Andrea further confirms this isn't a bug, marking as Invalid, unless another test can show validity.

> SoapFault(Element) constructor retrieves code but loses namespace
> -----------------------------------------------------------------
>
> Key: MUSE-268
> URL: https://issues.apache.org/jira/browse/MUSE-268
> Project: Muse
> Issue Type: Bug
> Environment: Muse 2.2.0
> Reporter: Vinh Nguyen
> Assignee: Chris Twiner
> Priority: Minor
> Fix For: 2.2.1
>
> Attachments: FaultCodeNSTest.java
>
>
> I'm doing the following in SimpleResourceRouter:
> public Element invoke(Element soapBody)
> {
> // Check the error code.
> Element response = super.invoke(soapBody);
> QName name = XmlUtils.getElementQName(response);
> if (name.equals(SoapConstants.FAULT_QNAME))
> {
> SoapFault fault = new SoapFault(response);
> QName faultCode = fault.getCode();
> System.out.println("Fault code: " + faultCode.getPrefix() + ", " + faultCode.getLocalPart() + ", " + faultCode.getNamespaceURI());
> if (faultCode.equals(SoapConstants.SENDER_QNAME))
> {
> System.out.println("Fault is a user error!");
> }
> }
> return response;
> }
> But I noticed that the faultCode's namespace is lost. So when I try to compare it to SoapConstants.SENDER_QNAME, it always returns false. So it is difficult to check if the fault is a user error, or an actual system (Muse) error.

From forum: Muse - Dev

Dan Jemiolo is out of the office.

2009-07-06T10:56:16Z

I will be out of the office starting 07/06/2009 and will not return until 07/08/2009.

I will have access to email throughout the day. Please contact Jose Ortiz for any urgent matters related to WebSphere CloudBurst.

From forum: Muse - Dev

PMC Reorganization and July board report

2009-07-06T09:55:49Z

Hi everyone:

Once again, I'm cc'ing all the -dev lists to make absolutely sure everyone
sees this note. Future mails will just go to general@.

It's time to get this discussion going, and hopefully bring it to some kind
of a place from which we can affect change as a community. We're going to
submit a report to the board in July, and I'd really like to be able to say
something other than "radio silence on the PMC reorg front". :)

Can we talk some more about this in the near term? As you know, there is a
wiki page at:

http://wiki.apache.org/ws/FrontPage/WebServicesPMCReorg

One proposal there has four supporters so far, and other proposals, comments,
thoughts, etc., are very welcome.

Please, people, chime in. Either put your thoughts on the wiki, or continue
the discussion via email at general@... - please try and keep the
discussion about this topic on that list and not on the individual project
lists, since this is clearly a community-wide topic.

Thanks,
--Glen

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

From forum: Muse - Dev

Saurabh Dravid is out of the office.

2009-07-02T21:43:24Z

I will be out of the office starting 06/25/2009 and will not return until
07/06/2009.

Thanks for your email. I will be back to work only on 06-July-2009 and will
respond once I return. For any urgent issues contact my manager "Ramsy V
Pinto " (rvpinto@...).

From forum: Muse User

How i can get the WSDM definition for a resource

2009-07-02T20:59:41Z

Hi i am comfused how i can get the WSDM definition for a resource, Please help me! Thank you!

From forum: Muse User

Help. muse-2.2.0 and wsdl2java

2009-06-25T07:06:39Z

Hi,

I tried wsdl2java on both Unix and Windows and I get the following error:

Any ideas:

[pchandler]$ wsdl2java.sh -osgi -wsdl soap-bindings.wsdl -output output
Exception in thread "main" org.apache.muse.tools.generator.util.MuseRuntimeException: [ID = 'InvalidArgs'] The arguments passed to wsdl2java are not valid. Please rerun with -help.
at org.apache.muse.tools.generator.Wsdl2Java.checkProjectizerArg(Wsdl2Java.java:596)
at org.apache.muse.tools.generator.Wsdl2Java.main(Wsdl2Java.java:256)

Peter.

From forum: Muse User

Dan Jemiolo is out of the office.

2009-06-12T15:01:47Z

I will be out of the office starting 06/12/2009 and will not return until 06/22/2009.

If you have a question related to WebSphere CloudBurst, please forward it to Rohith Ashok or my manager, Jake Mickley.

From forum: Muse - Dev

One more thing..

2009-06-12T12:50:18Z

If you'd like to discuss the PMC reorganization issue, please keep that
thread on general@ws instead of any of the project-specific lists.

Thanks!

--Glen

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

From forum: Muse - Dev

Board report for June, and splitting the project

2009-06-12T12:25:21Z

Hi all!

Two things. First off, it's of course that time again. Kurt (thanks Kurt)
has been kind enough to set up the template report at

http://wiki.apache.org/ws/ReportForJun2009

Some content has already been added, but please feel encouraged to add your
project's status/highlights, or anything you feel needs to be communicated up
to the board level.

In particular, I was hoping to have more conversation and consensus around
the "splitting the project" idea, but that has been slow to get going. As a
reminder, please visit the wiki page for this discussion at:

http://wiki.apache.org/ws/FrontPage/WebServicesPMCReorg

There are proposals and comments there - please feel free to add more, or to
add yourself as a supporter to any of the proposals there currently.

Unfortunately there was a bit of a date snafu with the automated reminder
system this time around, and so I thought we had another week and a half
before the report was due... but actually it's due by the 15th, which is
Monday. Since I do not think we're going to have enough time for an adequate
discussion before then, I am planning to ask the board to allow us to report
at next month's meeting instead (we'll stay on our regular Mar/Jun/Sept/Dec
schedule, just move this one report).

Thanks,
--Glen
Your Friendly Neighborhood PMC Chair

---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@...
For additional commands, e-mail: muse-dev-help@...

From forum: Muse - Dev

Re: how create a resoruce

2009-06-03T04:46:13Z

What I meant to say:

The factory included has the potential to instantiate resources
programatically of other services than it's own, so that
1) you can have some resource monitor call the factory and ask it to
instantiate more version of a service
2) provide an easy way to instantiate services with specific
ResourceID's if needed (the same code can be used for serverside calls
only, if left out of the internet exposed WSDL)

Now if the CounterResourceIdFactory does allow for ResourceID's of a
different type than MuseResource-XX I don't really know.

/Lenni
On Jun 2, 2009, at 17:02 GMT+02:00, Francesco D'Andria wrote:

> Dear Lenni,
>
> First of all, thank you so much for the example you sent to us last
> week.
> BTW I would like to know if, when you say "it includes a small
> factory to
> showcase ho to create resources on the fly, ", it means that, to
> specify my
> RsourceId, I need to include a factory. I was convinced I could
> reuse the
> factory implementation provided by MUSE (I'm speaking about the "
> CounterResourceIdFactory").
>
>
> regards
> Francesco
>
> 2009/5/30 Lenni Madsen <l.madsen@...>
>
>> all right, it seems most of the issues is related to my laptop
>> environment,
>> there must be some settings that are out of whack. In any case I've
>> attached my general idea for the wsn-producer example, it includes
>> a small
>> factory to showcase ho to create resources on the fly, mind you if
>> you need
>> to programatically change the ResourceID of your resource instances
>> you
>> would need to edit the EndpointReference in the WsFactory step
>> createWithEprOperation
>> before the line with next.initialize(); I've left room in the
>> operation
>> call to support a call with the desired ResourceId, though I haven
>> implemented the actual code to make it happen, as it's "just" a
>> simple xml
>> edit operation.
>>
>> Mind you this code should work, though as this an initial delivery
>> chances
>> are that there might be a bug or two :) Also the code was run on a
>> Mac so
>> make sure you edit the build.properties to reflect your system
>> environments.
>>
>> Happy hunting.
>>
>> /Lenni
>>
>>
>> On May 25, 2009, at 22:51 GMT+02:00, Lenni Madsen wrote:
>>
>> I've run into a few odd issues with my proposed example and due to
>> a high
>> workload tomorrow, that I need to prepare for, I'm going to have to
>> keep you
>> all waiting a few days more. Hopefully no longer than Thursday. So
>> far it
>> generates and compiles, but some of the more "advance" things are
>> acting up
>> a bit.
>> On May 25, 2009, at 13:19 GMT+02:00, Lenni Madsen wrote:
>>
>> I might be able to include that in the example I hope to have done by
>> tonight (EST)
>>
>>
>>
>> On May 25, 2009, at 13:07 GMT+02:00, Francesco D'Andria wrote:
>>
>>
>> Hi all,
>>
>>
>> Could someone tell me the right code to create a new instance of a
>> transient
>>
>> grid service.
>>
>> I would like to specify my RsourceId and not MuseResource-1, please
>>
>> tell me also
>>
>> the code to interact with the same ResoruceID via other client...
>>
>>
>> thanks in advance and best regards
>>
>> Francesco
>>
>>
>> Lenni Madsen
>>
>>
>> Security Architect,
>>
>> Dip. Eng. m. IDA.
>>
>>
>> Danish Defence IT
>>
>> Helseholmen 1
>>
>> 2650 Hvidovre
>>
>>
>> Tel: (+45) 4567 7236
>>
>> Mob: (+45) 2621 0011
>>
>> Email: l.madsen@...
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Lenni Madsen
>>
>> Security Architect,
>> Dip. Eng. m. IDA.
>>
>> Danish Defence IT
>> Helseholmen 1
>> 2650 Hvidovre
>>
>> Tel: (+45) 4567 7236
>> Mob: (+45) 2621 0011
>> Email: l.madsen@...
>>
>>
>>
>>
>>

Lenni Madsen

Security Architect,
Dip. Eng. m. IDA.

Danish Defence IT
Helseholmen 1
2650 Hvidovre

Tel: (+45) 4567 7236
Mob: (+45) 2621 0011
Email: l.madsen@...

From forum: Muse User

Re: how create a resoruce

2009-06-02T08:02:18Z

Dear Lenni,

First of all, thank you so much for the example you sent to us last week.
BTW I would like to know if, when you say "it includes a small factory to
showcase ho to create resources on the fly, ", it means that, to specify my
RsourceId, I need to include a factory. I was convinced I could reuse the
factory implementation provided by MUSE (I'm speaking about the "
CounterResourceIdFactory").

regards
Francesco

2009/5/30 Lenni Madsen <l.madsen@...>

> all right, it seems most of the issues is related to my laptop environment,
> there must be some settings that are out of whack. In any case I've
> attached my general idea for the wsn-producer example, it includes a small
> factory to showcase ho to create resources on the fly, mind you if you need
> to programatically change the ResourceID of your resource instances you
> would need to edit the EndpointReference in the WsFactory step createWithEprOperation
> before the line with next.initialize(); I've left room in the operation
> call to support a call with the desired ResourceId, though I haven
> implemented the actual code to make it happen, as it's "just" a simple xml
> edit operation.
>
> Mind you this code should work, though as this an initial delivery chances
> are that there might be a bug or two :) Also the code was run on a Mac so
> make sure you edit the build.properties to reflect your system environments.
>
> Happy hunting.
>
> /Lenni
>
>
> On May 25, 2009, at 22:51 GMT+02:00, Lenni Madsen wrote:
>
> I've run into a few odd issues with my proposed example and due to a high
> workload tomorrow, that I need to prepare for, I'm going to have to keep you
> all waiting a few days more. Hopefully no longer than Thursday. So far it
> generates and compiles, but some of the more "advance" things are acting up
> a bit.
> On May 25, 2009, at 13:19 GMT+02:00, Lenni Madsen wrote:
>
> I might be able to include that in the example I hope to have done by
> tonight (EST)
>
>
>
> On May 25, 2009, at 13:07 GMT+02:00, Francesco D'Andria wrote:
>
>
> Hi all,
>
>
> Could someone tell me the right code to create a new instance of a
> transient
>
> grid service.
>
> I would like to specify my RsourceId and not MuseResource-1, please
>
> tell me also
>
> the code to interact with the same ResoruceID via other client...
>
>
> thanks in advance and best regards
>
> Francesco
>
>
> Lenni Madsen
>
>
> Security Architect,
>
> Dip. Eng. m. IDA.
>
>
> Danish Defence IT
>
> Helseholmen 1
>
> 2650 Hvidovre
>
>
> Tel: (+45) 4567 7236
>
> Mob: (+45) 2621 0011
>
> Email: l.madsen@...
>
>
>
>
>
>
>
>
>
>
> Lenni Madsen
>
> Security Architect,
> Dip. Eng. m. IDA.
>
> Danish Defence IT
> Helseholmen 1
> 2650 Hvidovre
>
> Tel: (+45) 4567 7236
> Mob: (+45) 2621 0011
> Email: l.madsen@...
>
>
>
>
>

From forum: Muse User

Re: how create a resoruce

2009-05-30T03:57:13Z

all right, it seems most of the issues is related to my laptop environment, there must be some settings that are out of whack.

In any case I've attached my general idea for the wsn-producer example, it includes a small factory to showcase ho to create resources on the fly, mind you if you need to programatically change the ResourceID of your resource instances you would need to edit the EndpointReference in the WsFactory step createWithEprOperation before the line with next.initialize(); I've left room in the operation call to support a call with the desired ResourceId, though I haven implemented the actual code to make it happen, as it's "just" a simple xml edit operation.

Mind you this code should work, though as this an initial delivery chances are that there might be a bug or two :) Also the code was run on a Mac so make sure you edit the build.properties to reflect your system environments.

Happy hunting.

/Lenni

On May 25, 2009, at 22:51 GMT+02:00, Lenni Madsen wrote:

I've run into a few odd issues with my proposed example and due to a high workload tomorrow, that I need to prepare for, I'm going to have to keep you all waiting a few days more. Hopefully no longer than Thursday. So far it generates and compiles, but some of the more "advance" things are acting up a bit.
On May 25, 2009, at 13:19 GMT+02:00, Lenni Madsen wrote:

I might be able to include that in the example I hope to have done by tonight (EST)

On May 25, 2009, at 13:07 GMT+02:00, Francesco D'Andria wrote:

Hi all,

Could someone tell me the right code to create a new instance of a transient
grid service.
I would like to specify my RsourceId and not MuseResource-1, please
tell me also
the code to interact with the same ResoruceID via other client...

thanks in advance and best regards
Francesco

Lenni Madsen

Security Architect,
Dip. Eng. m. IDA.

Danish Defence IT
Helseholmen 1
2650 Hvidovre

Tel: (+45) 4567 7236
Mob: (+45) 2621 0011
Email: l.madsen@...

Lenni Madsen

Security Architect,
Dip. Eng. m. IDA.

Danish Defence IT
Helseholmen 1
2650 Hvidovre

Tel: (+45) 4567 7236
Mob: (+45) 2621 0011
Email: l.madsen@...

wsn-producer.zip (149K) Download Attachment

From forum: Muse User

Re: how create a resoruce

2009-05-25T13:51:44Z

I've run into a few odd issues with my proposed example and due to a
high workload tomorrow, that I need to prepare for, I'm going to have
to keep you all waiting a few days more. Hopefully no longer than
Thursday. So far it generates and compiles, but some of the more
"advance" things are acting up a bit.
On May 25, 2009, at 13:19 GMT+02:00, Lenni Madsen wrote:

> I might be able to include that in the example I hope to have done
> by tonight (EST)
>
>
> On May 25, 2009, at 13:07 GMT+02:00, Francesco D'Andria wrote:
>
>> Hi all,
>>
>> Could someone tell me the right code to create a new instance of a
>> transient
>> grid service.
>> I would like to specify my RsourceId and not MuseResource-1, please
>> tell me also
>> the code to interact with the same ResoruceID via other client...
>>
>> thanks in advance and best regards
>> Francesco
>
> Lenni Madsen
>
> Security Architect,
> Dip. Eng. m. IDA.
>
> Danish Defence IT
> Helseholmen 1
> 2650 Hvidovre
>
> Tel: (+45) 4567 7236
> Mob: (+45) 2621 0011
> Email: l.madsen@...
>
>
>

From forum: Muse User

Re: how create a resoruce

2009-05-25T04:19:05Z

I might be able to include that in the example I hope to have done by
tonight (EST)

On May 25, 2009, at 13:07 GMT+02:00, Francesco D'Andria wrote:

> Hi all,
>
> Could someone tell me the right code to create a new instance of a
> transient
> grid service.
> I would like to specify my RsourceId and not MuseResource-1, please
> tell me also
> the code to interact with the same ResoruceID via other client...
>
> thanks in advance and best regards
> Francesco

Lenni Madsen

Security Architect,
Dip. Eng. m. IDA.

Danish Defence IT
Helseholmen 1
2650 Hvidovre

Tel: (+45) 4567 7236
Mob: (+45) 2621 0011
Email: l.madsen@...

From forum: Muse User

how create a resoruce

2009-05-25T04:07:14Z

Hi all,

Could someone tell me the right code to create a new instance of a transient
grid service.
I would like to specify my RsourceId and not MuseResource-1, please
tell me also
the code to interact with the same ResoruceID via other client...

thanks in advance and best regards
Francesco

From forum: Muse User

Re: Transport my own data types form wsn-producer to wsn-consumer

2009-05-24T23:38:39Z

some errors are showed above and
1) tomcat's logs localhost_log.2009-05-25.txt (wsn-producer):

2009-05-25 14:15:07 StandardContext[/balancer]org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]
2009-05-25 14:15:07 StandardContext[/jsp-examples]ContextListener: contextInitialized()
2009-05-25 14:15:07 StandardContext[/jsp-examples]SessionListener: contextInitialized()
2009-05-25 14:15:07 StandardContext[/servlets-examples]ContextListener: contextInitialized()
2009-05-25 14:15:07 StandardContext[/servlets-examples]SessionListener: contextInitialized()
2009-05-25 14:16:03 StandardContext[/servlets-examples]ContextListener: attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@42a818')

2) wsn-producer's log:
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ImmediateResourceTermination'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ScheduledResourceTermination'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Get'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Query'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Set'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsn/bw-2/NotificationProducer'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/Identity'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/ManageabilityCharacteristics'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/Description'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/OperationalStatus'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'WsResource' has started initialization of capability 'http://ws.apache.org/muse/test/wsrf/MyCapability'.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ImmediateResourceTermination.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ScheduledResourceTermination.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Get.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Query.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Set.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsn/bw-2/NotificationProducer.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/Identity.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/ManageabilityCharacteristics.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/Description.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://docs.oasis-open.org/wsdm/muws/capabilities/OperationalStatus.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'WsResource' has completed initialization of capability 'http://ws.apache.org/muse/test/wsrf/MyCapability.
2009-5-25 14:15:29 org.apache.muse.core.SimpleResource initialize
信息: [ID = 'ResourceInitialized'] The resource at 'WsResource' has been initialized.
2009-5-25 14:15:29 org.apache.muse.core.routing.SimpleResourceRouter initialize
信息: [ID = 'RouterIsInitialized'] The resource router has been initialized.
2009-5-25 14:15:29 org.apache.ws.muse.test.wsrf.MyCapabilityImpl$1 run
信息: Waiting 10 seconds before sending message...
2009-5-25 14:15:29 org.apache.muse.util.LoggingUtils logMessage
良好: [SERVER 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://localhost:8080/wsn-producer/services/WsResource</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsrf/rpw-2/GetResourceProperty/GetResourcePropertyRequest</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:5b0123cb-9fc9-b924-82b9-374e4d664be5</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:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<wsrf-rp:GetResourceProperty
xmlns:pfx1="http://ws.apache.org/muse/test/wsrf" xmlns:wsrf-rp="http://docs.oasis-open.org/wsrf/rp-2">pfx1:ServerName</wsrf-rp:GetResourceProperty>
</soap:Body>
</soap:Envelope>

2009-5-25 14:15:29 org.apache.muse.util.LoggingUtils logMessage
良好: [SERVER 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://www.w3.org/2005/08/addressing/role/anonymous</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsrf/rpw-2/GetResourceProperty/GetResourcePropertyResponse</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:f511d309-7855-5402-4df6-272ebb23d57c</wsa:MessageID>
<wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing" RelationshipType="wsa:Reply">uuid:5b0123cb-9fc9-b924-82b9-374e4d664be5</wsa:RelatesTo>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://localhost:8080/wsn-producer/services/WsResource</wsa:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<wsrf-rp:GetResourcePropertyResponse xmlns:wsrf-rp="http://docs.oasis-open.org/wsrf/rp-2">
<pfx1:ServerName xmlns:pfx1="http://ws.apache.org/muse/test/wsrf">muse-test.apache.org</pfx1:ServerName>
</wsrf-rp:GetResourcePropertyResponse>
</soap:Body>
</soap:Envelope>

2009-5-25 14:15:30 org.apache.muse.util.LoggingUtils logMessage
良好: [SERVER 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://localhost:8080/wsn-producer/services/WsResource</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsn/bw-2/NotificationProducer/SubscribeRequest</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:60819b9b-cf02-6168-3c69-f2f8d0a0ee71</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:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<wsnt:Subscribe xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
<wsnt:ConsumerReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://192.168.6.251:8080/wsn-consumer/services/consumer</wsa:Address>
</wsnt:ConsumerReference>
</wsnt:Subscribe>
</soap:Body>
</soap:Envelope>

2009-5-25 14:15:30 org.apache.muse.ws.notification.impl.SimpleSubscriptionManager setSubscriptionPolicy
警告: [ID = 'PolicyNotSupported'] WS-N SubscriptionPolicy is not supported. The policy value was: null
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'SubscriptionManager' has started initialization of capability 'http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata'.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'SubscriptionManager' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Get'.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'SubscriptionManager' has started initialization of capability 'http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager'.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'SubscriptionManager' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ImmediateResourceTermination'.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'SubscriptionManager' has started initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ScheduledResourceTermination'.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'SubscriptionManager' has completed initialization of capability 'http://schemas.xmlsoap.org/ws/2004/09/mex/GetMetadata.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'SubscriptionManager' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rpw-2/Get.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'SubscriptionManager' has completed initialization of capability 'http://docs.oasis-open.org/wsn/bw-2/SubscriptionManager.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'SubscriptionManager' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ImmediateResourceTermination.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'SubscriptionManager' has completed initialization of capability 'http://docs.oasis-open.org/wsrf/rlw-2/ScheduledResourceTermination.
2009-5-25 14:15:30 org.apache.muse.core.SimpleResource initialize
信息: [ID = 'ResourceInitialized'] The resource at 'SubscriptionManager' has been initialized.
2009-5-25 14:15:30 org.apache.muse.util.LoggingUtils logMessage
良好: [SERVER 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://www.w3.org/2005/08/addressing/role/anonymous</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsn/bw-2/NotificationProducer/SubscribeResponse</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:77358c3e-1a0c-f364-f0d1-afe2c1ee7d89</wsa:MessageID>
<wsa:RelatesTo xmlns:wsa="http://www.w3.org/2005/08/addressing" RelationshipType="wsa:Reply">uuid:60819b9b-cf02-6168-3c69-f2f8d0a0ee71</wsa:RelatesTo>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://localhost:8080/wsn-producer/services/WsResource</wsa:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<wsnt:SubscribeResponse xmlns:wsnt="http://docs.oasis-open.org/wsn/b-2">
<wsnt:SubscriptionReference>
<wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://localhost:8080/wsn-producer/services/SubscriptionManager</wsa:Address>
<wsa:ReferenceParameters xmlns:wsa="http://www.w3.org/2005/08/addressing">
<muse-wsa:ResourceId xmlns:muse-wsa="http://ws.apache.org/muse/addressing">MuseResource-1</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</wsnt:SubscriptionReference>
<wsnt:CurrentTime>2009-05-25T14:15:30+08:00</wsnt:CurrentTime>
</wsnt:SubscribeResponse>
</soap:Body>
</soap:Envelope>

2009-5-25 14:15:39 org.apache.ws.muse.test.wsrf.MyCapabilityImpl$1 run
信息: Sending message to consumers...
2009-5-25 14:15:41 org.apache.muse.util.LoggingUtils logError
信息: There was an error while processing a request:

The element type "HR" must be terminated by the matching end-tag "</HR>".

org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:298)
org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254)
org.apache.muse.ws.notification.remote.NotificationConsumerClient.notify(NotificationConsumerClient.java:99)
org.apache.muse.ws.notification.impl.SimpleSubscriptionManager.publish(SimpleSubscriptionManager.java:267)
org.apache.muse.ws.notification.impl.SimpleNotificationProducer.publish(SimpleNotificationProducer.java:445)
org.apache.muse.ws.notification.impl.SimpleNotificationProducer.publish(SimpleNotificationProducer.java:473)
org.apache.muse.ws.notification.impl.SimpleNotificationProducer.publish(SimpleNotificationProducer.java:462)
org.apache.ws.muse.test.wsrf.MyCapabilityImpl$1.run(Unknown Source)

------------------------------------------

3) tomcat's logs localhost_log.2009-05-25.txt (wsn-consumer):
2009-05-25 14:15:07 StandardContext[/balancer]org.apache.webapp.balancer.BalancerFilter: init(): ruleChain: [org.apache.webapp.balancer.RuleChain: [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string: News / Redirect URL: http://www.cnn.com], [org.apache.webapp.balancer.rules.RequestParameterRule: Target param name: paramName / Target param value: paramValue / Redirect URL: http://www.yahoo.com], [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL: http://jakarta.apache.org]]
2009-05-25 14:15:10 StandardContext[/jsp-examples]ContextListener: contextInitialized()
2009-05-25 14:15:10 StandardContext[/jsp-examples]SessionListener: contextInitialized()
2009-05-25 14:15:10 StandardContext[/servlets-examples]ContextListener: contextInitialized()
2009-05-25 14:15:10 StandardContext[/servlets-examples]SessionListener: contextInitialized()
2009-05-25 14:15:41 StandardWrapperValve[ApacheMuseServlet]: Servlet.service() for servlet ApacheMuseServlet threw exception
java.io.IOException: Element or attribute do not match QName production: QName::=(NCName':')?NCName.
at org.apache.muse.core.platform.mini.MiniServlet.doPost(MiniServlet.java:81)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:595)

4) wsn-consumer's log:
2009-5-25 14:15:41 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'consumer' has started initialization of capability 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer'.
2009-5-25 14:15:41 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitialized'] The resource at 'consumer' has started initialization of capability 'http://ws.apache.org/muse/test/wsn/consumer'.
2009-5-25 14:15:41 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'consumer' has completed initialization of capability 'http://docs.oasis-open.org/wsn/bw-2/NotificationConsumer.
2009-5-25 14:15:41 org.apache.muse.core.SimpleResource initializeCapabilities
良好: [ID = 'CapabilityInitializationComplete'] The resource at 'consumer' has completed initialization of capability 'http://ws.apache.org/muse/test/wsn/consumer.
2009-5-25 14:15:41 org.apache.muse.core.SimpleResource initialize
信息: [ID = 'ResourceInitialized'] The resource at 'consumer' has been initialized.
2009-5-25 14:15:41 org.apache.muse.core.routing.SimpleResourceRouter initialize
信息: [ID = 'RouterIsInitialized'] The resource router has been initialized.

From forum: Muse User