cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-2131) WSDL generation
Date Sun, 01 Nov 2009 14:20:59 GMT

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

Benson Margulies resolved CXF-2131.
-----------------------------------

    Resolution: Invalid

This is somewhere between 'works as designed' and 'talk to JAXB'. JAXB is making these decisions.
I believe that it has customization options you could use to trim.


> WSDL generation
> ---------------
>
>                 Key: CXF-2131
>                 URL: https://issues.apache.org/jira/browse/CXF-2131
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.1.4
>         Environment: JBoss, Windows XP
>            Reporter: Yogesh
>
> I am using code first approach to develop webservices. When I see generated WSDL after
hitting the service URL + '?wsdl', I see that all the type declarations done in XSD are getting
included in WSDL/Types element. Though I am just using 2 or 3 elements of XSD, it includes
all the elements. I am using JAXB to generate value objects from XSD. Is there any way to
restrict the elements to be include in WSDL/types to just objects used in Webservices and
not whole XSD.
> The problem could be worse If  I have 100s of webservices and all of them are using same
XSD. All 100 autogenerated WSDL file will include XSD declarations of all the elements which
will make WSDL bulkier, though each webservice is just using one or two elements.

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


Mime
View raw message