You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@openjpa.apache.org by Jason Pyeron <jp...@pdinc.us> on 2011/07/18 22:34:26 UTC
It can be done in annotations but not in XML?
Hmmm... I don't think I am crazy here
@Id @ManyToOne @JoinColumn(name = "CLM_VERS_ID", referencedColumnName =
"CLM_VERS_ID") private ClaimVersion claimVersion;
<id name="claimVersion"> <join-column name="CLM_VERS_ID"
referenced-column-name="CLM_VERS_ID" /> </id>
Jul 18, 2011 4:30:08 PM org.apache.openjpa.lib.log.CommonsLogFactory$LogAdapter
warn
WARNING: An exception was thrown while attempting to perform class file
transformation on
"com/carefirst/fep/local/commons/model/claim/BillingProviderSecondaryId":
<openjpa-2.1.0-SNAPSHOT-r422266:1057903 nonfatal general error>
org.apache.openjpa.util.GeneralException: org.xml.sax.SAXException:
file:/C:/Documents%20and%20Settings/All%20Users/workspace/testing/bin/META-INF/o
rm-claim.xml [Location: Line: 16, C: 76]: org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with element
'join-column'. One of '{"http://java.sun.com/xml/ns/persistence/orm":column,
"http://java.sun.com/xml/ns/persistence/orm":generated-value,
"http://java.sun.com/xml/ns/persistence/orm":temporal,
"http://java.sun.com/xml/ns/persistence/orm":table-generator,
"http://java.sun.com/xml/ns/persistence/orm":sequence-generator}' is expected.
at
org.apache.openjpa.persistence.PersistenceMetaDataFactory.parseXML(PersistenceMe
taDataFactory.java:295)
at
org.apache.openjpa.persistence.PersistenceMetaDataFactory.load(PersistenceMetaDa
taFactory.java:228)
at
org.apache.openjpa.meta.MetaDataRepository.getMetaDataInternal(MetaDataRepositor
y.java:580)
at
org.apache.openjpa.meta.MetaDataRepository.getMetaDataInternal(MetaDataRepositor
y.java:400)
at
org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:3
84)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:283)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:254)
at
org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransfor
mer.java:144)
at
org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransform
er.java:124)
at
sun.instrument.TransformerManager.transform(TransformerManager.java:169)
at
sun.instrument.InstrumentationImpl.transform(InstrumentationImpl.java:365)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
Caused by: java.io.IOException: org.xml.sax.SAXException:
file:/C:/Documents%20and%20Settings/All%20Users/workspace/testing/bin/META-INF/o
rm-claim.xml [Location: Line: 16, C: 76]: org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with element
'join-column'. One of '{"http://java.sun.com/xml/ns/persistence/orm":column,
"http://java.sun.com/xml/ns/persistence/orm":generated-value,
"http://java.sun.com/xml/ns/persistence/orm":temporal,
"http://java.sun.com/xml/ns/persistence/orm":table-generator,
"http://java.sun.com/xml/ns/persistence/orm":sequence-generator}' is expected.
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parseNewResource(XMLMetaDataParser
.java:396)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:334)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:311)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:284)
at
org.apache.openjpa.persistence.XMLPersistenceMetaDataParser.parse(XMLPersistence
MetaDataParser.java:365)
at
org.apache.openjpa.persistence.PersistenceMetaDataFactory.parseXML(PersistenceMe
taDataFactory.java:293)
... 23 more
Caused by: org.xml.sax.SAXException:
file:/C:/Documents%20and%20Settings/All%20Users/workspace/testing/bin/META-INF/o
rm-claim.xml [Location: Line: 16, C: 76]: org.xml.sax.SAXParseException:
cvc-complex-type.2.4.a: Invalid content was found starting with element
'join-column'. One of '{"http://java.sun.com/xml/ns/persistence/orm":column,
"http://java.sun.com/xml/ns/persistence/orm":generated-value,
"http://java.sun.com/xml/ns/persistence/orm":temporal,
"http://java.sun.com/xml/ns/persistence/orm":table-generator,
"http://java.sun.com/xml/ns/persistence/orm":sequence-generator}' is expected.
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.getException(XMLMetaDataParser.jav
a:675)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.error(XMLMetaDataParser.java:434)
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWr
apper.java:134)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorRep
orter.java:384)
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorRep
orter.java:318)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.r
eportError(XMLSchemaValidator.java:417)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.reportSchemaError(
XMLSchemaValidator.java:3182)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleStartElement
(XMLSchemaValidator.java:1806)
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.emptyElement(XMLSc
hemaValidator.java:725)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElemen
t(XMLNSDocumentScannerImpl.java:377)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentC
ontentDriver.next(XMLDocumentFragmentScannerImpl.java:2755)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentS
cannerImpl.java:648)
at
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocum
entScannerImpl.java:140)
at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocum
ent(XMLDocumentFragmentScannerImpl.java:511)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configu
ration.java:808)
at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configu
ration.java:737)
at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119)
at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXPa
rser.java:1205)
at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXPar
serImpl.java:522)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
at
org.apache.openjpa.lib.meta.XMLMetaDataParser.parseNewResource(XMLMetaDataParser
.java:393)
... 28 more
-Jason
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
Re: It can be done in annotations but not in XML?
Posted by Michael Dick <mi...@gmail.com>.
Sorry about that, I missed the email about having OpenJPA generate the XML
(which is pretty cool).
Thanks for the clarification,
-mike
On Mon, Jul 18, 2011 at 5:09 PM, Jason Pyeron <jp...@pdinc.us> wrote:
> > -----Original Message-----
> > From: Pinaki Poddar [mailto:ppoddar@apache.org]
> > Sent: Monday, July 18, 2011 17:48
> > To: users@openjpa.apache.org
> > Subject: Re: It can be done in annotations but not in XML?
> >
> > I thought (assumed rather) the XML was generated by OpenJPA
> > itself form the annotated entity classes.
> > Jason, can you please confirm that assumption?
>
> Yes, it was generated from openjpa
>
> > If that is the case, then it is a OpenJPA bug?
> > Else it is my bad assumption.
> >
> >
> >
> > -----
> > Pinaki Poddar
> > Chair, Apache OpenJPA Project
> > --
> > View this message in context:
> > http://openjpa.208410.n2.nabble.com/It-can-be-done-in-annotati
> ons-but-not-in-XML-tp6596288p6596544.html
> > Sent from the OpenJPA Users mailing list archive at Nabble.com.
> >
>
>
>
> --
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> - -
> - Jason Pyeron PD Inc. http://www.pdinc.us -
> - Principal Consultant 10 West 24th Street #100 -
> - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
> - -
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> This message is copyright PD Inc, subject to license 20080407P00.
>
>
>
>
RE: It can be done in annotations but not in XML?
Posted by Jason Pyeron <jp...@pdinc.us>.
> -----Original Message-----
> From: Pinaki Poddar [mailto:ppoddar@apache.org]
> Sent: Monday, July 18, 2011 17:48
> To: users@openjpa.apache.org
> Subject: Re: It can be done in annotations but not in XML?
>
> I thought (assumed rather) the XML was generated by OpenJPA
> itself form the annotated entity classes.
> Jason, can you please confirm that assumption?
Yes, it was generated from openjpa
> If that is the case, then it is a OpenJPA bug?
> Else it is my bad assumption.
>
>
>
> -----
> Pinaki Poddar
> Chair, Apache OpenJPA Project
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/It-can-be-done-in-annotati
ons-but-not-in-XML-tp6596288p6596544.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
Re: It can be done in annotations but not in XML?
Posted by Pinaki Poddar <pp...@apache.org>.
I thought (assumed rather) the XML was generated by OpenJPA itself form the
annotated entity classes.
Jason, can you please confirm that assumption?
If that is the case, then it is a OpenJPA bug?
Else it is my bad assumption.
-----
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context: http://openjpa.208410.n2.nabble.com/It-can-be-done-in-annotations-but-not-in-XML-tp6596288p6596544.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Re: It can be done in annotations but not in XML?
Posted by Michael Dick <mi...@gmail.com>.
I'm not sure it's a bug. A quick read of the XSD in the spec backs up the
parse exception, the id tag can't contain a join column..
Shouldn't the xml be something like this?
<attributes>
<id name="claimVersion">
</id>
<many-to-one name="claimVersion">
<join-column name="CLM_VERS_ID"
referenced-column-name="CLM_VERS_ID" />
</many-to-one>
</attributes>
-mike
On Mon, Jul 18, 2011 at 3:52 PM, Pinaki Poddar <pp...@apache.org> wrote:
> > Hmmm... I don't think I am crazy here
> nope. I think u just found a bug.
> Please file a JIRA.
>
>
> -----
> Pinaki Poddar
> Chair, Apache OpenJPA Project
> --
> View this message in context:
> http://openjpa.208410.n2.nabble.com/It-can-be-done-in-annotations-but-not-in-XML-tp6596288p6596368.html
> Sent from the OpenJPA Users mailing list archive at Nabble.com.
>
Re: It can be done in annotations but not in XML?
Posted by Pinaki Poddar <pp...@apache.org>.
> Hmmm... I don't think I am crazy here
nope. I think u just found a bug.
Please file a JIRA.
-----
Pinaki Poddar
Chair, Apache OpenJPA Project
--
View this message in context: http://openjpa.208410.n2.nabble.com/It-can-be-done-in-annotations-but-not-in-XML-tp6596288p6596368.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.