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

List:       xmlrpc-dev
Subject:    [jira] [Commented] (WODEN-20) Component model API needs modifiers
From:       "Hudson (Commented) (JIRA)" <jira () apache ! org>
Date:       2012-01-21 16:09:40
Message-ID: 1929882805.63418.1327162180625.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/WODEN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190451#comment-13190451 \
] 

Hudson commented on WODEN-20:
-----------------------------

Integrated in woden-trunk #538 (See [https://builds.apache.org/job/woden-trunk/538/])
    Merged woden-20 changes from woden-20 branch.

                
> Component model API needs modifiers
> -----------------------------------
> 
> Key: WODEN-20
> URL: https://issues.apache.org/jira/browse/WODEN-20
> Project: Woden
> Issue Type: New Feature
> Components: Parser
> Reporter: Jeremy Hughes
> Assignee: Dilshan Edirisuriya
> Labels: gsoc, gsoc2010
> Attachments: EditablePackage.patch, WodenProposal_Dilshan.pdf, woden-api.patch, \
> woden-commons.patch 
> 
> A Woden 'client' - eg a tool such as java2wsdl - might want to:
> 1 introspect a tree of java classes / interfaces
> 2 create an org.apache.woden.wsdl20.Interface for each - adding to the Description \
> object along the way 3 serialize to disk.
> Today it is only possible to modify the object form of the WSDL through the Element \
> model API. This requires the client app to understand WSDL at the file level. For \
> step 2 addInterface() is required on Description. Of course \
> Interface.addInterfaceOperation() is then required and so on... For step 3 a \
> 'strategy' is needed to map from the Component model to the Element model's \
> representation of the WSDL in file form. e.g. do all the <interface> elements go in \
> the same WSDL file or do all the <interface> elements in the same namespace go in \
> one file etc. Also, do the <service> elements go in separately included/imported \
> WSDL files as is typically the best practice with WSDL 1.1. All these options could \
> be represented using a strategy pattern. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        

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


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