Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » M2T (model-to-text transformation) » why WS tags not autoimported?
why WS tags not autoimported? [message #52053] Tue, 14 October 2008 20:02 Go to next message
Roshan S. is currently offline Roshan S.Friend
Messages: 125
Registered: July 2009
Senior Member
I've been wondering this for a while and never asked. When you create a
transformation project all of the tag libraries are autoimported except
for the workspace tag library. It's manually imported in the generated
main.jet file. What's the reason for this? I guess a good reason would
be since it's main functionality is for the workspace and would mainly be
used in the main template it's not used anywhere else and therefore,
memory could be saved, but I don't believe it's much at all.

Anyone have any ideas?

Re: why WS tags not autoimported? [message #52104 is a reply to message #52053] Thu, 16 October 2008 18:20 Go to previous messageGo to next message
Kamesh Sampath is currently offline Kamesh SampathFriend
Messages: 213
Registered: July 2009
Senior Member

Another reason to add to your point is that JET can also be executed from
the a standalone project which necessarily be a Eclipse based project ,
the concept is that all OSGI bundles can be executed from anywhere , if
thats the case then lots of Workspace related pre initializations could
potentially result in errors and plugins will not be loaded properly.

The same reason could be though from the Project - Link to File System
type too.

JET experts please correct me if I am wrong on my perception.

Re: why WS tags not autoimported? [message #52209 is a reply to message #52053] Mon, 20 October 2008 17:38 Go to previous message
Paul Elder is currently offline Paul ElderFriend
Messages: 849
Registered: July 2009
Senior Member

There is no deep technical mystery here.

The thought was that the WS tags are generally used by a small number of
templates (main.jet and those it directly includes), and that it would be
bad practice to use them in templates that create content. So, the decision
was made to made those tags a little harder to get at.

In general, setting auto-import to true means you can avoid writing @taglib
directives in each template. Including a tag lib import with auto-import set
to false does nothing - a @taglib directive will pull in any tag library,
whether it is mentioned on plugin.xml or not.

Previous Topic:JET tag to set local variable - Flag
Next Topic:Unable to Parse XML EMF Document
Goto Forum:

Current Time: Wed May 23 01:15:32 GMT 2018

Powered by FUDForum. Page generated in 0.01680 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top