[
https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614305#action_12614305
]
Eduard Hildebrandt commented on CXF-1701:
-----------------------------------------
I created this issue primary because it is very irritating having valid
(according to XML schema) configuration elements which do nothing. Maybe these
configuration elements should be removed from XML schema for WSDL (not for
Spring configuration). At least this behaviour should be documented in Wiki.
However one of my customers is planning to use a service registry. The registry
keeps the abstract part of the WSDL static and generates the concrete part
(ports, endpoint, ...) dynamically based on the query (or requester). For this
reason it could be interesting having the possibility to configure the endpoint
including client, server and session pool.
> JMS Transport Configuration in a WSDL file is not parsed
> --------------------------------------------------------
>
> Key: CXF-1701
> URL: https://issues.apache.org/jira/browse/CXF-1701
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.1.1
> Reporter: Eduard Hildebrandt
> Attachments: patch.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> JMS Transport Configuration in a WSDL file is not parsed correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
