You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org> on 2009/01/15 12:18:00 UTC

[jira] Created: (QPID-1577) Use JAXB in order to dynamically create / populate wsdl:types/xsd:schema section for complex types.

Use JAXB in order to dynamically create / populate wsdl:types/xsd:schema section for complex types.
---------------------------------------------------------------------------------------------------

                 Key: QPID-1577
                 URL: https://issues.apache.org/jira/browse/QPID-1577
             Project: Qpid
          Issue Type: Sub-task
          Components: Java Management : QMan
    Affects Versions: M5
         Environment: J2SE 1.5 or higher
            Reporter: Andrea Gazzarini
            Assignee: Andrea Gazzarini
            Priority: Minor
             Fix For: M5


When a new object instance is created on Qpid side, QMan receives content indication message about that.
On its side this is what happens:

- JMX core creates and register a new MBean for that instance; 
- WSDM Adapter creates a WS resource including WSDL and the corresponding capability.

If the incoming object instance has some complex property (i.e. Map or UUID) the WSDLBuilder, which is the component responsible to build wsdl for the resource, uses hard-coded statements in order to define schema section of wsdl.

Improvement should made in order to do that using automatic schema generation feature of JAXB API.

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


[jira] Resolved: (QPID-1577) Use JAXB in order to dynamically create / populate wsdl:types/xsd:schema section for complex types.

Posted by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Gazzarini resolved QPID-1577.
------------------------------------

    Resolution: Later

move to M6

> Use JAXB in order to dynamically create / populate wsdl:types/xsd:schema section for complex types.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: QPID-1577
>                 URL: https://issues.apache.org/jira/browse/QPID-1577
>             Project: Qpid
>          Issue Type: Sub-task
>          Components: Java Management : QMan
>    Affects Versions: M5
>         Environment: J2SE 1.5 or higher
>            Reporter: Andrea Gazzarini
>            Assignee: Andrea Gazzarini
>            Priority: Minor
>             Fix For: M5
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When a new object instance is created on Qpid side, QMan receives content indication message about that.
> On its side this is what happens:
> - JMX core creates and register a new MBean for that instance; 
> - WSDM Adapter creates a WS resource including WSDL and the corresponding capability.
> If the incoming object instance has some complex property (i.e. Map or UUID) the WSDLBuilder, which is the component responsible to build wsdl for the resource, uses hard-coded statements in order to define schema section of wsdl.
> Improvement should made in order to do that using automatic schema generation feature of JAXB API.

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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


[jira] Updated: (QPID-1577) Use JAXB in order to dynamically create / populate wsdl:types/xsd:schema section for complex types.

Posted by "Andrea Gazzarini (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Gazzarini updated QPID-1577:
-----------------------------------


The current implementation of WSDL Builder is not good...it contains hard-coded mappings between Java and XML types...
The optimal things should be to do those things using JAXB but javax.xml.bind API have been incorporated only since JDK 1.6 and QMan is supposed to be 1.5 or higher compatible. I f we want to use the JAXB libs on JDK1.5 we should add additional dependencies :(

> Use JAXB in order to dynamically create / populate wsdl:types/xsd:schema section for complex types.
> ---------------------------------------------------------------------------------------------------
>
>                 Key: QPID-1577
>                 URL: https://issues.apache.org/jira/browse/QPID-1577
>             Project: Qpid
>          Issue Type: Sub-task
>          Components: Java Management : QMan
>    Affects Versions: M5
>         Environment: J2SE 1.5 or higher
>            Reporter: Andrea Gazzarini
>            Assignee: Andrea Gazzarini
>            Priority: Minor
>             Fix For: M5
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> When a new object instance is created on Qpid side, QMan receives content indication message about that.
> On its side this is what happens:
> - JMX core creates and register a new MBean for that instance; 
> - WSDM Adapter creates a WS resource including WSDL and the corresponding capability.
> If the incoming object instance has some complex property (i.e. Map or UUID) the WSDLBuilder, which is the component responsible to build wsdl for the resource, uses hard-coded statements in order to define schema section of wsdl.
> Improvement should made in order to do that using automatic schema generation feature of JAXB API.

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


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org