Re: Sturts - Custom Tags and limitations

[Benjamin Stewart]

Just strange that I have always thought of a setter and getter with 
reference to setting or getting a class field.

But if I have a get function that is in a bean that is not used in 
reference to a particular field, feels wrong to me.

For example I have a class person which has field name I am happy to 
have getName, setName. But if I have a function called isHuman which 
runs off and check my database which contains a list of humans, if it 
was to be bean accessible I would have to call it getIsHuman  right ??

Ben

Steve Raeburn wrote:

The zero argument and serializable requirements are for there for persisting
and re-instantiating beans. I guess without the zero arg constructor it's
not *technically* a bean but I won't tell if you don't ;-)
As long as you follow the bean naming conventions for setters & getters
you'll be OK.
Steve

 

-----Original Message-----
From: Benjamin Stewart [mailto:[EMAIL PROTECTED]
Sent: June 29, 2003 5:23 PM
To: Struts Users Mailing List
Subject: Re: Sturts - Custom Tags and limitations
In order to make our classes bean compliant we would have to change our
constructors so they dont take parameters right ?? That is a pretty
severe limitation, or are you saying just make your method calls bean
compliant?
Ben
Steve Raeburn wrote:

   

Struts (and JSTL) will be happy with a LinkedHashMap as it is a member of
the Collection class hierarchy.
I would not recommend with custom tags unless you need custom
     

functionality.
   

If you really can't change the existing method names you should consider
adding additional methods that are bean compliant (they can just
     

delegate to
   

the existing methods). You should consider deprecating the old methods so
they could be removed in future.
If you can't touch the existing classes at all (why?), think about using
adaptor classes.
Steve



     

-----Original Message-----
From: Benjamin Stewart [mailto:[EMAIL PROTECTED]
Sent: June 29, 2003 4:33 PM
To: Struts Users Mailing List
Subject: Sturts - Custom Tags and limitations
Greetings,
Before I go charging off and make a stack of custom tags, I thought I
would post to the group to make sure I am heading in the right
       

direction.
   

We are devloping an applicaton and we have created the business logic
that is able to fit a number of UI (web, Local application etc). A
number of our classes have methods that are not bean compliant
(addCategory for example). Many of the functions also return objects and
datastructures like linked lists and hash maps. As I understand it
struts is happy to use beans, but if I am using an object and make a
method call that is not bean compliant I am going to have to create my
own tag library to deal with this.
For example, I have a bean function that returns a linked hash map, in
order for me to itterate through this and display an output I will need
to create my own tag library right?
Any advice appreciated.

Regards
Ben Stewart




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




       

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


     

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]