[shrinkwrap-issues] [JBoss JIRA] (SHRINKDESC-130) Provide a way to validate an imported or created descriptor content

[Ralf Battenfeld (JIRA)]

    [ https://issues.jboss.org/browse/SHRINKDESC-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733908#comment-12733908 ] 

Ralf Battenfeld commented on SHRINKDESC-130:
--------------------------------------------

I analysed point 4). 

The new getClassLoaderForClass(this.getClass()).getResourceAsStream(schema); call tries to find the XSD in the own jar (schema-validator) but since all XSD in the gen jar located this call doesn't resolve the entity (XSD) and therefore, the standard xerces implementation connects to the internet for downloading the missing XSD. That is the reason for the long time.

So, the issue is that the XSD resources are not in the same jar but in the gen jar. What is your favourite solution? Moving all XSDs from gen to the schma-validator module or to move some of the resource reader implementation to the gen module?   
                
> Provide a way to validate an imported or created descriptor content
> -------------------------------------------------------------------
>
>                 Key: SHRINKDESC-130
>                 URL: https://issues.jboss.org/browse/SHRINKDESC-130
>             Project: ShrinkWrap Descriptors
>          Issue Type: Feature Request
>            Reporter: Ralf Battenfeld
>            Assignee: Ralf Battenfeld
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira