| RE: [cosmos-dev] questions on new annotation code |
|
|
Glad to hear it! I think your suggestion of a totally bogus endpoint request is a good one. As for the need to start up muse, if we want advertisements to be sent when the resource is first available we need something like this. The problem is that the isolation layer makes the resource router, and for most containers this happens on first request, so muse won’t create any resources until somebody asks for one. Chicken, meet Egg.
The reason that the OSGI-INF version has a relationship and the subscription manager implementations specified is because I’ve got relationship-specific annotations (the @ManagedRelationship stuff) and metric/event annotations (@ManagedMetric, @ManagedEvent stuff), and the implementation just shells out the relationship and subscription manager implementations contained by muse.xml. If you’re not using these annotations you can certainly get away with removing the relationship implementation – I need to check the property notification implementation in muse to see if it’s depending on a subscription manager being available (I’m pretty sure it is…)
If you’re happy with the ME code I’ll go ahead and commit it.
Cheers,
Joel
-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx]
On Behalf Of Hubert H Leung
Sent: Tuesday, January 29, 2008 11:58 PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] questions on new annontation code
Hi Joel,
I solved the problem. I have got the example MDR running on Tomcat!
The problem was that I actually have a Relationships resource specified
in the muse.xml. It was ported from the muse.xml in OSGI-INF directory
of org.eclipse.cosmos.me.management.wsdm. This is also a SubscriptionManager
resource specified in that muse.xml. In the OSGi environment, the
endpoint is not available when you try to start up muse, you always get
a endoint unreachable fault when you ping the endpoint.
Here are my suggestions:
1. Investigate whether we need to "start up muse" in J2EE environment.
2. If we still need to start up muse, and the right way to do it is to
ping muse with an invalid EPR, I suggest changing the URI to a very unlikely
name:
String contextPath = webAppRoot
+ "/services/Relationships";
Change to ===>
String contextPath = webAppRoot
+ "/services/abcd";
3. Revisit the muse.xml for OSGi. Do we need the two resources (Relationships
and SubscriptionManager) specified in the muse.xml? I removed both
of them for my web app.
Are you going to check in the patch for the ME code in CVS soon? I
will need these fixes in order to switch the cosmos code to use the new
ME code.
Thanks,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
| "Hawkins, Joel"
<Joel.Hawkins@xxxxxxxxxxxxx> Sent by: cosmos-dev-bounces@xxxxxxxxxxx 01/29/2008 07:22 PM
|
|
That warmup request is just to start muse up so that the advertisements
can go out. The request is expected to fail, and is expected to be unreachable.
Apparently you actually HAVE a service group?
Can you attach your muse.xml and web.xml to 209980? While your at it, can
you put the whole web application up there?
Thanks,
Joel
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev