Nabble - Muse - Dev

[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@...

[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.

[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).

[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).

[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).

[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).

[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.

[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.

[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.

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.

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@...

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.

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@...

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@...

Web Services PMC - Organization and futures

2009-05-17T13:17:05Z

[PLEASE KEEP REPLIES TO THIS THREAD ON "general@ws". If you're not on it and
interested, please subscribe.]

Hi all:

June approaches, and with it another WS PMC board report. After the March
report, we were again asked by the board what's up with our project's
organization. As such, I'd like to re-open this discussion here, in hopes
that we can achieve a real consensus this time around, whatever the outcome.

PLEASE NOTE - we all have opinions, and while we certainly would like to sway
others to our point of view, let's make sure that we keep the conversation
respectful and considerate of each other's ideas (no matter how totally
insane they might sound to us. :) ).

Toward this end I've spun up a wiki page:

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

I'd like to record the proposals here, as well as a bullet-item list of
points that people think are important to consider in the discussion. I did
a very quick start of a couple of items, please feel free to jump in and add
/ edit stuff.

If it looks like we're heading towards some kind of agreement in the next
couple of weeks, that's awesome. If it appears we can't reach consensus, I'd
love to hear ideas as to how we should proceed - but for now, let's just talk
about it again and see what comes up.

Thanks,
--Glen
Your friendly neighborhood PMC chair

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

How to decalre new properties in service definition file

2009-05-07T23:40:05Z

Hi Chris,

I've modified the WsResource's definition file in wrsf example to add a new complex property, but get the following warning information after running wsdl2java:

WARNING: [ID = 'NoWSRPSchema'] No WS-RP schema found.

Also, there is no capability generated for the new property.

I've renamed the WsResource to WsrServerMBean. The content of WsrServerMBean.wsdl where the new property is added is as following:

......
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://www.30wish.com/muse/ManagementService">

<xsd:element name="WsrServerMBeanProperty">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="InShutdown" type="xsd:boolean" />
<xsd:element name="BuildID" type="xsd:string" />

</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element name="WsrServerMBeanProperties">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="wsrf-rl:CurrentTime" />
<xsd:element ref="wsrf-rl:TerminationTime" />
<xsd:element ref="wsrf-rp:QueryExpressionDialect" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="tns:WsrServerMBeanProperty" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

......

<wsdl:portType
name="WsrServerMBeanPortType"
wsrf-rp:ResourceProperties="tns:WsrServerMBeanProperties"
wsrmd:Descriptor="WsrServerMBeanMetadata"
wsrmd:DescriptorLocation="WsrServerMBean.rmd" >
......

The content of WsrServerMBean.rmd is as following:

<MetadataDescriptor xmlns:wsrl="http://docs.oasis-open.org/wsrf/rl-2"
xmlns:myns="http://www.30wish.com/muse/ManagementService" name="WsrServerMBeanMetadata"
interface="myns:WsrServerMBeanPortType"
wsdlLocation="http://www.30wish.com/muse/ManagementService WsrServerMBean.wsdl" >

<Property name="wsrl:CurrentTime" modifiability="read-only" mutability="mutable" />

<Property name="wsrl:TerminationTime" modifiability="read-only" mutability="mutable" />

<Property name="myns:WsrServerMBeanProperty" modifiability="read-write" mutability="mutable"/>

</MetadataDescriptor>
Could you tell me what's wrong?

Thanks.

Sara

Re: About ResourceId - 2

2009-05-05T06:48:11Z

hiya, I'm swamped at the moment, hence slow in replying, I'll try to
get to you're other emails soon.

When creating a new resource via a factory function you should return
at least the resources EPR. This allows the invoking code to know
what the new resource is.

Regarding the actual id creation that is entirely up to the creator of
the resource, ResourceManager.addResource provides the simple method
to store it against an epr.

The http://www.ibm.com/developerworks/library/ac-muse.html article
holds all the information necessary for such a pattern when proxying
(i.e. an actual new resource isn't created, just a new epr for that
resource).

In terms of file based persistence, you can choose any content you
wish, the basic aim is just to keep the eprs unique.

And finally, what I think you might actually need here is when
creating a new resource ...

In general if you find something like this : muse-wsa:ResourceId its
used by / created by the default ResourceIdFactory implementation
CounterResourceIdFactory (loaded with
org.apache.muse.core.descriptor.SimpleResourceDescriptor, see
http://ws.apache.org/muse/docs/2.2.0/manual/architecture/deployment-descriptor.html).

You can use whatever you wish for a java-id-factory-class, there are
also other default implementations, but I would advice that if the
resource id is not good for you that you choose something semantic,
something which identifies that resource for your domain (could be
userids etc).

I know that I have copy+pasted this kind of thing before, and that you
have found the java-id-factory-class yourself, I hope this fills in
the blanks.

As a note to all reading, I'm low on resource at the moment, and - as
I'm sure many other committers do - I do this in my free time, so
please excuse late answers and the current glacial pace of
development.

cheers,
Chris

On Tue, May 5, 2009 at 11:13 AM, SARA1232007 <cyl_axis@...> wrote:

>
> Hi Chris,
>
> I need to assign the value of resourceId which satisfies my own needs. Could
> you tell me which class is responsible for invoke the resourceId factory to
> get the value of resourceId?
>
> Urgently needs you help.
>
> Thanks.
>
> Sara
> --
> View this message in context: http://www.nabble.com/About-ResourceId---2-tp23383784p23383784.html
> Sent from the Muse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-dev-unsubscribe@...
> For additional commands, e-mail: muse-dev-help@...
>
>

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

About ResourceId - 2

2009-05-05T02:13:16Z

Hi Chris,

I need to assign the value of resourceId which satisfies my own needs. Could you tell me which class is responsible for invoke the resourceId factory to get the value of resourceId?

Urgently needs you help.

Thanks.

Sara

About resourceId

2009-05-03T18:51:00Z

Hi,

Can anyone tell me what else need to be done to access a resource, which generated by a factory, without resourceId?
Also, an another question: what should I do if I want to assign the resourceId value by an another class?

Thanks.

Sara

Nalini Vidapankal/India/IBM is out of the office.

2009-04-29T03:34:20Z

I will be out of the office starting 29/04/2009 and will not return until
04/05/2009.

I will not have access to my mails during this period. I will respond once
I am back to office.

Kindly contact Indumathy Gururao/India/IBM for any urgent issues related to
the AC-LA.

Thanks.
Nalini

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

Re: About use factory to create resource

2009-04-29T02:24:16Z

Hi Chris,

I search the WsrMEPMBean(managed resource) entry using ServiceGroup and found that the WsrMEPMBean has a resourceId with the value MuseResource-1. What I plan is to use the address 'http://127.0.0.1:8086/WsrServer/services/WsrMEPMBean' without resourceId, so I remove the subdirectory 'WsrMEPMBean' under 'router-entries' directory.

Can anyone tell me what else need to be done to access a resource, which generated by a factory, without resourceId?
Also, an another question: what should I do if I want to assign the resourceId value by an another class?

The muse.xml content is as following:

<router>
<java-router-class>org.apache.muse.core.routing.SimpleResourceRouter</java-router-class>
<logging>
<log-file>log/muse.log</log-file>
<log-level>FINE</log-level>
</logging>
<persistence>
<java-persistence-class>org.apache.muse.core.routing.RouterFilePersistence</java-persistence-class>
<persistence-location>router-entries</persistence-location>
</persistence>
</router>
<resource-type>
<context-path>WsrMEPMBean</context-path>
<wsdl>
<wsdl-file>/wsdl/WsrMEPMBean.wsdl</wsdl-file>
<wsdl-port-type xmlns:pfx="http://www.30wish.com/muse/ManagementService">pfx:WsrMEPMBeanPortType</wsdl-port-type>
</wsdl>
<java-id-factory-class>org.apache.muse.core.routing.CounterResourceIdFactory</java-id-factory-class>
<java-resource-class>org.apache.muse.ws.resource.impl.SimpleWsResource</java-resource-class>
... ...
Thanks.

Sara

About use factory to create resource

2009-04-27T06:16:53Z

Hi,

I tried to use a factory to create a managed resource and then access the resource directly without searching the ServiceGroup.

I have modified the wrsf example as following:
1) use WsrMEPMBeanFactory to create a managed resource, ie, WsrMEPMBean, the code is following:

public void initializeCompleted()
throws SoapFault
{
super.initializeCompleted();

ResourceManager manager = getResource().getResourceManager();

Resource next = manager.createResource("WsrMEPMBean");
next.initialize();

getLog().warning("WsrMEPMBeanFactoryImpl.initializeCompleted():: WsrMEPMBean address:"+next.getEndpointReference().getAddress());
}

2) rename the WsResource to WsrMEPMBean
3) remove the declarence and implementation of ServiceGroup and ServiceGroupEntry.

The log information of client which try to build a WsrServerClient to access "http://127.0.0.1:8086/WsrServer/services/WsrMEPMBean" directly without searching ServiceGroup. The client trace information tells me that the endpoint "http://127.0.0.1:8086/WsrServer/services/WsrMEPMBean" does not exist, while the server information tells me that the resource with address "http://127.0.0.1:8086/WsrServer/services/WsrMEPMBean" is already created. The detailed trace information of client is as following:

[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://127.0.0.1:8086/WsrServer/services/WsrMEPMBean</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/wsrf/rpw-2/GetResourcePropertyDocument/GetResourcePropertyDocumentRequest</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:0593b5c8-f369-8188-7674-e76599ba8a94</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:GetResourcePropertyDocument xmlns:wsrf-rp="http://docs.oasis-open.org/wsrf/rp-2"/>
</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:9ab4845a-7d97-746d-2faf-e68acb554fb4</wsa:MessageID>
<wsa:RelatesTo RelationshipType="wsa:Reply" xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:0593b5c8-f369-8188-7674-e76599ba8a94</wsa:RelatesTo>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://127.0.0.1:8086/WsrServer/services/WsrMEPMBean</wsa:Address>
</wsa:From>
</soap:Header>
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Sender</soap:Value>
<soap:Subcode xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soap:Value>wsa:DestinationUnreachable</soap:Value>
</soap:Subcode>
</soap:Code>
<soap:Reason>
<soap:Text>[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:8086/WsrServer/services/WsrMEPMBean</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"/>
<wsa:Address>http://127.0.0.1:8086/WsrServer/services/WsrMEPMBeanFactory</wsa:Address>
</wsa:EndpointReference>
</soap:Text>
</soap:Reason>
</soap:Fault>
</soap:Body>
</soap:Envelope>

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:8086/WsrServer/services/WsrMEPMBean</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"/>
<wsa:Address>http://127.0.0.1:8086/WsrServer/services/WsrMEPMBeanFactory</wsa:Address>
</wsa:EndpointReference>

The log information from server is as following:

10:22:03,342 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBos
s_4_2_2_GA date=200710221139)] Started in 1m:27s:229ms
10:22:16,140 ERROR [STDERR] 2009-4-27 10:22:16 org.apache.muse.core.SimpleResour
ce initialize
信息: [ID = 'ResourceInitialized'] The resource at 'WsrMEPMBean' has been initia
lized.
10:22:16,140 ERROR [STDERR] WsrMEPMBeanFactoryImpl.initializeCompleted():: WsrME
PMBean address:http://127.0.0.1:8086/WsrServer/services/WsrMEPMBean
10:22:16,140 ERROR [STDERR] 2009-4-27 10:22:16 com._30wish.www.muse.ManagementSe
rvice.WsrMEPMBeanFactoryImpl initializeCompleted

10:22:16,140 ERROR [STDERR] 2009-4-27 10:22:16 org.apache.muse.core.SimpleResour
ce initialize
信息: [ID = 'ResourceInitialized'] The resource at 'WsrMEPMBeanFactory' has been
initialized.
10:22:16,140 ERROR [STDERR] 2009-4-27 10:22:16 org.apache.muse.core.routing.Simp
leResourceRouter initialize
信息: [ID = 'RouterIsInitialized'] The resource router has been initialized.

Can anyone tell me what's wrong?

Thanks.

Sara

Re: about SimpleWsResource and SimpleResource

2009-04-27T06:13:31Z

Chris Twiner wrote:

Hi, sorry I should have been much clearer, In the email you copied and
pasted the xml content so we got < instead of <, this makes it
difficult to look at for each member of the list. Instead if you
could show the eprs themselves (so we see < not <) that makes it
easier for everyone on the list.
itional commands, e-mail: muse-dev-help@ws.apache.org

Hi Chris,

Sorry I still don't know what you mean. English is not my native language. Could you give an example of the msg with the required format?

Thank you very much for your patience!

Cheers,
Sara

Re: about SimpleWsResource and SimpleResource

2009-04-22T22:49:44Z

On Thu, Apr 23, 2009 at 3:23 AM, SARA1232007 <cyl_axis@...> wrote:

>
>
>
> In future posts to the mailing list can you please copy and paste the
> actual text of available EPRS (not just the escaped xml), its
> particularly difficult to read.
>
>
> Hi Chris,
>
> Thank you for your quick response. But I don't understand what you mean by
> "actual text of available EPRS , not just the escaped xml". Those
> information I post is gotten from Muse.
> --

Hi, sorry I should have been much clearer, In the email you copied and
pasted the xml content so we got < instead of <, this makes it
difficult to look at for each member of the list. Instead if you
could show the eprs themselves (so we see < not <) that makes it
easier for everyone on the list.

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

Re: about wsrf-rpQueryExpressionDialect capability

2009-04-22T18:39:55Z

why do you want to do that? It may be a completely legitimate thing to
do but I don't really understand it.

Normally the expressiondialects are only used when making a query such
as a filter for subscriptions, not exposed as resource properties.

The error message tells you that no capability configured for that
resource provides that property, if you really do want it as a
property then you must declare (and possibly implement) a capability
that provides it.

Hi Chris,

This program is developed according to the Muse wsrf example. Wsrf example declare a wsrf-rpQueryExpressionDialect without configure a capability for it. The reason I want wsrf-rpQueryExpressionDialect is I might need to query the managed resource using query expression.

Your further help is very much appreciated.

Thanks.

Sara

Re: about SimpleWsResource and SimpleResource

2009-04-22T18:23:53Z

In future posts to the mailing list can you please copy and paste the
actual text of available EPRS (not just the escaped xml), its
particularly difficult to read.

Hi Chris,

Thank you for your quick response. But I don't understand what you mean by "actual text of available EPRS , not just the escaped xml". Those information I post is gotten from Muse.

Re: about wsrf-rpQueryExpressionDialect capability

2009-04-21T22:31:29Z

On Wed, Apr 22, 2009 at 5:08 AM, SARA1232007 <cyl_axis@...> wrote:
>
> Hi,
>
> I declare the QueryExpressionDialect property in wsdl as following:
>

hiya,

why do you want to do that? It may be a completely legitimate thing to
do but I don't really understand it.

Normally the expressiondialects are only used when making a query such
as a filter for subscriptions, not exposed as resource properties.

The error message tells you that no capability configured for that
resource provides that property, if you really do want it as a
property then you must declare (and possibly implement) a capability
that provides it.

cheers,
Chris

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

Re: about the situation to use factory to create resource

2009-04-21T22:25:11Z

On Wed, Apr 22, 2009 at 5:05 AM, SARA1232007 <cyl_axis@...> wrote:

>
> Hi,
>
> It seems that in simple example, the managed resource is created when the
> invocation to it is called. And in wsrf example, a factory resource is used
> to create WsResource resource. What confused me is:
> Under what situation a factory is needed to create managed resource, and
> under what situation the resource is created automatically when the
> invocation to it is called?
>

Best advice is to always declare resources in the file system that you
intend to have available at startup (as per most examples). If you
need to create resources dynamically use a factory operation to create
them and return a new epr (look at the pullpoint interface for an
example).

If these aren't appropriate for you then at the other end of the scale
you can proxy (be careful with subscriptions though):

http://www.ibm.com/developerworks/autonomic/library/ac-muse.html?S_TACT=105AGX09&S_CMP=TipWSDM2

it also helps understand how muse creates resources dynamically.

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

Re: about SimpleWsResource and SimpleResource

2009-04-21T22:15:41Z

On Wed, Apr 22, 2009 at 5:04 AM, SARA1232007 <cyl_axis@...> wrote:

>
> Hi,
>
> I modify the simple example to add a new property.
> For SimpleResource definition in muse.xml, I alter the java-resource-class
> definition as following:
>
>
> <java-id-factory-class>org.apache.muse.core.routing.CounterResourceIdFactory</java-id-factory-class>
>
> <java-resource-class>org.apache.muse.ws.resource.impl.SimpleWsResource</java-resource-class>
>
> I run the client which extends WsResourceClient class to invoke
> firstOperation, and I get "There is no resource available at the given EPR"
> exception from client.The trace information from client as following:
>
> [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://127.0.0.1:8086/simple/services/SimpleResource</wsa:To>
> <wsa:Action
> xmlns:wsa="http://www.w3.org/2005/08/addressing">http://ws.apache.org/muse/test/simple/first/FirstOperation</wsa:Action>
> <wsa:MessageID
> xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:2ba3f950-9ab8-8759-1749-57cbe781cd1b</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>
> <muse-wsa:ResourceId
> xmlns:muse-wsa="http://ws.apache.org/muse/addressing"
> xmlns:wsa="http://www.w3.org/2005/08/addressing"
> wsa:IsReferenceParameter="true">MuseResource-1</muse-wsa:ResourceId>

Do you have a resource with this resourceid? According to the result
from Muse you don't. Depending on the routingpersistence settings you
should have a file somewhere under SimpleResource that has this
reference parameter.

In future posts to the mailing list can you please copy and paste the
actual text of available EPRS (not just the escaped xml), its
particularly difficult to read.

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

about wsrf-rpQueryExpressionDialect capability

2009-04-21T20:08:12Z

Hi,

I declare the QueryExpressionDialect property in wsdl as following:

<xsd:schema elementFormDefault="qualified" targetNamespace="http://ws.apache.org/muse/test/simple">
<xsd:element name="MyProperty" type="xsd:string"/>
<xsd:element name="WsResourceProperties">
<xsd:complexType>
<xsd:sequence>

<xsd:element maxOccurs="unbounded" minOccurs="0" ref="tns:MyProperty"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>

After I run client, I get the error msg of 'NoCapability
ForProperty' from server. The trace information from server as following:

16:58:58,562 ERROR [STDERR] java.lang.IllegalStateException: [ID = 'NoCapability
ForProperty'] There is no capability that defines the property {http://docs.oasi
s-open.org/wsrf/rp-2}QueryExpressionDialect. If you have a capability that is su
pposed to define this property, make sure the name is returned as part of WsReso
urceCapability.getPropertyNames().
16:58:58,562 ERROR [STDERR] at org.apache.muse.ws.resource.properties.impl.S
impleResourcePropertyCollection.validateSchema(Unknown Source)
16:58:58,562 ERROR [STDERR] at org.apache.muse.ws.resource.impl.SimpleWsReso
urce.initialize(SimpleWsResource.java:227)

Can anyone tell me what's wrong?

Thanks.

Sara

about the situation to use factory to create resource

2009-04-21T20:05:51Z

Hi,

It seems that in simple example, the managed resource is created when the invocation to it is called. And in wsrf example, a factory resource is used to create WsResource resource. What confused me is:
Under what situation a factory is needed to create managed resource, and under what situation the resource is created automatically when the invocation to it is called?

Thanks.

Sara

about SimpleWsResource and SimpleResource

2009-04-21T20:04:42Z

Hi,

I modify the simple example to add a new property.
For SimpleResource definition in muse.xml, I alter the java-resource-class definition as following:

<java-id-factory-class>org.apache.muse.core.routing.CounterResourceIdFactory</java-id-factory-class>
<java-resource-class>org.apache.muse.ws.resource.impl.SimpleWsResource</java-resource-class>

I run the client which extends WsResourceClient class to invoke firstOperation, and I get "There is no resource available at the given EPR" exception from client.The trace information from client as following:

[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://127.0.0.1:8086/simple/services/SimpleResource</wsa:To>
<wsa:Action xmlns:wsa="http://www.w3.org/2005/08/addressing">http://ws.apache.org/muse/test/simple/first/FirstOperation</wsa:Action>
<wsa:MessageID xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:2ba3f950-9ab8-8759-1749-57cbe781cd1b</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>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing"
xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="true">MuseResource-1</muse-wsa:ResourceId>
</soap:Header>
<soap:Body>
<FirstOperation xmlns="http://ws.apache.org/muse/test/simple/first">Hello, World!</FirstOperation>
</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:160b9c61-df5e-be27-e3b0-c5f8ba9a2f88</wsa:MessageID>
<wsa:RelatesTo RelationshipType="wsa:Reply" xmlns:wsa="http://www.w3.org/2005/08/addressing">uuid:2ba3f950-9ab8-8759-1749-57cbe781cd1b</wsa:RelatesTo>
<wsa:From xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Address>http://127.0.0.1:8086/simple/services/SimpleResource</wsa:Address>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId wsa:IsReferenceParameter="true"
xmlns:muse-wsa="http://ws.apache.org/muse/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing">MuseResource-1</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</wsa:From>
</soap:Header>
<soap:Body>
<soap:Fault>
<soap:Code>
<soap:Value>soap:Sender</soap:Value>
<soap:Subcode xmlns:wsa="http://www.w3.org/2005/08/addressing">
<soap:Value>wsa:DestinationUnreachable</soap:Value>
</soap:Subcode>
</soap:Code>
<soap:Reason>
<soap:Text>[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:8086/simple/services/SimpleResource</wsa:Address>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing"
wsa:IsReferenceParameter="true" xmlns:wsa="http://www.w3.org/2005/08/addressing">MuseResource-1</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</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"/>
<wsa:Address>http://127.0.0.1:8086/simple/services/SimpleResource</wsa:Address>
</wsa:EndpointReference>
</soap:Text>
</soap:Reason>
</soap:Fault>
</soap:Body>
</soap:Envelope>

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:8086/simple/services/SimpleResource</wsa:Address>
<wsa:ReferenceParameters>
<muse-wsa:ResourceId
xmlns:muse-wsa="http://ws.apache.org/muse/addressing"
wsa:IsReferenceParameter="true" xmlns:wsa="http://www.w3.org/2005/08/addressing">MuseResource-1</muse-wsa:ResourceId>
</wsa:ReferenceParameters>
</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"/>
<wsa:Address>http://127.0.0.1:8086/simple/services/SimpleResource</wsa:Address>
</wsa:EndpointReference>
at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:298)
at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254)
at org.apache.muse.test.simple.SimpleResourceClient.firstOperation(SimpleResourceClient.java:67)
at org.apache.muse.test.simple.SimpleTestClient.main(SimpleTestClient.java:105)

Can anyone tell me what is wrong?

Thanks!

Sara

Re: Question of realizing Metric Capability

2009-04-14T06:45:00Z

Hi Sara,

what logs are produced? This kind of error usually implies that the
servlet hasn't started, there should be some log files to go with
this.

Regarding the simple metrics capability:

http://ws.apache.org/muse/docs/2.2.0/manual/capabilities/wsdm-metrics.html

and

http://www.ibm.com/developerworks/library/ac-musemetric/index.html

cheers,
Chris

On Tue, Apr 14, 2009 at 3:30 PM, SARA1232007 <cyl_axis@...> wrote:

>
> Hi,
>
> I've tried to realize a metric capability following the guidiance provided
> by muse refernce manual, but failed to do this.
>
> I have defined my metric in rmd file as following:
>
> <?xml version="1.0"?>
> <Definitions xmlns="http://docs.oasis-open.org/wsrf/rmd-1" >
>
> <MetadataDescriptor xmlns:wsrl="http://docs.oasis-open.org/wsrf/rl-2"
> xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd"
>
> xmlns:myns="http://www.30wish.com/muse/ManagementInterface"
> name="WsrMEPMBeanMetadata"
> interface="myns:WsrMEPMBeanPortType"
>
> wsdlLocation="http://www.30wish.com/muse/ManagementInterface
> WsrMEPMBean.wsdl" >
>
> <Property name="muws2:CurrentTime" modifiability="read-only"
> mutability="mutable" />
>
> 
>
> <Property name="myns:MEPMBeanMetrics" modifiability="read-only"
> mutability="mutable">
>
> <muws2:Capability>http://docs.oasis-open.org/wsdm/muws/capabilities/Metrics</muws2:Capability>
> <muws2:TimeScope>Interval</muws2:TimeScope>
> <muws2:GatheringTime>Periodic</muws2:GatheringTime>
> <muws2:CalculationInterval>1 Minute</muws2:CalculationInterval>
> </Property>
>
> </MetadataDescriptor>
>
> </Definitions>
>
> Also, my wsdl definition is as following:
>
> ... ...
> <wsdl:types>
> ... ...
> <xsd:schema
> elementFormDefault="qualified"
> targetNamespace="http://www.30wish.com/muse/ManagementInterface">
>
> <xsd:element name="MEPMBeanMetrics">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="Metrics" >
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="MaxProcessingTime" type="xsd:long" />
> <xsd:element name="AverageProcessingTime" type="xsd:long" />
> <xsd:element name="StartTime" type="xsd:date" />
> <xsd:element name="ResponseCount" type="xsd:long" />
> <xsd:element name="MinProcessingTime" type="xsd:long" />
> 
> <xsd:element name="TotalProcessingTime" type="xsd:long" />
> <xsd:element name="RequestCount" type="xsd:long" />
> <xsd:element name="FaultCount" type="xsd:long" />
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
>
> <xsd:element name="WsrMEPMBeanProperties">
> <xsd:complexType>
> <xsd:sequence>
> <xsd:element name="Identity" type="xsd:string" />
> <xsd:element xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd"
> ref="muws2:CurrentTime"/>
> <xsd:element ref="wsrf-rl:TerminationTime" />
> <xsd:element ref="wsrf-rp:QueryExpressionDialect" minOccurs="0"
> maxOccurs="unbounded"/>
> <xsd:element ref="tns:MEPMBeanMetrics"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
> </wsdl:types>
> ... ...
> <wsdl:service name="WsrMEPMBeanService">
> <wsdl:port name="WsrMEPMBeanPort" binding="tns:WsrMEPMBeanBinding">
> <wsdl-soap:address
> location="http://localhost:8086/ManagementService/WsrMEPMBean"/>
> </wsdl:port>
> </wsdl:service>
>
>
> My client code:
>
> URI address =
> "http://127.0.0.1:8086/ManagementService/WsrMEPMBean";
> EndpointReference epr = new EndpointReference(address);
>
> MetricsClient client = new MetricsClient(epr);
> client.setTrace(true);
> Map metrics = new HashMap();
>
> QName name = new QName(
> "http://www.30wish.com/muse/ManagementInterface",
> "MEPMBeanMetrics", "myns");
> String[] values = (String[])
> client.getPropertyAsObjectAndMetrics(
> name, String.class, metrics);
>
> System.out.println("The property values are: ");
>
> for (int n = 0; n < values.length; ++n)
> System.out.println(values[n]);
>
>
> I have deployed the war onto JBoss successfully. After I run client, I get
> trace information from client but there is no response information I get
> from the JBoss server. The information get I from client is following:
>
> [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://127.0.0.1:8086/ManagementService/WsrMEPMBean</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:6045ae9d-5edf-f156-489c-c2f8d2fe013a</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:wsrf-rp="http://docs.oasis-open.org/wsrf/rp-2"
> xmlns:myns="http://www.30wish.com/muse/ManagementInterface">myns:MEPMBeanMetrics</wsrf-rp:GetResourceProperty>
> </soap:Body>
> </soap:Envelope>
>
> [Fatal Error] :1:1025: The element type "HR" must be terminated by the
> matching end-tag "</HR>".
> org.apache.muse.ws.addressing.soap.SoapFault: The element type "HR" must be
> terminated by the matching end-tag "</HR>".
> at
> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:298)
> at
> org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254)
> at
> org.apache.muse.ws.resource.remote.WsResourceClient.getResourceProperty(WsResourceClient.java:138)
> at
> org.apache.muse.ws.dm.muws.remote.MetricsClient.getResourcePropertyAndMetrics(MetricsClient.java:103)
> at
> org.apache.muse.ws.dm.muws.remote.MetricsClient.getPropertyAsObjectAndMetrics(MetricsClient.java:84)
> at
> org.apache.muse.test.wsrServer.WsrServerClient.main(WsrServerClient.java:203)
>
> Also what needs to be mention is the muse.xml generated by wsdl file does
> not contain the metrics capability.
>
> Could anyone tell me what's wrong? Also, what should be done if I want to
> provide my own metrics capability implementation class?
>
> Any help is very much appreicated!
>
> Sara
> --
> View this message in context: http://www.nabble.com/Question-of-realizing-Metric-Capability-tp23039515p23039515.html
> Sent from the Muse - Dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: muse-dev-unsubscribe@...
> For additional commands, e-mail: muse-dev-help@...
>
>

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

Question of realizing Metric Capability

2009-04-14T06:30:49Z

Hi,

I've tried to realize a metric capability following the guidiance provided by muse refernce manual, but failed to do this.

I have defined my metric in rmd file as following:

<?xml version="1.0"?>
<Definitions xmlns="http://docs.oasis-open.org/wsrf/rmd-1" >

<MetadataDescriptor xmlns:wsrl="http://docs.oasis-open.org/wsrf/rl-2"
xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd"
xmlns:myns="http://www.30wish.com/muse/ManagementInterface" name="WsrMEPMBeanMetadata"
interface="myns:WsrMEPMBeanPortType"
wsdlLocation="http://www.30wish.com/muse/ManagementInterface WsrMEPMBean.wsdl" >

<Property name="muws2:CurrentTime" modifiability="read-only" mutability="mutable" />



<Property name="myns:MEPMBeanMetrics" modifiability="read-only" mutability="mutable">
<muws2:Capability>http://docs.oasis-open.org/wsdm/muws/capabilities/Metrics</muws2:Capability>
<muws2:TimeScope>Interval</muws2:TimeScope>
<muws2:GatheringTime>Periodic</muws2:GatheringTime>
<muws2:CalculationInterval>1 Minute</muws2:CalculationInterval>
</Property>

</MetadataDescriptor>

</Definitions>

Also, my wsdl definition is as following:

... ...
<wsdl:types>
... ...
<xsd:schema
elementFormDefault="qualified"
targetNamespace="http://www.30wish.com/muse/ManagementInterface">

<xsd:element name="MEPMBeanMetrics">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Metrics" >
<xsd:complexType>
<xsd:sequence>
<xsd:element name="MaxProcessingTime" type="xsd:long" />
<xsd:element name="AverageProcessingTime" type="xsd:long" />
<xsd:element name="StartTime" type="xsd:date" />
<xsd:element name="ResponseCount" type="xsd:long" />
<xsd:element name="MinProcessingTime" type="xsd:long" />

<xsd:element name="TotalProcessingTime" type="xsd:long" />
<xsd:element name="RequestCount" type="xsd:long" />
<xsd:element name="FaultCount" type="xsd:long" />
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

<xsd:element name="WsrMEPMBeanProperties">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Identity" type="xsd:string" />
<xsd:element xmlns:muws2="http://docs.oasis-open.org/wsdm/muws2-2.xsd" ref="muws2:CurrentTime"/>
<xsd:element ref="wsrf-rl:TerminationTime" />
<xsd:element ref="wsrf-rp:QueryExpressionDialect" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="tns:MEPMBeanMetrics"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
</wsdl:types>
... ...
<wsdl:service name="WsrMEPMBeanService">
<wsdl:port name="WsrMEPMBeanPort" binding="tns:WsrMEPMBeanBinding">
<wsdl-soap:address location="http://localhost:8086/ManagementService/WsrMEPMBean"/>
</wsdl:port>
</wsdl:service>

My client code:

URI address = "http://127.0.0.1:8086/ManagementService/WsrMEPMBean";
EndpointReference epr = new EndpointReference(address);

MetricsClient client = new MetricsClient(epr);
client.setTrace(true);
Map metrics = new HashMap();

QName name = new QName(
"http://www.30wish.com/muse/ManagementInterface",
"MEPMBeanMetrics", "myns");
String[] values = (String[]) client.getPropertyAsObjectAndMetrics(
name, String.class, metrics);

System.out.println("The property values are: ");

for (int n = 0; n < values.length; ++n)
System.out.println(values[n]);

I have deployed the war onto JBoss successfully. After I run client, I get trace information from client but there is no response information I get from the JBoss server. The information get I from client is following:

[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://127.0.0.1:8086/ManagementService/WsrMEPMBean</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:6045ae9d-5edf-f156-489c-c2f8d2fe013a</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:wsrf-rp="http://docs.oasis-open.org/wsrf/rp-2" xmlns:myns="http://www.30wish.com/muse/ManagementInterface">myns:MEPMBeanMetrics</wsrf-rp:GetResourceProperty>
</soap:Body>
</soap:Envelope>

[Fatal Error] :1:1025: The element type "HR" must be terminated by the matching end-tag "</HR>".
org.apache.muse.ws.addressing.soap.SoapFault: The element type "HR" must be terminated by the matching end-tag "</HR>".
at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:298)
at org.apache.muse.core.AbstractResourceClient.invoke(AbstractResourceClient.java:254)
at org.apache.muse.ws.resource.remote.WsResourceClient.getResourceProperty(WsResourceClient.java:138)
at org.apache.muse.ws.dm.muws.remote.MetricsClient.getResourcePropertyAndMetrics(MetricsClient.java:103)
at org.apache.muse.ws.dm.muws.remote.MetricsClient.getPropertyAsObjectAndMetrics(MetricsClient.java:84)
at org.apache.muse.test.wsrServer.WsrServerClient.main(WsrServerClient.java:203)

Also what needs to be mention is the muse.xml generated by wsdl file does not contain the metrics capability.

Could anyone tell me what's wrong? Also, what should be done if I want to provide my own metrics capability implementation class?

Any help is very much appreicated!

Sara

[jira] Created: (MUSE-302) WS-MEX capability implementation class should default to WsrfMetadataExchange when RMD file specified.

2009-04-14T05:42:14Z

WS-MEX capability implementation class should default to WsrfMetadataExchange when RMD file specified.
------------------------------------------------------------------------------------------------------

Key: MUSE-302
URL: https://issues.apache.org/jira/browse/MUSE-302
Project: Muse
Issue Type: Bug
Components: Tooling - Code Generation
Affects Versions: 2.2.0
Environment: latest SVN trunk to data
Reporter: Jonas Buys
Assignee: Dan Jemiolo

When running WSDL2JAVA on a WSDL and RMD file that contain all the necessary XML for WS-MetadataExchange, in the generated muse.xml file the default MUSE class org.apache.muse.ws.metadata.impl.SimpleMetadataExchange is specified as implementation class for WS-MEX. This is sufficient in the case there is a WSDL without an RMD file.

The side effect is that, when invoking getRMD() on your WsrfMetadataExchangeClient proxy object, the SOAP message will return an EMPTY metadata response. The issue can be resolved by manually setting the MUSE class org.apache.muse.ws.resource.metadata.ext.WsrfMetadataExchange as implemantation class for the MEX capability.

An easy way to fix this issue is to modify org.apache.muse.tools.generator.analyzer.SimpleAnalyzer, by inserting the WsrfMetadataExchange class at line 106 in the _internalImplMap instead of the default SimpleMetadataExchange. Or it can of course also be done manually.

A better solution would be for the generator tool to check whether an RMD file is specified, and if so, use the WsrfMetadataExchange instead of the SimpleMetadataExchange class.

--
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@...