cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Watkins, Garry" <>
Subject RE: Tapestry tutorial advice
Date Fri, 09 Jun 2006 13:18:05 GMT
Thanks for the info, I will try doing some of the things mentioned
below.  However, I don't want to patch too far in advance of the final


-----Original Message-----
From: Andrus Adamchik [] 
Sent: Friday, June 09, 2006 5:19 AM
Subject: Re: Tapestry tutorial advice

On Jun 9, 2006, at 1:17 AM, Watkins, Garry wrote:

> I did give it a try with WebObjects, and I had success.  My roadblock 
> there is that, I don't want to process ArrayLists.  I would rather 
> work with NSArray.  I was wondering if you would consider using a 
> factory to do the construction of List objects.  I used aspectj and 
> did trapped the list modification methods that would throw 
> OperationNotSupported errors for NSMutableArrays, therefore a factory 
> could create a NSMutableArray as a list and everything should work 
> afterwards if you use the

You can use custom to customize how
the objects are built. The factory is set on the DataDomain's
EntityResolver. Specifically custom factory will need to tweak how
ToManyListProperty operates to return a subclass of NSArray that
implements ValueHolder interface.

Also I believe you will need to patch the faulting mechanism, that
currently uses static fault singletons in a few places (search for
'Fault.getToManyFault()'), and replace it with ClassDescriptor based

> On another note, I have several patches to submit for the wocompat 
> package, but I was not sure if you wanted them, because you put it 
> into
> RC1 already.

We won't be able to apply them now, but RC also means that the new
release cycle will soon start. Stay tuned.

> Andrus as a person with WO experience, which of the other frameworks 
> do you think works the best?

I like Click. Don't know how representative this is of a "former WO
user" :-)


Confidential & Privileged

Unless otherwise indicated or obvious from its nature, the information contained in this communication
is attorney-client privileged and confidential information/work product. This communication
is intended for the use of the individual or entity named above.  If the reader of this communication
is not the intended recipient, you are hereby notified that any dissemination, distribution
or copying of this communication is strictly prohibited.  If you have received this communication
in error or are not sure whether it is privileged, please immediately notify us by return
e-mail and destroy any copies--electronic, paper or otherwise--which you may have of this

View raw message