Eclipse Community Forums: M2T (model-to-text transformation) » JET2 merging of model data with existing Java code

Help

Home

Home » Modeling » M2T (model-to-text transformation) » JET2 merging of model data with existing Java code

Show: Today's Messages :: Show Polls :: Message Navigator

JET2 merging of model data with existing Java code [message #56454]

Mon, 26 January 2009 15:26

J F

Messages: 256
Registered: July 2009

Senior Member

In
http://www-128.ibm.com/developerworks/java/library/os-ecl-je t/index.html?ca=drs
the authors mention tag libraries that appear to load java code as input
models (
http://wiki.eclipse.org/JET_FAQ_What_kind_of_input_model_can _JET_handle%3F);

"org.eclipse.jet.modelInspectors

This allows you to define inspectors that enable the JET XPath engine to
interpret loaded Java objects as XPath nodes. An inspector is an object
that adapts objects to the XPath information model. As an example, JET
uses a model to navigate the Eclipse workspace. Note that this is a
provisional API, and that it is likely to evolve over time."

... or if not strictly input models then allowing me process a JDT tree
and XML model at the same time?

Has this been ambandoned in favour of using JMerge?

Thanks...

Report message to a moderator

Re: JET2 merging of model data with existing Java code [message #56512 is a reply to message #56454]

Tue, 27 January 2009 16:10

Paul Elder

Messages: 849
Registered: July 2009

Senior Member

JF:

No, the modelInspectors approach has not been abandoned. JET2 already has
the following inspectors:

* XML DOM Node objects
* EMF EObject object (which covers any EMF-based model in existance)
* Eclipse workspaces IResource objects

I will be adding to this list in the Galileo release:
* JDT trees

I hope also, to add the ability to navigate (but no promises)
* java.util.Properties
* Manifest files

But, that doesn't mean you should leave JMerge behind.

Paul

Report message to a moderator

Re: JET2 merging of model data with existing Java code [message #56534 is a reply to message #56512]

Tue, 27 January 2009 22:51

Eclipse User

Originally posted by: tmothymarc.freenet.de

Hi Paul,

just a simple question. With JDT tree, you mean the AST created by the
JDT or what else?

Thx
Timothy

Paul Elder schrieb:
> JF:
>
> No, the modelInspectors approach has not been abandoned. JET2 already has
> the following inspectors:
>
> * XML DOM Node objects
> * EMF EObject object (which covers any EMF-based model in existance)
> * Eclipse workspaces IResource objects
>
> I will be adding to this list in the Galileo release:
> * JDT trees
>
> I hope also, to add the ability to navigate (but no promises)
> * java.util.Properties
> * Manifest files
>
> But, that doesn't mean you should leave JMerge behind.
>
> Paul
>
>

Report message to a moderator

Re: JET2 merging of model data with existing Java code [message #56642 is a reply to message #56534]

Thu, 29 January 2009 14:44

Paul Elder

Messages: 849
Registered: July 2009

Senior Member

Timothy:

I mean the all the descendents of ASTNode:

http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.i sv/reference/api/org/eclipse/jdt/core/dom/ASTNode.html

Paul

"Timothy Marc" <tmothymarc@freenet.de> wrote in message
news:glo34r$hfi$1@build.eclipse.org...
> Hi Paul,
>
> just a simple question. With JDT tree, you mean the AST created by the JDT
> or what else?
>
> Thx
> Timothy
>
> Paul Elder schrieb:
>> JF:
>>
>> No, the modelInspectors approach has not been abandoned. JET2 already has
>> the following inspectors:
>>
>> * XML DOM Node objects
>> * EMF EObject object (which covers any EMF-based model in existance)
>> * Eclipse workspaces IResource objects
>>
>> I will be adding to this list in the Galileo release:
>> * JDT trees
>>
>> I hope also, to add the ability to navigate (but no promises)
>> * java.util.Properties
>> * Manifest files
>>
>> But, that doesn't mean you should leave JMerge behind.
>>
>> Paul

Report message to a moderator

Re: JET2 merging of model data with existing Java code [message #56749 is a reply to message #56642]

Sun, 01 February 2009 14:53

Eclipse User

Originally posted by: tmothymarc.freenet.de

Okay, thanks Paul.
i think this enhancement would be quite fantastic.

Paul Elder schrieb:
> Timothy:
>
> I mean the all the descendents of ASTNode:
>
> http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.i sv/reference/api/org/eclipse/jdt/core/dom/ASTNode.html
>
> Paul
>
> "Timothy Marc" <tmothymarc@freenet.de> wrote in message
> news:glo34r$hfi$1@build.eclipse.org...
>> Hi Paul,
>>
>> just a simple question. With JDT tree, you mean the AST created by the JDT
>> or what else?
>>
>> Thx
>> Timothy
>>
>> Paul Elder schrieb:
>>> JF:
>>>
>>> No, the modelInspectors approach has not been abandoned. JET2 already has
>>> the following inspectors:
>>>
>>> * XML DOM Node objects
>>> * EMF EObject object (which covers any EMF-based model in existance)
>>> * Eclipse workspaces IResource objects
>>>
>>> I will be adding to this list in the Galileo release:
>>> * JDT trees
>>>
>>> I hope also, to add the ability to navigate (but no promises)
>>> * java.util.Properties
>>> * Manifest files
>>>
>>> But, that doesn't mean you should leave JMerge behind.
>>>
>>> Paul
>
>

Report message to a moderator

Previous Topic:	[JET2] Iterating through the elements of an EList in an EMF model
Next Topic:	[Announce] M2T XPAND 0.7.0 M200902040403 is available

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jun 30 13:49:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter