Code is checked in under
215123.
Joel
-----Original Message-----
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hubert H Leung
Sent: Wednesday, January 30, 2008
9:58 AM
To: Cosmos Dev
Subject: RE: [cosmos-dev] RE:
CMDBf service data in WSDL 215123
Hi Bill,
I
have migrated the data manager code to use the new annotations (cosmos.me*). It's
using a newer version of the annotation code than what's in CVS. So Joel
will need to check in his changes too. I will check in the code after the
architecture call, just to make sure we have a good integration build. My
checkins will cause the build to break. I will open a bug for Jagmit to
update the build.
The
migration to the new annotation code is not complete. I have only tested
the query API so far. But I can check in the code now to support
incremental check in approach.
Regards,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
"Muldoon, William H"
<William.Muldoon@xxxxxx>
Sent
by: cosmos-dev-bounces@xxxxxxxxxxx
01/30/2008 09:30 AM
Please
respond to
Cosmos Dev <cosmos-dev@xxxxxxxxxxx>
|
|
To
|
"Cosmos Dev"
<cosmos-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
RE: [cosmos-dev] RE: CMDBf service data in
WSDL 215123
|
|
Joel
I’m using the
ExampleMDR, which is built using the IDataManager interface.
I think the problem
is that our Data Managers are still using the “old” annotations (in
cosmos.dc.*) while the new policy provider capability requires the
“new” annotations (in cosmos.me.*). So we need to convert to the
new annotations and deprecate the old annotations, correct? If so, do you
already have code “pending check-in” for this conversion?
Regards
Bill
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent: Tuesday, January 29, 2008 5:25 PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] RE: CMDBf service data in WSDL 215123
Bill,
Look at the test case for policy. You need to implement that
policy provider interface on one of your capabilities. Is the cmdbf code
checked in? I can take a look at your resource implementation to see what
you’ve got.
Cheers,
Joel
-----Original
Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of Muldoon, William H
Sent: Tuesday, January 29, 2008 5:06 PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] RE: CMDBf service data in WSDL 215123
Joel
I’ve setup
the ExampleMDR with the new metadata interface under OSGI. The client code is
simply:
MetadataExchangeClient
mex = new
MetadataExchangeClient(eprDataManager);
Element result = mex.getWSDL();
WSDL is returned
(see attachment) but it doesn’t include the metadata. I see this on the
example mdr osgi console (so I reached the server side):
osgi>
SOAP:<?xml version="1.0" encoding="UTF-8"?>
<wsx:GetMetadata
xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex">
<wsx:Dialect>http://schemas.xmlsoap.org/wsdl/</wsx:Dialect>
</wsx:GetMetadata>
But the new code in
your patch is never reached. Any ideas why?
Regards
Bill
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent: Tuesday, January 29, 2008 11:17 AM
To: Cosmos Dev
Subject: RE: [cosmos-dev] RE: CMDBf service data in WSDL 215123
Bill,
JAX-WS allows you to specify a wsdl location in the
webservice annotation, and I’m guessing that this is used by the JAX-WS
implementation to sew up the location in order to respond to a ?wsdl call, or
whatever mechanism the JAX-WS implementation chooses to expose. I think our
stance should be that the client retrieves the wsdl in a container-specific
way, as the spec takes no stance on the matter.
The rest of the design looks good – now I need to check
that I’m actually able to deliver the wsdl to Axis2! ;-)
Cheers,
Joel
-----Original
Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of Muldoon, William H
Sent: Monday, January 28, 2008 5:35 PM
To: Cosmos Dev
Subject: RE: [cosmos-dev] RE: CMDBf service data in WSDL 215123
Joel
I’ve updated
the design page at http://wiki.eclipse.org/COSMOS_Design_215123. Please review that it matches your patch. I wasn’t sure
about WSDL in JAX-WS so I left it as an open issue.
Thanks
Bill
From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Hawkins, Joel
Sent: Monday, January 28, 2008 8:12 AM
To: Muldoon, William H
Cc: Cosmos Dev
Subject: [cosmos-dev] RE: CMDBf service data in WSDL 215123
Hey Bill – sure, patch is attached:
You can look at the fixtures for the test case to see how to
use it. If you’re happy with it, we’ll commit it as soon as i9
opens.
Cheers,
Joel
-----Original
Message-----
From: Muldoon, William H [mailto:William.Muldoon@xxxxxx]
Sent: Friday, January 25, 2008 5:01 PM
To: Hawkins, Joel
Subject: RE: CMDBf service data in WSDL 215123
Joel
I think
you’re right. Better wait until the i8 build is officially blessed.
Meanwhile if
it’s not too much trouble, can you send me a patch?
Thanks
Bill
From: Hawkins, Joel
[mailto:Joel.Hawkins@xxxxxxxxxxxxx]
Sent: Friday, January 25, 2008 4:43 PM
To: Muldoon, William H
Subject: RE: CMDBf service data in WSDL 215123
Is it OK to check stuff in? I was holding out until i8 was
out the door…
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.
From: Muldoon, William H [mailto:William.Muldoon@xxxxxx]
Sent: Friday, January 25, 2008 4:08 PM
To: Hawkins, Joel
Subject: CMDBf service data in WSDL 215123
Hi Joel
Have you
made any progress with the IPolicyAssertion support in the Contribution
Manager
that was discussed for https://bugs.eclipse.org/bugs/show_bug.cgi?id=215123?
If not, I
can make the changes (just point me in the
right direction in the code).
Regards
Bill
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev