Tefkat Google Group

Re: problem with parser?

2009-11-23T06:17:34Z

Thanks Ed, this is really useful info.

It's somewhat frustrating the way that upgrades to EMF cause bit-rot
based on non-regeneration of files like plugin.xml, etc But it's
handy to be reminded that this is an issue that needs to be monitored
as new versions come out.

Cheers,

michael

Re: problem with parser?

2009-11-20T06:36:56Z

Hi Jim
With low traffic, this newsgroup is often good value.
Yes things are much improved. There are now content types.
The appropriate ResourceFactory to load a file used to be chosen
a) URI-based
b) extension based
Now a content-based choice, if available, precedes the extension-based.
At the platform level these are registered and can be browsed in

Re: problem with parser?

2009-11-20T03:40:20Z

Hi Ed (on the offchance you're still reading this forum)

I am working on a different project (based on using Tefkat to write
some transformations), implementing another metamodel (actually 2)
with a non-XML file serialization. I have copied the approach to
resource implementations used by Tefkat, and (unsurprisingly) I am

Re: problem with parser?

2009-10-08T13:46:42Z

Yeah, its kinda strange. We're implementing extension_parser with the
file extension, but for some reason its trying to use the xml parser
anyway.

Re: problem with parser?

2009-10-08T09:45:49Z

Hi Jim

That looks like what happens when you pass a non-XML file to an XML loader.

Regards

Ed Willink

Jim wrote:

problem with parser?

2009-10-08T05:46:30Z

Hi,

I'm just picking up tefkat for the first time in a very, very long
time, and I found a problem that looks like its in the parser
somewhere. I can comment all the rules/patterns etc in my
transformation and still get the same result, so I think its something
basic about the parser, or resource loading.

View this page "newbie tutorial questiion"

2009-01-12T21:57:38Z

Click on [link]
- or copy & paste it into your browser's address bar if that doesn't
work.

Re: Inaccessible Instances

2007-11-05T12:30:23Z

Hi I've committed changes to fix this problem and they'll be in the
next build, lawley246, as soon as I can access the site to upload the
files.
Other bonus features of the new build include major improvements to
error reporting from the parser.
michael

Re: problem

2007-11-04T17:33:45Z

Hi David,
Thank you. That helps a lot.
Arda

Re: Inaccessible Instances

2007-11-02T01:31:09Z

TRANSFORMATION test2code : src -> tgt
NAMESPACE http:///au/edu/uq/itee/mdavv/w rsa/foxbus/modelManagement.eco re
RULE cannotResolveType
>>> FORALL ::modelManagement::designtime: :components::Component
c
MAKE println(c.name);
This one does not parse.
And this one does not find anything:

Re: Inaccessible Instances

2007-11-02T01:25:39Z

Even stranger, the rule below works!
TRANSFORMATION test2code : src -> tgt
NAMESPACE http:///au/edu/uq/itee/mdavv/w rsa/foxbus/designtime/componen ts.ecore
RULE butNowIdo
FORALL Component c
MAKE println(c.name);
INFO: Loaded (19509258) platform:/resource/
au.edu.uq.itee.mdavv.wrsa.foxb us.test2code/transformations/

Re: Inaccessible Instances

2007-11-02T01:17:45Z

Does not fix it (See below). However, the parser detects the ambiguity
when I include the other namespace, saying that 'Component' matches in
both spaces.
TRANSFORMATION inaccessible: src -> tgt
NAMESPACE http:///au/edu/uq/itee/mdavv/w rsa/foxbus/modelManagement.eco re
NAMESPACE http:///au/edu/uq/itee/mdavv/w rsa/foxbus/designtime.ecore

Re: Inaccessible Instances

2007-11-02T00:26:20Z

The problem is that the Components is in
http:///au/edu/uq/itee/mdavv/w rsa/foxbus/designtime/componen ts.ecore,
not http:///au/edu/uq/itee/mdavv/w rsa/foxbus/designtime.ecore -- it's
in a nested package.
The fully-qualified name will work.
RULE nowYouDont
FORALL ::designtime::components::Comp onent c

Re: Blocker: Tefkat does not find any model content

2007-11-02T00:12:30Z

Var Groups are a very recent addition to Tefkat (i.e., they were added
for the current build).
After some further digging, the issue is related to the difference
between an unset String attribute, and a String attribute set to the
empty string (fixed in next release). If you're up to hand-editing
the tefkatconfig file, you can remove the varGroup="" bits and all

Inaccessible Instances

2007-11-02T00:03:34Z

I have a problem with rule matching. I have an MM structured into
recursive packages. The source is a resource that is strictly
contained (Everything in one root element, stored in one xmi file). I
find that I am able to match elements defined in the package that
contains the root element, but in none of the other packages using a