You are going to kill me, but I take that risk.
Aren't generator properties just Application level hints. What about:
Application myApp hint="GenerateGapClass" {...
And than of course:
Entity SomeEntity hint="NoGenerateGapClass" {...
Advantage should be to have "GenerateGapClass" for example on Module.
What about "scaffold"? Put in on Application and all Entities became scaffolded.
Isn't this same mechanism?
Should we build this extension functions some generic way that for
example when I define GenerateGapClass on Application and than I put
"NoGenerateGapClass" on Module and ask in entity template inside this
module hasHint("GenerateGapClass") it will return false?
Is it too far?
Pavel
On Tue, Jun 30, 2009 at 12:23 PM, Patrik
Nordwall<patrik.nordw...@gmail.com> wrote:
>
> I thought of it as a plain string, but your idea with parameters and
> separators is even better.
>
> We add convenient extension functions so it could look like this:
>
> «AROUND templates::DomainObject::jpaAnnotations FOR Attribute»
> «IF hasHint("xml")»
> �...@javax.xml.bind.annotation.xmlelement(required=true«IF
> getHintParam("xml", "default") != null»,
> defaultValue=getHintParam("xml", "default")«ENDIF»)
> «targetDef.proceed()»
> «ENDIF»
> «ENDAROUND»
>
> Oliver has done parsing for the validation that we might be able to reuse.
>
>
> /Patrik
> --
> View this message in context:
> http://www.nabble.com/New-concept-tp24252062s17564p24269489.html
> Sent from the Fornax-Platform mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Fornax-developer mailing list
> Fornax-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fornax-developer
>
------------------------------------------------------------------------------
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
