You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Gyorgy Orban (JIRA)" <ji...@apache.org> on 2007/11/06 17:26:51 UTC

[jira] Created: (CXF-1181) Dynamic client

Dynamic client
--------------

                 Key: CXF-1181
                 URL: https://issues.apache.org/jira/browse/CXF-1181
             Project: CXF
          Issue Type: Improvement
          Components: Core
            Reporter: Gyorgy Orban


As we see CXF on the client side uses a static client. By static client, we mean that during service invocation at runtime it uses both the WSDL and the interface generated from the service. We are planning to implement a client that uses only the WSDL to call a service. Using this dynamic client, we would also implement  a client side STAX interface, where the application programmer can pass and get back STAX streams  (or callbacks)  directly to the operations. 
Do you think these ideas make sense to the public as well? If so, we would be happy to contribute these extensions to CXF. Do you have any similar plans or suggestions?
Thanks,
Gyorgy

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

[jira] Resolved: (CXF-1181) Dynamic client

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

Benson Margulies resolved CXF-1181.
-----------------------------------

    Resolution: Invalid

I suggested that the submitted of this discuss the idea on cxf-dev, instead.


> Dynamic client
> --------------
>
>                 Key: CXF-1181
>                 URL: https://issues.apache.org/jira/browse/CXF-1181
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Gyorgy Orban
>
> As we see CXF on the client side uses a static client. By static client, we mean that during service invocation at runtime it uses both the WSDL and the interface generated from the service. We are planning to implement a client that uses only the WSDL to call a service. Using this dynamic client, we would also implement  a client side STAX interface, where the application programmer can pass and get back STAX streams  (or callbacks)  directly to the operations. 
> Do you think these ideas make sense to the public as well? If so, we would be happy to contribute these extensions to CXF. Do you have any similar plans or suggestions?
> Thanks,
> Gyorgy

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

[jira] Commented: (CXF-1181) Dynamic client

Posted by "Glen Mazza (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552036 ] 

Glen Mazza commented on CXF-1181:
---------------------------------

I think we already have this, no?  http://cwiki.apache.org/CXF20DOC/dynamic-clients.html


> Dynamic client
> --------------
>
>                 Key: CXF-1181
>                 URL: https://issues.apache.org/jira/browse/CXF-1181
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Gyorgy Orban
>
> As we see CXF on the client side uses a static client. By static client, we mean that during service invocation at runtime it uses both the WSDL and the interface generated from the service. We are planning to implement a client that uses only the WSDL to call a service. Using this dynamic client, we would also implement  a client side STAX interface, where the application programmer can pass and get back STAX streams  (or callbacks)  directly to the operations. 
> Do you think these ideas make sense to the public as well? If so, we would be happy to contribute these extensions to CXF. Do you have any similar plans or suggestions?
> Thanks,
> Gyorgy

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

[jira] Commented: (CXF-1181) Dynamic client

Posted by "Benson Margulies (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CXF-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552015 ] 

Benson Margulies commented on CXF-1181:
---------------------------------------

Gyorgy,

Please join the cxf-dev mailing list and send in a more detailed concept of what you are proposing. It seems reasonable, but a JIRA is not a good forum for a discussion with the committers.



> Dynamic client
> --------------
>
>                 Key: CXF-1181
>                 URL: https://issues.apache.org/jira/browse/CXF-1181
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Gyorgy Orban
>
> As we see CXF on the client side uses a static client. By static client, we mean that during service invocation at runtime it uses both the WSDL and the interface generated from the service. We are planning to implement a client that uses only the WSDL to call a service. Using this dynamic client, we would also implement  a client side STAX interface, where the application programmer can pass and get back STAX streams  (or callbacks)  directly to the operations. 
> Do you think these ideas make sense to the public as well? If so, we would be happy to contribute these extensions to CXF. Do you have any similar plans or suggestions?
> Thanks,
> Gyorgy

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