Jetty

[Rod Widdowson]

Just to report some more on this.

I spent a frustrating couple of hours yesterday trying to see what java-idp-testbed would look like under my proposal.  I began drowning in a mess of classpaths which culminated in a conflict of which jasper to be running.   At that stage I walked away and spent the afternoon on native Attribute filter.  This was a significantly less confusing problem.

Overnight I have come to the conclusion that I need to jettison the idea of doing anything with the testbed (save make it run on Jetty9.3 which is probably a separate project) and concentrate on the integration tests and the embedded users.  There is just so much accreted cruft in the way that we put together our distribution and in the way that the testbed summons up jetty that I end up considering massive reworks on what is effectively a working system: life's too short and we don't have an infinity of resource.

I've not looked at the integration tests, but my assumption is that there is much less incestuous knowledge there than for idp-testbed.

I think that my current thoughts are:

1) New projects for "deployable Jetty" (9.2 and 9.3).  These consist of the Jetty distribution and our jetty-base, plus our ant installer (suitably modified).  These can co-exist inside a standard IdP install (as per the current version of my noted)

2) A small bit of code for use by the integration tests to allow selecting which install to use and set it running.  I'm thinking of using Jetty9.2 for Java7 and jetty 9.3 for Java 8 (with override of course).  It might be nice *(?required?) to have this usable by embedded users.

3) Some maven jiggery pokery to auto-unpack the deployable jetties & and run the ant installers (idp & jetties)*. Specialized properties files  to set up idp.properties and idp.ini

4) (Potentially) deployable tomcats which also can co-exist inside a standard IdP install, extending 2 & 3  appropriately.

This now becomes a tractable problem.

Can we add this to the list for tomorrow?

Rod