Re: [ccmtools-devel] source reorganization ideas

[Robert L. <rle...@sb...>]

Egon Teiniker wrote:
> 
> At this point (using the painful MDR stuff) I think the MDR/ directory
> should be put into a separate java_environment source tree and a
> script (or Ant) should copy the *.jar files to
> <ccmtools-install-path>/lib at build/install time - because they are
> like the antlr.jar file. A working MOF-JMI-generator would be a
> perfect dream ;-) 

Yes, a very good idea!


> 
> Robert, you have created the OCL.MagicDraw.xml.zip metamodel file, and
> you have generated, compiled and packaged the
> JMI interfaces to the oclmetamodel.jar file.
> The oclmetamodel.jar file together with the mdr01.jar file are used by
> the OCL parser/generator to build/use the OCL model - right?

Yes.


> 
> I think that (if we would have a pure OCL metamodel library, without
> the MDR stuff) this package should be put in ccmtools/metamodel/ocl
> (corresponding to the package name).

Or ccmtools/Metamodel/OCL (corresponding to the name of the IDL model).


> But, using the MDR stuff in a offline manner, we should put the files
> in the java_environment source tree.

Ok.


> 
> I also think that it would be nice to have a structure like that:
> OCL
>> -- parser
>> -- generator
> `-- utils

Yes, I think it's better to have an OCL source tree
than a separate OCLParser directory. It should be now problem
to extract the parser from utils and remove the circular dependencies.


> 
> I played with Ant and made a build.xml file that can be used to build
> both the dtd2java.jar and the uml2idl.jar file (containing
> uml_parser). Also, I will try to make a build.xml file to build the
> whole ccmtools (parallel to the autotools build process ;-)

Excellent!


> 
> Maybe, we can put the dtd2java tool into the java_environment source
> tree. There, we will use Ant to build the java source and install the
> *.jar file in <ccmtools-install-path>/lib (in the same way as we copy
> the mdr01.jar and oclmetamodel.jar files).
> The dtd2java tool is so flexible that it may be used in a standalone
> way too. But, that's just an idea...

A good idea.


> Thus, after make install, the <ccmtools-install-dir>/lib directory
> should contain:
> antlr.jar, oclmetamodel.jar, mdr01.jar, dtd2java.jar and ccmtools.jar
> (containing uml_parser and uml2idl)

I think there are two possibilities:

1) Put all the code of the java_environment source tree into ccmtools.jar
   (except oclmetamodel.jar, mdr01.jar). No "dtd2java.jar" file.

2) Create a Jar file for each main package.

For ccmtools users (and developers), it would be more comfortable
to create one Jar file (ccmtools.jar).


> I vote for a java_environment source tree (like the cpp_environment)

Yes!


> 
>> *) make our own MOF-JMI-generator => no need for MDR tools or extra
>>    jar-files =>  create an independent package "ccmtools/Metamodel/OCL"
> 
> Great, when can you start...?

Well, it's not that difficult. We could use 'dtd2java' to create
a MOF model, convert UML to MOF (no UML editor has a MOF mode) and
use the JMI specification to build Java-interfaces and classes.

I would (and could) do the work, but the problem is: time.

I have to finish the DbC component generator and my master thesis.
My contract with Salomon ends this month, so I don't want to spent
more time with another tool (like dtd2java and uml2idl), which
is not part of my master thesis.


Bye