|
| Re: why interface package cannot be deduced from qualified name? [message #8215 is a reply to message #8124] |
Wed, 19 March 2008 23:19   |
 Eric Dillon
Messages: 103
Registered: July 2009 |
Senior Member |
|
|
Hi Marc,
this is an OSSJ-ism that was introduced at the begining allowing to have 2
separate namespaces for the model and the corresponding OSSJ interface.
As we moved forward we kept that in the current OSSJ plugins, although this
should really be a property on the corresponding plugin.
The "Interface Package" will be used when generating an API with the JVT
OSSJ plugin. For any other plugin, it is up to the plugin's implementation
to use it or not.
As we are working on migrating the implementation of Tigerstripe to EMF we
are trying to separate these OSSJ-ism from the "core" metamodel. However,
this is work in progress, so in the meantime you'll have to bear with us I'm
afraid.
Eric
"Marc Flauw" <marc.flauw@hp.com> wrote in message
news:e6f4aa715f4dce9d0c641a974c3c59dd$1@www.eclipse.org...
> Hello,
>
> When defining an object, it needs to be put in a specific namespace, like
> org.tmforum.tip.fm.sa that drives its qualified name:
> org.tmforum.tip.fm.sa.ImpactPatterns.
>
> But hidden on the details pane, there is another field called Interface
> package. When creating a new object, the Interface package seems to
> inherit from the default one set at project level and is not using the
> current one by default.
> Seems odd, esp like me when you have messed up with the default and the
> objects end up with strange java packages.
>
> Best regards,
>
> Marc
>
|
|
|
|
| Re: why interface package cannot be deduced from qualified name? [message #562599 is a reply to message #8124] |
Wed, 19 March 2008 23:19 |
Eric Dillon
Messages: 103
Registered: July 2009 |
Senior Member |
|
|
Hi Marc,
this is an OSSJ-ism that was introduced at the begining allowing to have 2
separate namespaces for the model and the corresponding OSSJ interface.
As we moved forward we kept that in the current OSSJ plugins, although this
should really be a property on the corresponding plugin.
The "Interface Package" will be used when generating an API with the JVT
OSSJ plugin. For any other plugin, it is up to the plugin's implementation
to use it or not.
As we are working on migrating the implementation of Tigerstripe to EMF we
are trying to separate these OSSJ-ism from the "core" metamodel. However,
this is work in progress, so in the meantime you'll have to bear with us I'm
afraid.
Eric
"Marc Flauw" <marc.flauw@hp.com> wrote in message
news:e6f4aa715f4dce9d0c641a974c3c59dd$1@www.eclipse.org...
> Hello,
>
> When defining an object, it needs to be put in a specific namespace, like
> org.tmforum.tip.fm.sa that drives its qualified name:
> org.tmforum.tip.fm.sa.ImpactPatterns.
>
> But hidden on the details pane, there is another field called Interface
> package. When creating a new object, the Interface package seems to
> inherit from the default one set at project level and is not using the
> current one by default.
> Seems odd, esp like me when you have messed up with the default and the
> objects end up with strange java packages.
>
> Best regards,
>
> Marc
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.14668 seconds
] 
Search
Help
Register
Login
Home
