[prev in list] [next in list] [prev in thread] [next in thread] 

List:       muse-dev
Subject:    [jira] Commented: (MUSE-85) WSDM Test File
From:       "Dan Jemiolo (JIRA)" <jira () apache ! org>
Date:       2006-08-30 23:00:23
Message-ID: 33473589.1156978823847.JavaMail.jira () brutus
[Download RAW message or body]

    [ http://issues.apache.org/jira/browse/MUSE-85?page=comments#action_12431740 ] 
            
Dan Jemiolo commented on MUSE-85:
---------------------------------

Caption, Version, ResourceId are the property names - a capability may have [0..n] \
properties, all under one namespace. As an example, there's nothing (normative) in \
the WSDM XSD that says ResourceId belongs to the Identity capability, which we could \
use to in deciding to name a file Identity.java.

Also, for any standard capabilities, the generator will rely on our default \
implementations of those (see muse.xml for the hook up of capabilities to impl \
classes) rather than re-generating them. If you want to replace the default impls, \
you'd just have to extend or replace the class with one of your own. As an example, \
if you wanted to replace org.apache.muse.ws.dm.muws.impl.SimpleIdentity (which \
implements org.apache.muse.ws.dm.muws.Identity), you'd just write your own class that \
implements  org.apache.muse.ws.dm.muws.Identity.

To see this in action, try adding a custom property/operation that is not defined in \
WS-* - the tool should generate code for that.

> WSDM Test File
> --------------
> 
> Key: MUSE-85
> URL: http://issues.apache.org/jira/browse/MUSE-85
> Project: Muse
> Issue Type: Test
> Components: Other
> Affects Versions: 2.0.0
> Reporter: Steve Jerman
> Assigned To: Dan Jemiolo
> Attachments: MyCapabilityImpl.java, TestFile.zip, WSDM-POC-Model.gif
> 
> 
> OK, attached isa diagram which shows the model I am trying to create WSDM \
> interfaces for. Also attached is a Zip file with a set of WSDLs. Basically I \
> started with some generated XSD/WSDL and then decided that I should hand code a \
> proto that validated correct and did the right stuff and use that as pattern. The \
> system.wsdl file was the result. I *think* it should create a simple WSDM resource \
> implementation with getResourcePropertyDocument and getResourceProperty operations. \
> It sort of looks like thats the case. A few questions.
> What would some code look like that could handle multiple instances of System. Do I \
> need to do anything different? Surely the Java interfaces generated are for the \
> ManagedResource? They don't seem to be Capapability implementations. Looks like the \
> name of the Java files is hard coded. Is there a better way to handle this? I would \
> like to get this sample up and runing first and then expand out to the rest of my \
> model (and all the configuration I have in mind). Steve

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: \
                http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[prev in list] [next in list] [prev in thread] [next in thread]