[prev in list] [next in list] [prev in thread] [next in thread]
List: xmlbeans-dev
Subject: [jira] Resolved: (XMLBEANS-400) XMlBeans : same complex type in
From: "Jacob Danner (JIRA)" <xmlbeans-dev () xml ! apache ! org>
Date: 2009-02-26 17:27:06
Message-ID: 1713814034.1235669226846.JavaMail.jira () brutus
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/XMLBEANS-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]
Jacob Danner resolved XMLBEANS-400.
-----------------------------------
Resolution: Invalid
This isn't really an issue with XMLBeans but rather the way the schemas are \
structured. There are several things the user can do for duplicate type definitions.
For this issue I would use the sfactor tool to refactor the schemas so only one type \
definition is defined.
Refactors a directory of XSD files to remove name conflicts.
Usage: sfactor [-import common.xsd] [-out outputdir] inputdir
-import common.xsd - The XSD file to contain redundant
definitions for importing.
-out outputdir - The directory into which to place XSD
files resulting from refactoring,
plus a commonly imported common.xsd.
inputdir - The directory containing the XSD files with
redundant definitions.
-license - Print license information.
> XMlBeans : same complex type in multiple xsd files
> --------------------------------------------------
>
> Key: XMLBEANS-400
> URL: https://issues.apache.org/jira/browse/XMLBEANS-400
> Project: XMLBeans
> Issue Type: Test
> Reporter: Deepa.B
> Attachments: Prb_Xsd.zip, SEPA.xml
>
>
> Problem i face is that there are same complextype elements in multiple xsd's and \
> when i try to build them under the same package using xsd config files, the complex \
> types with the same name of different xsd's are overwitten. When tried to give \
> different packages for each of such duplicate complex type, even then i face a \
> prbm. Can u please suggest us a way to solve the problem.
> Senario no : 1 (same package)
> ==============
> CBIPartyIdentification1 is an ComplexType,
> which exist in 3 different xsd files like
> CreditTransfer.xsd
> CBIPaymentRequest.00.03.05.xsd
> CBICdtrPmtStatusReport.00.03.05.xsd
> while trying to take object of type (CBIPartyIdentification1) in \
> CBIPaymentRequest.00.03.05.xsd file, but its overlapping type of \
> CBICdtrPmtStatusReport.00.03.05.xsd, so while getting object in java source is \
> NULL. Senario no : 2 (diff package)
> ==============
> In this senario, while taking object type of CBIPartyIdentification1 in \
> CBIPaymentRequest.00.03.05.xsd file, the last CBICdtrPmtStatusReport.00.03.05.xsd \
> file type is overlapped with CBIPaymentRequest.00.03.05.xsd so im getting package \
> is different( not expected one), due to this ClassCastException araise. //sample \
> snippet which we tried here.... CBIPaymentRequestMsgDocument requestDocument = \
> CBIPaymentRequestMsgDocument.Factory.parse(getInputXml()); \
> CBIBdyPaymentRequest000305 request000305 = \
> requestDocument.getCBIPaymentRequestMsg().getCBIBdyPaymentRequest(); \
> CBIPaymentRequest000305 paymentRequest000305 = \
> request000305.getCBIEnvelPaymentRequestArray(0).getCBIPaymentRequest(); \
> CBIPartyIdentification1 identification1 = \
> paymentRequest000305.getGrpHdr().getInitgPty(); \
> System.out.println(identification1.getId().getOrgId().getPrtryId().getId());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic