[ 
https://issues.apache.org/jira/browse/OOZIE-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15805958#comment-15805958
 ] 

Robert Kanter commented on OOZIE-2746:
--------------------------------------

Before committing this, I think it would be best to try to figure out why this 
is different for [~Dongying Jiao].  

I tried backporting OOZIE-2159 to Oozie 4.2 and it the tests work fine for me.  
[~Dongying Jiao], can you try running the tests on Oozie 4.3 and see if that 
also fails for you?  

[~Dongying Jiao], can you also check which version of xerces is being used?  
That's the parser Oozie is using and that's where the cvc error comes from.  If 
you build Oozie, you should find xerces 2.10.0:
{noformat}
find . -name xerces*.jar
./client/target/oozie-client-4.2.0-client/oozie-client-4.2.0/lib/xercesImpl-2.10.0.jar
./webapp/target/oozie-webapp-4.2.0/WEB-INF/lib/xercesImpl-2.10.0.jar
{noformat}



For reference, my env is:
{noformat}
mvn -version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512m; 
support was removed in 8.0
Picked up _JAVA_OPTIONS: -Djava.awt.headless=true
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 
05:51:28-0800)
Maven home: /usr/local/Cellar/maven30/3.0.5/libexec
Java version: 1.8.0_91, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_91.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.1", arch: "x86_64", family: "mac"
{noformat}
I also tried with Java 1.7.0_79

> Several tests failure in TestV2ValidateServlet.java
> ---------------------------------------------------
>
>                 Key: OOZIE-2746
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2746
>             Project: Oozie
>          Issue Type: Test
>          Components: tests
>    Affects Versions: 4.2.0
>            Reporter: Dongying Jiao
>         Attachments: OOZIE-2746-1.patch, OOZIE-2746-2.patch, 
> OOZIE-2746-3.patch, OOZIE-2746-4.patch
>
>
> I backport JIRA {{OOZIE-2159 : 'oozie validate' command should be moved 
> server-side}} in oozie 4.2.0 release, but has several UT failures in 
> TestV2ValidateServlet. 
> For example:
> From UT output of TestV2ValidateServlet#testValidateBundle:
> {noformat}
> error[E0701], E0701: XML schema error, bundle.xml, 
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 115; cvc-elt.1: 
> Cannot find the declaration of element 'bundle-app'.
> org.apache.oozie.servlet.XServletException: E0701: XML schema error, 
> bundle.xml, org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 115; 
> cvc-elt.1: Cannot find the declaration of element 'bundle-app'.
> {noformat}
> If I modify validate(String xml) function in V2ValidateServlet.java from :
> {code}
> if (!e.getMessage().contains("cvc-elt.1.a"))
> { exception = e; break; }
> {code}
> to:
> {code}
> if (!e.getMessage().contains("cvc-elt.1"))
> { exception = e; break; }
> {code}
> Then this UT can pass.
> I wonder what is the difference between exception message {{cvc-elt.1}} and 
> {{cvc-elt.1.a}}.
> Why {{cvc-elt.1}} is generated from my environment instead of {{cvc-elt.1.a}}?
> Thanks very much.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to