OK, I figured it out. oAW uses the hybridlabs beautifier library, which is based on Jalopy. The key to getting the imports in the generated file is to make the template print out the entire class name like this:
java.util.Map Then the beautifier will notice the full path, create an import statement, and use the short name in the code (like "Map"). The documentation is here: http://www.hybridlabs.org/data/hybridlabs-beautifier.pdf --Polly amphoras wrote: > > Hi, > > How does sculptor/oAW generate import statements in a Java file? > DomainObject.xpt does not seem to do anything with generating imports, yet > they are always there in the generated file. How does this magic happen? > > The reason I ask is because I am trying to generate a Java class with some > logic in it. This Java class references some of the enums that I defined > in the model.design. My generated file magically has most of the imports > for the enums, but it is missing one. Any idea why that might happen? > > Thanks, > Polly > -- View this message in context: http://www.nabble.com/-Sculptor--generating-import-statements-tp18492684s17564p18495148.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
