You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Eduard Hildebrandt (JIRA)" <ji...@apache.org> on 2008/07/15 16:49:32 UTC

[jira] Created: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

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

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.


[jira] Resolved: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ulhas Bhole resolved CXF-1701.
------------------------------

    Resolution: Fixed

> 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
>            Assignee: Ulhas Bhole
>         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.


[jira] Updated: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Eduard Hildebrandt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eduard Hildebrandt updated CXF-1701:
------------------------------------

    Attachment: patch.txt

Please consider apply attached patch.

> 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
>
>
> 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.


[jira] Updated: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ulhas Bhole updated CXF-1701:
-----------------------------

    Remaining Estimate: 0h
     Original Estimate: 0h

This behaviour is intentional. Client, Server and Session Pool configuration are specific to each instance so they are excluded from WSDL extensor  and added to CXF configuration.

Can you explain more why you need them via WSDL?
 

> 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.


[jira] Commented: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616410#action_12616410 ] 

Ulhas Bhole commented on CXF-1701:
----------------------------------

Sending        .
Sending        rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/JMSProviderHub.java
Sending        rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/JMSTransportBase.java
Sending        rt/transports/jms/src/main/resources/META-INF/cxf/extensions.xml
Sending        rt/transports/jms/src/main/resources/schemas/wsdl/jms.xsd
Sending        systests/src/test/java/org/apache/cxf/systest/jms/GreeterByteMessageImpl.java
Sending        systests/src/test/java/org/apache/cxf/systest/jms/GreeterImplDoc.java
Adding         systests/src/test/java/org/apache/cxf/systest/jms/GreeterImplDocBase.java
Sending        systests/src/test/java/org/apache/cxf/systest/jms/GreeterImplTwoWayJMS.java
Sending        systests/src/test/java/org/apache/cxf/systest/jms/JMSClientServerTest.java
Adding         systests/src/test/java/org/apache/cxf/systest/jms/JmsDestPubSubImpl.java
Sending        systests/src/test/java/org/apache/cxf/systest/jms/Server.java
Adding         systests/src/test/java/org/apache/cxf/systest/jms/SoapService6SoapPort6Impl.java
Adding         systests/src/test/java/org/apache/cxf/systest/jms/TwoWayJMSImplBase.java
Sending        testutils/src/main/resources/wsdl/hello_world_doc_lit.wsdl
Sending        testutils/src/main/resources/wsdl/jms_test.wsdl
Transmitting file data ...........
Committed revision 679316.

> 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
>            Assignee: Ulhas Bhole
>         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.


[jira] Commented: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Eduard Hildebrandt (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Commented: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614308#action_12614308 ] 

Daniel Kulp commented on CXF-1701:
----------------------------------


For 2.2, we've discussed enhancing the JMS transport to support the proposed spec:
http://www.w3.org/Submission/SOAPJMS/
and all the timeToLive, timeouts, etc... would be in the wsdl there as well.    Thus, I don't really see a reason not to do this.

> 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.


[jira] Assigned: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

Posted by "Ulhas Bhole (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ulhas Bhole reassigned CXF-1701:
--------------------------------

    Assignee: Ulhas Bhole

> 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
>            Assignee: Ulhas Bhole
>         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.