EclipseZone - [Teneo] DocumentRoot object name causes ...

The Rich Engineering Heritage Behind Dependency Injection

Andrew McVeigh takes us on a tour of the rich heritage behind dependency injection, what it represents, and tells us why its here to stay.

Java, the OLPC, and community responsibility

The "One Laptop Per Child" project has a great device ready to ship, but there's no Java on there. Let's think about working together to put Java on OLPC!

Replies: 5 - Pages: 1
Threads: [ Previous | Next ]

Reply 1. At 4:06 AM on Aug 8, 2008, Martin Taal wrote:: Re: [Teneo] DocumentRoot object name causes PAnnotation difficulty?
Hi Jason,
Normally DocumentRoots are ignored by Teneo but the check if a type is a documentroot is very
primitive (:-(): it checks if the name of the EClass is DocumentRoot). So it can be related to this
(as you are renaming). So if the documentroots don't need to be persisted to the db then I would add
the @Transient annotation.

If this does not solve it for you, can you post the complete stacktrace?

gr. Martin

jason henriksen wrote:
> Hi guys,
>
> I've set some XSD up like this:
>
> > xmlns:xsd='http://www.w3.org/2001/XMLSchema'
> xmlns:ecore='http://www.eclipse.org/emf/2002/Ecore'
> xmlns:com.vsp.ancillary.service='http://service.ancillary.vsp.com'
> targetNamespace='http://service.ancillary.vsp.com'
> ecore:nsPrefix='com.vsp.ancillary.service'
> ecore:package='com.vsp.ancillary.service'
> elementFormDefault='qualified'
>
> ecore:documentRoot='AncillaryServiceDocumentRoot'
> >
>
> However I'm getting exceptions like this:
> Caused by: java.lang.Throwable: java.lang.IllegalArgumentException: No
> annotated model element present for: value for type EAttribute has its
> epackage been registered with Teneo?
>
> The package has been registered with Teneo, so I'm wondering if Teneo
> treats DocumentRoot specially and gets confused when I rename it? Do I
> need to put @Transient somewhere?
>
> We have abou 50 packages of model objects. Until I can make the
> DocumentRoot renaming work, I have 50 objects all called DocumentRoot in
> each package of my model hierarchy. :(
>
> Thanks for any help,
>
> Jason

--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal at springsite dot com - mtaal at elver dot org
Web: www.springsite.com - www.elver.org
Reply 2. At 7:45 AM on Aug 8, 2008, Ed Merks wrote:: Re: [Teneo] DocumentRoot object name causes PAnnotation difficulty?
Martin,

It's best to use ExtendedMetaData.INSTANCE.isDocumentRoot().

Martin Taal wrote:
> Hi Jason,
> Normally DocumentRoots are ignored by Teneo but the check if a type is
> a documentroot is very primitive (:-(): it checks if the name of the
> EClass is DocumentRoot). So it can be related to this (as you are
> renaming). So if the documentroots don't need to be persisted to the
> db then I would add the @Transient annotation.
>
> If this does not solve it for you, can you post the complete stacktrace?
>
> gr. Martin
>
> jason henriksen wrote:
>> Hi guys,
>>
>> I've set some XSD up like this:
>>
>> >> xmlns:xsd='http://www.w3.org/2001/XMLSchema'
>> xmlns:ecore='http://www.eclipse.org/emf/2002/Ecore'
>> xmlns:com.vsp.ancillary.service='http://service.ancillary.vsp.com'
>> targetNamespace='http://service.ancillary.vsp.com'
>> ecore:nsPrefix='com.vsp.ancillary.service'
>> ecore:package='com.vsp.ancillary.service'
>> elementFormDefault='qualified'
>>
>> ecore:documentRoot='AncillaryServiceDocumentRoot'
>> >
>>
>> However I'm getting exceptions like this:
>> Caused by: java.lang.Throwable: java.lang.IllegalArgumentException:
>> No annotated model element present for: value for type EAttribute
>> has its epackage been registered with Teneo?
>>
>> The package has been registered with Teneo, so I'm wondering if Teneo
>> treats DocumentRoot specially and gets confused when I rename it? Do
>> I need to put @Transient somewhere?
>>
>> We have abou 50 packages of model objects. Until I can make the
>> DocumentRoot renaming work, I have 50 objects all called DocumentRoot
>> in each package of my model hierarchy. :(
>>
>> Thanks for any help,
>>
>> Jason
>
>
Reply 3. At 9:08 AM on Aug 8, 2008, Martin Taal wrote:: Re: [Teneo] DocumentRoot object name causes PAnnotation difficulty?
Thanks Ed, that is a much better check.

gr. Martin

Ed Merks wrote:
> Martin,
>
> It's best to use ExtendedMetaData.INSTANCE.isDocumentRoot().
>
>
> Martin Taal wrote:
>> Hi Jason,
>> Normally DocumentRoots are ignored by Teneo but the check if a type is
>> a documentroot is very primitive (:-(): it checks if the name of the
>> EClass is DocumentRoot). So it can be related to this (as you are
>> renaming). So if the documentroots don't need to be persisted to the
>> db then I would add the @Transient annotation.
>>
>> If this does not solve it for you, can you post the complete stacktrace?
>>
>> gr. Martin
>>
>> jason henriksen wrote:
>>> Hi guys,
>>>
>>> I've set some XSD up like this:
>>>
>>> >>> xmlns:xsd='http://www.w3.org/2001/XMLSchema'
>>> xmlns:ecore='http://www.eclipse.org/emf/2002/Ecore'
>>> xmlns:com.vsp.ancillary.service='http://service.ancillary.vsp.com'
>>> targetNamespace='http://service.ancillary.vsp.com'
>>> ecore:nsPrefix='com.vsp.ancillary.service'
>>> ecore:package='com.vsp.ancillary.service'
>>> elementFormDefault='qualified'
>>>
>>> ecore:documentRoot='AncillaryServiceDocumentRoot'
>>> >
>>>
>>> However I'm getting exceptions like this:
>>> Caused by: java.lang.Throwable: java.lang.IllegalArgumentException:
>>> No annotated model element present for: value for type EAttribute
>>> has its epackage been registered with Teneo?
>>>
>>> The package has been registered with Teneo, so I'm wondering if Teneo
>>> treats DocumentRoot specially and gets confused when I rename it? Do
>>> I need to put @Transient somewhere?
>>>
>>> We have abou 50 packages of model objects. Until I can make the
>>> DocumentRoot renaming work, I have 50 objects all called DocumentRoot
>>> in each package of my model hierarchy. :(
>>>
>>> Thanks for any help,
>>>
>>> Jason
>>
>>

--

With Regards, Martin Taal

Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal at springsite dot com - mtaal at elver dot org
Web: www.springsite.com - www.elver.org
Reply 4. At 2:16 PM on Aug 8, 2008, jason henriksen wrote:: Re: [Teneo] DocumentRoot object name causes PAnnotation difficulty?
Do you guys have a suggestion on how I could add @Transient to the
generated DocumentRoot object? I'm not sure where in the XSD to put the
annotation.

Martin, I logged this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=243616
(If you'd like me to write a patch for this let me know, but I'm betting
you can do it faster/easier on your own)

Ed, I'm a bit confused if I logged the bug properly. I know Teneo isn't
under EMFT any more, but within Modeling it doesn't seem to have a
component that fits. Any suggestions?

Thanks guys,

Jason Henriksen
Reply 5. At 2:48 PM on Aug 8, 2008, Richard Gronback wrote:: Re: [Teneo] DocumentRoot object name causes PAnnotation difficulty?
I moved it to the Teneo component (now under EMF).

- Rich

On 8/8/08 2:16 PM, in article g7i2il$lqv$1 at build dot eclipse dot org, "jason
henriksen" wrote:

> Do you guys have a suggestion on how I could add @Transient to the
> generated DocumentRoot object? I'm not sure where in the XSD to put the
> annotation.
>
> Martin, I logged this bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=243616
> (If you'd like me to write a patch for this let me know, but I'm betting
> you can do it faster/easier on your own)
>
> Ed, I'm a bit confused if I logged the bug properly. I know Teneo isn't
> under EMFT any more, but within Modeling it doesn't seem to have a
> component that fits. Any suggestions?
>
> Thanks guys,
>
> Jason Henriksen