|Re: Xcore 100 EClassifier limit? [message #1456565 is a reply to message #1455787]
||Thu, 30 October 2014 13:44
| Ed Merks
Registered: July 2009
Please open a bugzilla with an Xcore instance that reproduces the
problem so I can have a look. Also have a look in the Error Log; likely
there's a clue there about what's gone wrong. I suspect it's a bug
that's been fixed in the in the pre-SR2 maintenance stream, so please
first try updating from
http://download.eclipse.org/modeling/emf/emf/updates/2.10.x to pick up
that fix. Alternatively, try setting "Initialize by Loading" to fast in
the properties view when you have the package declaration of the *.xcore
selected; hopefully that doesn't generate class files that have too much
byte code, but also should avoid this problem, if my theory is correct.
On 29/10/2014 8:08 PM, Erick Hagstrom wrote:
> Ok, there doesn't seem to be a 100 EClassifier limit. It's a 500
> ENamedElement limit.
> I just created several test .xcore files. One, with 500 class entries.
> All generates well. Add the 501st class and generation of Factory,
> Package, and .util fails. But don't add the 501st class. Stick with
> 500 classes and add a single attribute to any one of them. Gen fails
> Another, with 100 class entries, each of which has 4 attributes. All
> generates well. Add the 101st class (an empty one) and gen fails.
> Leave it in and comment out one of the attributes on one of the other
> classes and gen works again.
> So are there any suggestions on how I can proceed with my excessively
> large .xcore file for my doesn't-seem-so-large project?
Powered by FUDForum
. Page generated in 0.02380 seconds