That will be enough. We need usually one at maximum two of such
strange definition in one project.
TNX
Pavel
On Thu, Jul 8, 2010 at 8:09 AM, Patrik Nordwall
<patrik.nordw...@gmail.com> wrote:
>
> Yes, Map definitions might need some improvements. I'm not sure we should
> support nested type parameters due to the added complexity, but let us take
> a look at it. Right now I think you can do something like this by defining
> your own javaType
>
> In sculptor-generator.properties
> javaType.OrgStructPair=org.foo.domain.Pair<org.foo.domain.Boss,
> List<org.foo.domain.OrgStruct>>
>
> In model.btdesign:
> Service CompanyService {
> Map<org.foo.domain.OrgStruct, OrgStructPair> getOrgStruct;
> }
>
> Entity Boss {
> }
>
> Entity OrgStruct {
> }
>
> Pair will have to be a plain old hand-written class.
>
> /Patrik
>
>
> PaloT wrote:
>>
>> Hi Patrik,
>> I found in syntax file that we are limited in DslComplexType with
>> number of parametric parameters. Do we really need such complex
>> syntax?
>>
>> Shouldn't we have just:
>> DslComplexType:
>> (type=DslType) |
>> ("@"domainObjectType=[DslSimpleDomainObject]) |
>> (type=DslType"<" (complexTypes+=[DslComplexType]")? (","
>> complexTypes+=[DslComplexType]")*>");
>>
>>
>> This will allow to return more complex types specially from Service
>> methods. Is it also necessary to limit Map to have key parameter only
>> of DslType? Is it some hibernate constraint?
>> If it's too complicated for modeling should we support up to 3
>> parametrized types? For example:
>> HashMap<@OrgStruct, Pair<@Boss, List<@OrgStruct>>>
>>
>> I don't know how complex it will be and how fast for parser and xtext
>> framework. We can live without this but it will be good addition.
>>
>> TNX
>>
>> Pavel
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by Sprint
>> What will you do first with EVO, the first 4G phone?
>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
>> _______________________________________________
>> Fornax-developer mailing list
>> Fornax-developer@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/fornax-developer
>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/ComplexType-tp29097250s17564p29100033.html
> Sent from the Fornax-Platform mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Fornax-developer mailing list
> Fornax-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fornax-developer
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
