[jboss-jira] [JBoss JIRA] Commented: (JBMETA-204) Validation errors in jboss_5_1.xsd (missing webservice-descriptionType)

[Zachary Bedell (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBMETA-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12471225#action_12471225 ] 

Zachary Bedell commented on JBMETA-204:
---------------------------------------

Hmm... So then it's likely that any attempts I'm making to customize the retrieval locations via setting schemaLocation aren't actually having an effect?

At this point, I wonder if the 5.1 schemas are something that "should" be used?  I've not been able to get JBoss 5.1.0.GA to deploy an app which was working under 4.2.3.  Falling back to the 5.0 schemas (with the XML prolog in jboss.xml below) does appear to pass validation.

<jboss xmlns="http://www.jboss.com/xml/ns/javaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd"
       version="3.0">

The jboss.xml *does* validate when checked in an XML editor on my development machine, both with the 5_0 and 5_1 versions of the schema in the prolog (and the file otherwise unmodified).  Trying with the 5_1 fails at deployment with "xml is not well formed".  Starting up with trace level logging lists messages like the following for all of the elements in jboss.xml before it finally fails:

[RtElementHandler] startElement {http://www.jboss.com/xml/ns/javaee}jboss parent=null term=org.jboss.xb.binding.sunday.unmarshalling.ElementBinding at 2ddde6d0({http://www.jboss.com/xml/ns/javaee}jboss, type={http://www.jboss.com/xml/ns/javaee}jbossType)
[RtElementHandler] Failed to resolve class for element {http://www.jboss.com/xml/ns/javaee}jboss: com.jboss.xml.ns.javaee.JbossType

Deploying with the 5_0 schemas appears okay (I'm running into other problems further along now).  If the 5_1 schemas aren't considered "production ready" at this point, then this ticket can probably close out as is.  If they *are* supposed to be ready, then there's still an issue.  I can definitely provided additional logs and samples of the XML if that's the case.


> Validation errors in jboss_5_1.xsd (missing webservice-descriptionType)
> -----------------------------------------------------------------------
>
>                 Key: JBMETA-204
>                 URL: https://jira.jboss.org/jira/browse/JBMETA-204
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.1.GA
>         Environment: Eclipse 3.4, WebToolsPlatform 3.0
>            Reporter: Zachary Bedell
>            Assignee: Alexey Loubyansky
>            Priority: Critical
>
> An additional validation issue with current trunk jboss_5_1.xsd.  The webservicesType complex type references type jboss:webservice-descriptionType which is missing.  Copying the type from the jboss_5_0.xsd (which appears directly the webservicesType object around line 1223) resolves the issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira