Hi Karthik -
I would use prop wherever possible, and at least consider writing new
methods in Java for the places that you can't currently use it. Not only
does that increase the amount of code that you can unit test, but you'll see
definite speed improvements. Changing BeanForm to use prop
Great! thank you all. We will also adopt a similar approach
thanks
Karthik
On 12/18/06, DJ Gredler [EMAIL PROTECTED] wrote:
Hi Karthik -
I would use prop wherever possible, and at least consider writing new
methods in Java for the places that you can't currently use it. Not only
does that
use prip where you can for its speed and ognl where you can't.
--sam
On 12/15/06, Barry Books [EMAIL PROTECTED] wrote:
I don't know about the norm but prop does not have all the
functionality of ognl. It's probably faster at what it can do. So if
you need speed or believe in optimizing early
Should i be using tapestry prop in place of ognl? Is this norm when
developing with tapestry?
http://howardlewisship.com/tapestry-javaforge/tapestry-prop/
Please do let me know as we are at a very early in the project and would
like to adopt the best option.
thanks,
Karthik
I don't know about the norm but prop does not have all the
functionality of ognl. It's probably faster at what it can do. So if
you need speed or believe in optimizing early then you'll need both.
Or
You can use prop for everthing, but you'll need to write to write java
methods to handle the
