2009/7/1 Simon Denier Simon.Denier@inria.fr

On 1 juil. 09, at 15:08, Alberto Bacchelli wrote:

Hi everybody, [...]

"Unhandled exception: Unknown character".

I'm not a fine connoisseur of iPlasma so here is some general tips:

Did you try to debug the exception, see what is the character in question?

Yes, I tried. The problematic character seems to be " [ ". I searched for it both in the correctly-imported MSE files and in the not-correctly-imported ones. In the latter case, I see that there are many fields like this:

(name '[]')

which are not present in the correctly-imported MSE files.

You can also check file format, see what kind of return line characters it uses...

Carriage return shouldn't be a problem since some MSE files are correctly imported.

Finally, you can try to generate two mse of the same version of JRuby with the two iPlasma and compare them with a file merge (might not work at all because the content and the order will be different, but maybe you can catch something)

I have only one iPlasma version (the one that is available here: http://loose.upt.ro/iplasma/download.html) are there more? Where can I find them?

The first releases are correctly imported in Moose.

If you want to help me with this problem, you find an example of a problematic MSE here : http://www.inf.unisi.ch/phd/bacchelli/research/20080720_jruby-1.1.3.mse and an example of a not-problematic MSE here : http://www.inf.unisi.ch/phd/bacchelli/research/20060802_jruby-0.9.0.mse

-- Simon

Alberto

Hi everybody,

I investigated in more detail the issue of the annotation, and maybe I found the problem.

I searched in the JRuby sources for the text 'JRubyMethod' and I found it used as an annotation many times. Here is an example (from the class: org.jruby.RubyZlib):

@JRubyMethod(name = "zlib_version", module = true, visibility = Visibility.PRIVATE) public static IRubyObject zlib_version(IRubyObject recv) { return ((RubyModule)recv).fastGetConstant("ZLIB_VERSION"); }

So, I supposed that probably somewhere (maybe in iPlasma, maybe in Moose) such complex annotations weren't correctly managed.

For this reason, I parsed the not-correctly-imported MSE file, and removed all the FAMIX.AnnotationInstance. After this operation, the resulting MSE file can be easily imported into Moose.

At this point, the next step should be finding the component which is not correctly handling those annotations. As I am not expert of Moose and iPlasma, I don't think I can help a lot more than this bug-report. In addition, for my needs I can just remove the FAMIX.AnnotationInstances.

However the script I created is not fast at all... can I use the MSEParser to remove FAMIX.AnnotationInstance? Are there examples for such a thing?

Thank you, Alberto

2009/7/1 Alberto Bacchelli alberto.bacchelli@usi.ch

In addition, I saw that in the not-correctly-imported file, there are annotations like this:

[...]

(FAMIX.AnnotationInstance (id: 121052) (name 'JRubyMethod') (belongsTo (idref: 121050)) (name '[]') )

isn't it strange that those AnnotationIntances have more than one name?

[...]

Hi,

Thanks for reporting.

It looks like a problem in the iPlasma parser. Could you provide me with the java file that causes the problem? Like this I can pass it forward for debugging.

Cheers, Doru

On 2 Jul 2009, at 12:16, Alberto Bacchelli wrote:

Hi everybody,

I investigated in more detail the issue of the annotation, and maybe I found the problem.

I searched in the JRuby sources for the text 'JRubyMethod' and I found it used as an annotation many times. Here is an example (from the class: org.jruby.RubyZlib):

@JRubyMethod(name = "zlib_version", module = true, visibility = Visibility.PRIVATE) public static IRubyObject zlib_version(IRubyObject recv) { return ((RubyModule)recv).fastGetConstant("ZLIB_VERSION"); }

So, I supposed that probably somewhere (maybe in iPlasma, maybe in Moose) such complex annotations weren't correctly managed.

For this reason, I parsed the not-correctly-imported MSE file, and removed all the FAMIX.AnnotationInstance. After this operation, the resulting MSE file can be easily imported into Moose.

At this point, the next step should be finding the component which is not correctly handling those annotations. As I am not expert of Moose and iPlasma, I don't think I can help a lot more than this bug- report. In addition, for my needs I can just remove the FAMIX.AnnotationInstances.

However the script I created is not fast at all... can I use the MSEParser to remove FAMIX.AnnotationInstance? Are there examples for such a thing?

Thank you, Alberto

2009/7/1 Alberto Bacchelli alberto.bacchelli@usi.ch In addition, I saw that in the not-correctly-imported file, there are annotations like this:

[...]

(FAMIX.AnnotationInstance (id: 121052) (name 'JRubyMethod') (belongsTo (idref: 121050)) (name '[]') )

isn't it strange that those AnnotationIntances have more than one name?

[...] _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every thing has its own flow."

Thanks, I will take a look.

Cheers, Doru

On 7 Jul 2009, at 17:49, Alberto Bacchelli wrote:

Sure!

Here you can find the file: http://www.inf.unisi.ch/phd/bacchelli/research/RubyZlib.java

This file is only one example, but other similar files generate the same error. If you need you can find the whole source code here:

http://www.inf.unisi.ch/phd/bacchelli/research/20080720_jruby-src-1.1.3.tar....

Thank you!

Ciao, Alberto

2009/7/7 Tudor Girba girba@iam.unibe.ch Hi,

Thanks for reporting.

It looks like a problem in the iPlasma parser. Could you provide me with the java file that causes the problem? Like this I can pass it forward for debugging.

Cheers, Doru [...]

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Every now and then stop and ask yourself if the war you're fighting is the right one."

Hi Doru,

I (successfully) tried to reproduce the problem again:

- I used the sources that you can find in http://www.inf.unisi.ch/phd/bacchelli/research/iPlasma/20080720_jruby-src-1.... - I followed the steps in http://moose.unibe.ch/docs/faq/importJavaWithiPlasma - I exported the mse file, which you can also find in http://www.inf.unisi.ch/phd/bacchelli/research/iPlasma/jruby-1.1.3.mse - I tried to import it in Moose, in VisualWorks 7.6nc

The problem is still there: "Unhandled exception: Unknown character". If you look at my previous mails, you can see how I tried to spot the cause of this exception. At the end, I noticed that: It seems that iPlasma generates a mse file that it considers valid, however Moose on VW 7.6nc does not agree :) This issue is probably caused by annotation (in the java sense).

