|
|
|
|
|
|
Re: JSF tools M5 - EL Syntax checking [message #471503 is a reply to message #471501] |
Tue, 21 March 2006 06:34 |
Mario Ivankovits Messages: 23 Registered: July 2009 |
Junior Member |
|
|
Hi!
>> In other words, beside "create bean" this will be a "associate class".
>
> Can you elaborate a little more on "associate class"? Are you
> suggesting that the user would be able to have a referenced-bean-like
> mechanism that is stored outside the faces-config that would allow them
> to say: "use this class for content-assist, validation etc."?
Yes, this association should not influence any config file. Just to help
the code assist.
You NEVER EVER can handle all cases automatically. Think of custom
components - sure its a common standard to use "var=" to define a local
scoped variable, but its not always easy - say, often its not even
possible - to determine the class behind this var automatically.
Its even hard to detect the class for a dataTable as the values= points
to a DataModel or a simple List - you need a datasample to get in touch
with the class.
My suggestion also allows us to associate a class to the el-string if a
bean is set from the application directly into the request/session map.
There might be no configuration, not even a component - just a bean
somewhere laying around.
This is why I thought about such a association feature.
Wherever you store this mapping, I think the key should be something
like "filename/el-reference-name=className".
I think, this will be a killer feature.
Ciao,
Mario
|
|
|
|
|
|
|
|
Re: JSF tools M5 - EL Syntax checking [message #596659 is a reply to message #471501] |
Tue, 21 March 2006 06:34 |
Mario Ivankovits Messages: 23 Registered: July 2009 |
Junior Member |
|
|
Hi!
>> In other words, beside "create bean" this will be a "associate class".
>
> Can you elaborate a little more on "associate class"? Are you
> suggesting that the user would be able to have a referenced-bean-like
> mechanism that is stored outside the faces-config that would allow them
> to say: "use this class for content-assist, validation etc."?
Yes, this association should not influence any config file. Just to help
the code assist.
You NEVER EVER can handle all cases automatically. Think of custom
components - sure its a common standard to use "var=" to define a local
scoped variable, but its not always easy - say, often its not even
possible - to determine the class behind this var automatically.
Its even hard to detect the class for a dataTable as the values= points
to a DataModel or a simple List - you need a datasample to get in touch
with the class.
My suggestion also allows us to associate a class to the el-string if a
bean is set from the application directly into the request/session map.
There might be no configuration, not even a component - just a bean
somewhere laying around.
This is why I thought about such a association feature.
Wherever you store this mapping, I think the key should be something
like "filename/el-reference-name=className".
I think, this will be a killer feature.
Ciao,
Mario
|
|
|
Powered by
FUDForum. Page generated in 0.05393 seconds