Re: How to decorate external Web sites?

Hi there,

Thanks for your answer...

> AFAIK the standard procedure is:
> 1. checkout the sitemesh sources.
> 2. update the documentation/sources with your content.
> 3. create a patch from those changes.
> 4. create a JIRA/tracker issue and attach the patch to that ticket.
> 5. publish the ticket number here, so that the users can vote for it
>
> I know it's too much work, and there should be other simplers ways to include contributions,  but this is how it mostly works with all OS projects for user contributions :( .

It's not a problem, I don't have all my programming/editing
environment at home, holidays yeah!, but I thought modifying the
documentation might have a different approach than modifying the
source code "per se".

> IMHO the WIKI is not the right place to do it because,
> the OpenSymphony WIKI is full of spam and is getting more each day: just look at the
> "Tonic" WIKI space :(.

Ouch, I didn't know that. Wiki-styled documentation is quite useful
but it has its own share of problems. I use confluence myself for our
framework, but I don't allow any conttribution but from the well-know,
registered users.

> The problem is that SiteMesh must be JDK1.4 compatible (even if a great amounth of
> it's users already moved to 1.5).
> IMHO the HTTPClient dependency is too much just for timeout handling.
> If it would be possible to isolate only the function that delivers the timeout,
> it would be fantastic.
> If not, than conditioning this feature to the presence of JDK 1.5(for execution, not
> compilation) would also be OK.

Well, I have to run my webapps under JDK1.4 also and having the time
out there is quite necessary (still wondering why it took Sun around 6
years to fix that)... I don't think that feature would be easy to
isolate, as HTTPClient needs to replace protocol handlers with their
own to be able to do that, so requiring JDK1.5 might be the only
option. I will think if some kind of adaptative system could be added
(checking Java 5, then HTTPClient presence, then issuing a BIG
warning!)... we'll see.

Cheers!
D.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]