[ 
https://issues.apache.org/jira/browse/XMLBEANS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

PJ Fanning updated XMLBEANS-613:
--------------------------------
    Priority: Major  (was: Critical)

> XmlObject.Factory.parse() don't return the type of XML Document
> ---------------------------------------------------------------
>
>                 Key: XMLBEANS-613
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-613
>             Project: XMLBeans
>          Issue Type: Bug
>          Components: XmlObject
>    Affects Versions: Version 5.0.3, Version 5.1.0
>            Reporter: Huynh Long Thang
>            Priority: Major
>         Attachments: image-2022-06-28-16-33-48-716.png, 
> image-2022-06-30-17-12-47-080.png, image-2022-07-01-13-51-41-913.png, 
> image-2022-07-05-16-19-38-097.png, image-2022-07-06-08-50-17-630.png
>
>
> I am trying to upgrade XMLBeans version 5.1.0 from version 3.1.0. The XML 
> Document when running on our application (using IBM Websphere as a server) 
> can not parse with *XmlObject.Factory.parse:*
> h6. {{Code:}}
> {code:java}
> XmlObject xmlObj = XmlObject.Factory.parse(content, opts);{code}
> {*}It worked well with version 3.1.0 before{*}. But after upgrading to 5.1.0 
> (similar to 5.0.3) , it always returns XmlAnyTypeImpl type. 
> Even, it can parse when calling the Inner Factory class directly:
> Example:
> {code:java}
>   RequestSecurityTokenResponseCollectionDocument xmlObj = 
> RequestSecurityTokenResponseCollectionDocument 
> .Factory.parse(content,opts);{code}
>  
> Beside, I found the class which is built from the schema with xmlbeans in my 
> source code like the image:
> !image-2022-06-28-16-33-48-716.png!
> I think that there is a issue with class loading. Has anyone meet this issue 
> and how to resolve it? Thank you for your support.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to