Bug 793317 (JBEPP-400) - Include webservice xsd files
Summary: Include webservice xsd files
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-400
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.0.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.1.DEV01
Assignee: claprun@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On: JBEPP-789
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-30 14:31 UTC by Martin Weiler
Modified: 2013-09-02 05:13 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-03 17:06:55 UTC
Type: Task


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-400 0 Major Closed Include webservice xsd files 2013-01-22 10:49:05 UTC
Red Hat Issue Tracker JBWS-3162 0 Major Closed Add javaee_web_services_metadata_handler_2_0.xsd to jbossws-entities.properties 2013-01-22 10:49:05 UTC

Description Martin Weiler 2010-07-30 14:31:03 UTC
Affects: Release Notes
Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/1197883
project_key: JBEPP

When starting EPP 5 without internet connection the following WARN messages can be found in the log file:

16:21:54,416 WARN  [JBossEntityResolver] Trying to resolve systemId as a non-file URL: http://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_0.xsd
16:21:54,417 WARN  [JBossWSEntityResolver] Trying to resolve id as a non-file URL: http://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_0.xsd
16:21:54,421 WARN  [SaxJBossXBParser] schema_reference.4: Failed to read schema document 'http://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ *unknown*[26,158]

Looks like http://java.sun.com/xml/ns/javaee/javaee_web_services_metadata_handler_2_0.xsd is always loaded over the network ...

Comment 1 Chris Laprun 2010-08-03 12:03:15 UTC
This might need to be brought up with the JBoss WS team, actually.

Comment 2 Robert Dale 2010-11-18 14:40:46 UTC
Link: Added: This issue related JBWS-3162


Comment 3 Robert Dale 2010-11-18 14:41:49 UTC
I've submitted JBWS-3162 to jbossws.  If they think that the change doesn't belong there then we'll need to use a catalog here.

Comment 4 Robert Dale 2010-11-19 17:51:59 UTC
Unfortunately the default jax-ws implementation of jbossws-native doesn't support catalogs.  You could switch to CXF as a workaround.

Comment 5 Robert Dale 2010-11-19 18:05:09 UTC
requested JBWS-3165

Comment 6 Chris Laprun 2010-11-19 18:22:10 UTC
Thanks, Robert. I had started looking into using a catalog and couldn't find relevant information before I had to move to more pressing issues. Thanks for the definitive answer.

Comment 7 Chris Laprun 2011-01-27 15:49:52 UTC
Link: Added: This issue depends GTNWSRP-199


Comment 8 Chris Laprun 2011-02-03 16:30:10 UTC
Re-opening to resolve properly.

Comment 9 Chris Laprun 2011-02-03 16:30:37 UTC
Release Notes Docs Status: Added: Not Required
Affects: Added: [Release Notes]


Comment 10 Chris Laprun 2011-02-03 16:32:48 UTC
Will be addressed with upgrade of WSRP to 2.0.1-GA (JBEPP-789)

Comment 11 Chris Laprun 2011-02-03 16:33:28 UTC
Link: Added: This issue depends JBEPP-789


Comment 12 Chris Laprun 2011-02-03 16:42:42 UTC
Re-opening to add release note.

Comment 13 Chris Laprun 2011-02-03 17:06:55 UTC
Release Notes Docs Status: Removed: Not Required Added: Documented as Resolved Issue
Release Notes Text: Added: The Java EE Webservices Metadata Handler 2.0 schema is now bundled with the WSRP so that it's not necessary to retrieve it over the network, thus allowing proper behavior if the network is down or if the original is not accessible for some reason.


Comment 14 Scott Mumford 2011-03-29 06:35:04 UTC
Updated the Release Notes text to more fully reflect the "Cause, Consequence, Fix, Result" model.

Comment 15 Scott Mumford 2011-03-29 06:35:04 UTC
Release Notes Text: Removed: The Java EE Webservices Metadata Handler 2.0 schema is now bundled with the WSRP so that it's not necessary to retrieve it over the network, thus allowing proper behavior if the network is down or if the original is not accessible for some reason. Added: Warning messages were found in the server log when starting EPP 5 without an active internet connection. This was because the Java EE Webservices Metadata Handler 2.0 schema was requested via the network at start up. The schema is now bundled with the WSRP which allows EPP to start without producing error messages if there is no internet connection.


Comment 16 Scott Mumford 2011-05-04 04:02:31 UTC
Release Notes Text: Removed: Warning messages were found in the server log when starting EPP 5 without an active internet connection. This was because the Java EE Webservices Metadata Handler 2.0 schema was requested via the network at start up. The schema is now bundled with the WSRP which allows EPP to start without producing error messages if there is no internet connection. Added: Warning messages were found in the server log when starting JBoss Enterprise Portal Platform 5 without an active internet connection. This was because the Java EE Webservices Metadata Handler 2.0 schema was requested via the network at start up. The schema is now bundled with the WSRP which allows JBoss Enterprise Portal Platform to start without producing error messages if there is no internet connection.



Note You need to log in before you can comment on or make changes to this bug.