You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2009/06/02 05:54:07 UTC
[jira] Created: (GERONIMO-4664) OpenSSO Deployment fails with "WSDL
generation failed"
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
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.
[jira] Closed: (GERONIMO-4664) OpenSSO Deployment fails with "WSDL
generation failed"
Posted by "Rex Wang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rex Wang closed GERONIMO-4664.
------------------------------
closing it
> 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.
[jira] Commented: (GERONIMO-4664) OpenSSO Deployment fails with
"WSDL generation failed"
Posted by "Kevan Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734767#action_12734767 ]
Kevan Miller commented on GERONIMO-4664:
----------------------------------------
Jarek,
Are we done with this? Feel free to close...
> 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.
[jira] Resolved: (GERONIMO-4664) OpenSSO Deployment fails with
"WSDL generation failed"
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor resolved GERONIMO-4664.
-----------------------------------
Resolution: Fixed
The improvements I mentioned in my previous comment are already done - see subversion commits tabs for details.
> 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.
[jira] Commented: (GERONIMO-4664) OpenSSO Deployment fails with
"WSDL generation failed"
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (GERONIMO-4664) OpenSSO Deployment fails with
"WSDL generation failed"
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Gawor reassigned GERONIMO-4664:
-------------------------------------
Assignee: Jarek Gawor
> 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.