Ciao, Alberto

2009/7/21 Tudor Girba girba@iam.unibe.ch

Hi Alberto,

I tried to reproduce the problem with the new inFusion, but I could not reproduce the problem. Could you try again following: http://moose.unibe.ch/docs/faq/importJavaWithiPlasma

Cheers, Doru

[...]

No problem Tudor!

So.. I tried to parse the system using inFusion. It seems that it generates "more correct" a mse file, but still not perfect:

I followed the instructions and generated the mse file [ http://www.inf.unisi.ch/phd/bacchelli/research/iPlasma/http://www.inf.unisi.ch/phd/bacchelli/research/iPlasma/20080720_jruby-src-1.1.3.tar.gzinfusion-jruby-1.1.3.mse ]. When I try to import it in VW based Moose: - it correctly does the first pass ( "Reading 17 MB from input stream..." ) [and this was the part that raised the exception using the mse file generated by iPlasma] - it correctly does also the second one ( "Importing 105029 elements..." ) - it raises an exception during the third pass ( "Importing attributes and assocations..." ): "Unhandled exception: CodeFoo.AssertionFailure"

looking at the calls before the exception, you can see a message "mmSetAll:collection:" sent to a "SCG.Moose.FAMIXAnnotationInstance" object. So, probably, the annotations are still problematic.

Thanks for your help! Alberto

2009/7/22 Tudor Girba girba@iam.unibe.ch

Hi,

Ohh, I am sorry but I gave you the wrong url :(

Could you try again following this: http://moose.unibe.ch/docs/faq/importJavaWithinFusion

Cheers, Doru

On 22 Jul 2009, at 08:58, Alberto Bacchelli wrote:

...

Hi Doru,

I (successfully) tried to reproduce the problem again:

• I used the sources that you can find in

http://www.inf.unisi.ch/phd/bacchelli/research/iPlasma/20080720_jruby-src-1....

...

• I followed the steps in

http://moose.unibe.ch/docs/faq/importJavaWithiPlasma

...

• I exported the mse file, which you can also find in

http://www.inf.unisi.ch/phd/bacchelli/research/iPlasma/jruby-1.1.3.mse

...

• I tried to import it in Moose, in VisualWorks 7.6nc

The problem is still there: "Unhandled exception: Unknown character". If you look at my previous mails, you can see how I tried to spot the cause of this exception. At the end, I noticed that: It seems that iPlasma generates a mse file that it considers valid, however Moose on VW 7.6nc does not agree :) This issue is probably caused by annotation (in the java sense).

Ciao, Alberto

2009/7/21 Tudor Girba girba@iam.unibe.ch Hi Alberto,

I tried to reproduce the problem with the new inFusion, but I could not reproduce the problem. Could you try again following: http://moose.unibe.ch/docs/faq/importJavaWithiPlasma

Cheers, Doru [...]

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

-- www.tudorgirba.com

"Beauty is where we see it."

---

Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev