Thanks Lance,
These options are all great... helpful. I am interfacing with the author and
trying to communicate what I have identified is a show stopper for the users of
their library.
I think some rules of thumb need to be agreed upon especially with regard to
owness.
So it should really be up to the component library author to self contain and
secure it's library from coming apart at the seams no matter who's camp it
lands in.
Any best practice recommendations for component library developers would be
helpful. It seems like a wide open issue. I wonder if tapestry recommends or
advises special attention to this.
But you have been a tremendous help so far.
Thanks
I am in a holding pattern wondering whether I should modify my webapp code or
wait til something changes for the component library author.
- cheers
Ken
