tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Harish Krishnaswamy <hkrishnasw...@comcast.net>
Subject Re: OGNL
Date Wed, 06 Aug 2003 02:27:41 GMT
That would be an awesome feature. I was thinking the other day that the 
only thing that is hard to do with Tapestry is refactoring with all the 
html and xml stuff. May be this feature can be extended later to allow 
refactoring. Cool, exciting.

-Harish

Geoff Longman wrote:

>One of the goals of the new Spindle... I duck now to avoid the
>inevitable "where is it!?!" responses ... is to have a faclility to
>migrate template style component declartions to traditional specification
>based declarations.
>
>ie. MyPage.html...
>
><span
>    jwcid="someId@PropertySelection"
>
>model="ognl:@telepathy.cust_operator.CustOperatorSummary@TeacherTypeSelectio
>nModel"
>    value="ognl:teacherType"
>    submitOnChange="ognl:true">
>...
>
>into
>
>< span jwcid="someId">
>...
>
>with the tapestry stuff moved automagically into MyPage.page
>
><component id="someId"  type="PropertySelection">
>    <binding name="model">
>
>telepathy.cust_operator.CustOperatorSummary@TeacherTypeSelectionModel
>    </binding>
>    <binding name="value">
>        teacherType
>    </binding>
>    <binding name="submitOnChange">
>        true
>    </binding>
></component>
>
>I want this feature real bad 'cuz is using the template decls rocks for
>prototyping
>but it sucks when one has to migrate them by hand.
>
>Geoff
>
>----- Original Message -----
>From: "Vince Marco" <vmarco@mac.com>
>To: "Tapestry development" <tapestry-dev@jakarta.apache.org>
>Sent: Tuesday, August 05, 2003 9:45 PM
>Subject: Re:OGNL
>
>
>  
>
>>>I've tried to get people interested in OGNL, but it seems that it is a
>>>"stealth" project.  People use it within their frameworks and
>>>projects, but it doesn't get any press or recognition :-(
>>>      
>>>
>>Well, so far my experience with OGNL is that it is a real time (and
>>code) saver in the specification files.  It helps me avoid classes
>>where I really shouldn't need one.  Great for bindings.
>>
>>But I do like to limit (if not eliminate) all OGNL expressions from my
>>templates.  My whole excitement about Tapestry is to avoid the same
>>problem I end up with using JSPs and Struts...which is that I end up
>>mixing logic into my HTML.
>>
>>But there are times when expediency wins out, at least in the near term
>>and I use an occasional OGNL expression in the HTML template.
>>
>>I need to get more into OGNL, as I'm sure it can do much more for me.
>>
>>Say, one aspect of Struts I find very annoying is that when I'm using
>>their expressions to access JBs and a null is down the line (ie.
>>"office.city.address.line1" and address is null).  I want to handle
>>this as elegantly as possible in Tapestry without adding a null handler
>>to every JB class.  Can I add the null handler to an abstract class and
>>have it effect instances of inherited classes?  This seems to be an
>>OGNL question.
>>
>>Thanks,
>>
>>Vince
>>
>>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>Vince Marco
>>Enterprise Frameworks, Inc.
>>vmarco@mac.com
>>
>>    
>>
>
>
>
>  
>
>>-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>>
>>
>>
>>    
>>
>
>
>
>  
>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>    
>>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
>  
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message