Bugzilla – Full Text Bug Listing
| Summary: | EPackage-s name does not accept dots | ||
|---|---|---|---|
| Product: | [Modeling] EMFT | Reporter: | Gabriele Mising name <gdelprete> |
| Component: | Texo | Assignee: | Martin Taal <mtaal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
Yes previously the model was not validated before generating code, resulting in unclear behavior if there are errors in the model. So I added model validation before model code generation. This is the same as in the EMF genmodel. I checked and also the EMF genmodel does not allow dots in the package name. So I don't want to change this validation. I decided to make a change to make it possible to have an epackage names with dots as it is really a pain when you have xsd's with namespace values with dots (which is quite logical to have). The solution is available in the latest build of Texo today. |
An EPackage name cannot be set to string containind dot ('.') characters. This used to work with the versions until mid-May 2011 while now (as of version 0.1.0.v201106191954 it makes Code Gen fail. The message is: Click the details button for more information, and check the Error Log view for any exceptions. Invalid EPackage: a.domandaaccr01 Diagnosis of file:<your path>/<your ecore>#/ The name 'a.domandaaccr01' is not well formed Note that from the book "EMF Eclipse Modelling Framework", Second Edition, it appears that EPackage-s should not have dots in their name as EPackage-s can be nested and each of their name may end up being a component in a dot-separated Java package name. So it should be first decided whether dots are to be allowed or not.