At 11:35 PM 1/19/2005, Paul Smith wrote:
OK, I see. You are trying to provide a full environment through web-start. IMHO that's a waste of time at best, and in the worst case, a source of confusion and bugs. As I understand it, the idea behind web-start is to provide a self-contained application at click of a URL. If several configuration steps are necessary, you might as well download and launch the application through more conventional means.What could happen inside Chainsaw though, is that it could d/l those extra jars and plonk them in the local directory for the user automatically.
Anyway, we have discussed this before and I'll go along with whatever you prefer.
When you say chainsaw could d/l those extra jars, which jar files are you referring to? For instance, to use DBReceiver, you also need the appropriate driver for your databasae system. Surely, we cannot provide these drivers through webstart. The same is true for JMSReceiver. To run JMSReceiver, you need the JMS API (the interfaces) but also the client-side implementation. Again, we cannot provide the client-side implementation through web-start.
I don't see providing a good user experience a waste of time.
Agreed. My point is that if extra jar files are needed and cannot be provided automatically, then the user experience will be worse than the situation where you plainly state that webstart is not suitable for DB and JMS Receivers.
That's the point of a GUI, otherwise it's just easier to use grep, but that's not exactly a good user experience for new people...
Paul
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
