texo webservice support for nested packages [message #999197] |
Fri, 11 January 2013 09:50  |
Eclipse User |
|
|
|
Hi,
I am using nested model packages with the schema <mandator>.<application>.<version>.
To distinguish class names this is required at ecore model level not only at java package name level.
While decoding the qualified classname in ModelUtils.getEClassFromQualifiedName() the segment splitting with the QUALIFIERSEPARATOR is applied just once. Then ePackage.eNS_PREFIX is checked against the extracted qualifier.
In my case having multiple packages with nsprefix v1 this does not help to make the class name unique.
Suggestion split prefix into qualifier components then walk up the epackage hierarchy and check eNS_PREFIX for each component. Or use nsURI but this would break backward compatibility.
Kind regards,
Donat
[Updated on: Fri, 11 January 2013 17:12] by Moderator
|
|
|
|
|
|
|
Re: texo webservice support for nested packages [message #999959 is a reply to message #999408] |
Sun, 13 January 2013 10:19  |
Eclipse User |
|
|
|
Hi Donat,
Okay, it seems somewhat less-common imho, it only occurs with epackages with non-unique nsprefixes and the solution only
works for cases with sub model packages. So I prefer to use something else, like a parameter/option somewhere to work
with truly generic qualifiers based on the nsuri.
gr. Martin
On 01/12/2013 03:17 AM, Donat Mueller wrote:
> Anyway this is not a big issue for me as I have implemented my own ModelOperation subclasses and others probably wont
> care about model subpackages.
>
--
With Regards, Martin Taal
Springsite/Elver.org
Office: Hardwareweg 4, 3821 BV Amersfoort
Postal: Nassaulaan 7, 3941 EC Doorn
The Netherlands
Cell: +31 (0)6 288 48 943
Tel: +31 (0)84 420 2397
Fax: +31 (0)84 225 9307
Mail: mtaal@xxxxxxxx - mtaal@xxxxxxxx
Web: www.springsite.com - www.elver.org
|
|
|
Powered by
FUDForum. Page generated in 0.03855 seconds