WS-DM Examples

2009-01-25 Thread Andrea Gazzarini
Hi all,
I added an example source folder (not yet committed).
I think that it should be better to release this folder as is, without
binaries.
Reason is that you don't need to effectively run this examples because :

- Unit test already do that;
- They must run in a predefined context (Qpid must up and running, QMan
too);
- User would simply have a look about how to do something (with code); About
that point on source code there's (between examples) a lot of code
duplication. This is due to the fact that the example should be IMO
immediately clear and I tried to isolate code that is not related with the
core of the example. You can find what I mean (when I will submit :) ) in
the executeExample of each class.
- Examples are written in Java so they are reporting how a Java client
connects to WS-DM. What is important is IMO is to describe the exchanged
messages (SOAP request  response) that are needed to conversate with WS-DM.
For that reason I will include, together with the examples, a set of xml
files that contains WS-DM conversations.

Anyway , if the use wants to run the example this will be possible. An
opportune README (or wiki howto) will be included and the example will
articulate in the following way.

* java  example_class host port*

 GetQManResourceMembersExample
---

This example shows the usage of WS-DM
GetResourcePropertyRequest / Response on a
Group service.
The target resource is the WS-DM Adapter itself
and the requested property is ws-rp:Entry.
WS-DM Adapter is a special WS-Resource (is a Group)
that  acts as the main entry point for retrieving
all other managed resources.
So clients that want to deal with QMan WS-Resources
must first get resource identifiers sending
a GetResourcePropertyRequest to WS-DM Adapter
with ws-rp:Entry as target target property.

---

Type enter to proceed...

[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://romagazzarini:8080/qman/services/adapter/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:024c678b-1fab-cb6a-0992-30027817fb92/wsa:MessageID
wsa:From xmlns:wsa=http://www.w3.org/2005/08/addressing;
wsa:Addresshttp://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:wsrf-sg=http://docs.oasis-open.org/wsrf/sg-2
wsrf-sg:Entry/wsrf-rp:GetResourceProperty
/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://docs.oasis-open.org/wsrf/rpw-2/GetResourceProperty/GetResourcePropertyResponse
/wsa:Action
wsa:MessageID xmlns:wsa=http://www.w3.org/2005/08/addressing
uuid:62f50bef-269a-7a52-712a-3196dc78d37a/wsa:MessageID
wsa:RelatesTo RelationshipType=wsa:Reply xmlns:wsa=
http://www.w3.org/2005/08/addressing
uuid:11c98e8b-1420-96fa-809b-89d64ce908eb/wsa:RelatesTo
wsa:From xmlns:wsa=http://www.w3.org/2005/08/addressing;
wsa:Addresshttp://localhost:8080/qman/services/adapter
/wsa:Address
/wsa:From
/soap:Header
soap:Body
wsrf-rp:GetResourcePropertyResponse xmlns:wsrf-rp=
http://docs.oasis-open.org/wsrf/rp-2;
wsrf-sg:Entry xmlns:wsrf-sg=
http://docs.oasis-open.org/wsrf/sg-2;
wsrf-sg:ServiceGroupEntryEPR
wsa:Address xmlns:wsa=
http://www.w3.org/2005/08/addressing;
http://localhost:8080/qman/services/ServiceGroupEntry/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
uuid:44bb636c-0cbf-97e2-fb16-976b357f2d7f/muse-wsa:ResourceId
/wsa:ReferenceParameters
/wsrf-sg:ServiceGroupEntryEPR
wsrf-sg:MemberServiceEPR
wsa:Address xmlns:wsa=
http://www.w3.org/2005/08/addressing;
http://localhost:8080/qman/services/QManWsResource/wsa:Address
wsa:ReferenceParameters xmlns:wsa=
http://www.w3.org/2005/08/addressing;
qman-wsa:ResourceId xmlns:qman-wsa=
http://amqp.apache.org/qpid/management/qman/addressing;Q-MAN:

Additional Qpid C++ on Windows content

2009-01-25 Thread Cliff Jansen (Interop Systems Inc)
Hi all,

Windows is a newly supported C++ platform in M4 and we are beginning
to see some early adopters having difficulty.

May I suggest a Windows area on qpid.apache.org with:

  - more elaborate install and run doc
  - clear info on differences compared to the Linux implementation
   i.e. X has been ported in M4, Y will be in the future
  - this (growing) list of tests/samples is known to work
  - binaries, 32 and 64 bit
  - possibly previewing an M5-style installer
  - backported M5 bug fixes for Windows (like QPID-1550 when available)
  - a few more Visual Studio build scripts for samples or tests

Let me know if this would be useful.

I would propose to do the lion's share on this with some Jiras and
associated patches.  Also, some of this can be staged or mirrored at a
Microsoft public location if that's helpful or more appropriate.

Cliff