[ 
http://issues.apache.org/jira/browse/MUSE-35?page=comments#action_12420178 ] 

Dan Jemiolo commented on MUSE-35:
---------------------------------

The solution above would work, however it also introduces a dependency on the 
WS-MEx module (muse-wsx) and the tools module (muse-tools). The getWSDL() 
method is actually a convenience method in the WS-MEx client, and the 
ResourceInspector is in muse-tools. I don't think adding these compilation 
dependencies is worth one convenience method, especially when the method is 
only 3-4 lines long.

As the tooling component grows, we may need to factor out the inspector into 
its own JAR, since it is relatively small and useful in other, non-generation 
scenarios. I think we should point people to the resource inspector for this 
task, and if/when the muse-tools JAR grows too large, we will factor it out.


> Add a getPropertyNames( ) to the WsResourceClient
> -------------------------------------------------
>
>          Key: MUSE-35
>          URL: http://issues.apache.org/jira/browse/MUSE-35
>      Project: Muse
>         Type: New Feature

>  Environment: Axis2 and OSGi
>     Reporter: Dan Jemiolo
>     Priority: Minor

>
> The WsResourceClient should use the introspection tool (ResourceInspector) to 
> find all of the property names in a WSDL and return them as a collection (or 
> array) to the user. The implementation of the method could look like this 
> (pseudo-code):
> Collection getPropertyNames( )
> {
>      Element wsdl = getWSDL();
>      ResourceInspector inspector = new ResourceInspector();
>      inspector.run(wsdl);
>      return inspector.getPropertyNames();
> }
> This feature would be very useful for dynamic clients that do not know ahead 
> of time what resource types they will be interacting with.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to