geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4664) OpenSSO Deployment fails with "WSDL generation failed"
Date Tue, 02 Jun 2009 21:17:07 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715692#action_12715692
] 

Jarek Gawor commented on GERONIMO-4664:
---------------------------------------

To deploy this way set the following property before starting the server:

export GERONIMO_OPTS=-Dorg.apache.geronimo.jaxws.builder.useSimpleFinder=true

This will disable discovery of @WebService and @WebServiceProvider annotated classes and deployment
of these web services. This discovery and deployment causes the wsdl generation error. One
of the web services discovered is a class annotated with @WebServiceProvider. It has no wsdl
specified and is using SOAP binding. That's not allowed by the spec. There are some Sun-specific
deployment descriptors that configure this particular service in the right way but they are
obviously ignored by Geronimo. 

There are a couple of things that can be improved though (wsdl generation logging and throwing
an error when WebServiceProvider without wsdl is discovered) so I'll work on fixing those.


> OpenSSO Deployment fails with "WSDL generation failed"
> ------------------------------------------------------
>
>                 Key: GERONIMO-4664
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4664
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>    Affects Versions: 2.1.4, 2.1.5, 2.2
>            Reporter: Kevan Miller
>            Assignee: Jarek Gawor
>             Fix For: 2.1.5, 2.2
>
>
> Deployment of the OpenSSO war (see https://opensso.dev.java.net/public/use/ for download)
will result in a "WSDL generation failed" error.
> OpenSSO has also identified an XBean bug, see XBEAN-126. However, this problem is not
causing the WSDL generation error. I don't think that XBEAN-126 actually causes a failure
-- it just generates a lot of stacktraces to STDOUT.
> In addition to fixing the wsdl generation error, should we consider capturing more information
about the generation failure? Info on what might actually be wrong would sure be useful...
> I'm running this on G 2.1.4 (Tomcat/Axis2).

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