You are viewing a plain text version of this content. The canonical link for it is here.

Posted to muse-dev@ws.apache.org by "Dan Jemiolo (JIRA)" <ji...@apache.org> on 2007/03/17 19:18:09 UTC

[jira] Updated: (MUSE-209) Create documentation for WebSphere 6.x platform (uses WSDL4J 1.4)

     [ https://issues.apache.org/jira/browse/MUSE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Jemiolo updated MUSE-209:
-----------------------------

      Component/s:     (was: Build - Maven, Dependencies, and Optimizations)
                   Documentation - Manual
    Fix Version/s:     (was: 2.3.0)
                   2.2.0
          Summary: Create documentation for WebSphere 6.x platform (uses WSDL4J 1.4)  (was: Create new module for WebSphere 6.x platform (uses WSDL4J 1.4))

Our users have provided helpful workarounds on the mailing list by using the WAS admin console/config settings. We should make a how-to for this rather than requiring a completely separate module.

> Create documentation for WebSphere 6.x platform (uses WSDL4J 1.4)
> -----------------------------------------------------------------
>
>                 Key: MUSE-209
>                 URL: https://issues.apache.org/jira/browse/MUSE-209
>             Project: Muse
>          Issue Type: Bug
>          Components: Documentation - Manual
>    Affects Versions: 2.2.0
>         Environment: WebSphere 6.0 or 6.1, with Axis2 or Mini
>            Reporter: Dan Jemiolo
>         Assigned To: Dan Jemiolo
>             Fix For: 2.2.0
>
>
> IBM's WebSphere server includes WSDL4J 1.4, and Muse relies on WSDL4J 1.5 or higher. We need to use 1.5+ because it includes an API for retrieving non-WSDL attributes from the operation/message elements, and this is how we retrieve the wsa:Action URIs from the WSDL. Without this API, we have to use a DOM representation of the WSDL (not the WSDL4J objects) to look for the operation elements and extract the Action URIs with getAttribute( ). This DOM duplicates the WSDL4J model we already have, which is wasteful.
> For WAS, the module will be a one-off that uses DOM to read the WSDL instead of WSDL4J. We already have this code for 2.0, but it will need to be upgraded slightly for 2.2+.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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