So, basically, you're thinking of letting them drop in a whole new webapp that will
walk them through the configuration of their device?
If so.. then that's what I'd do... bundle a war up and drop it in.  Then have an 
indexing
application provide access to that war.  Maybe even load the war through the index.  
There are
security risks of course, and rather severe ones with allowing anyone to drop a war 
file and
have it activated.
Other then that.. I don't know of any easy solution.


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 08, 2004 3:00 PM
> To: Struts Users Mailing List
> Subject: RE: Dynamic extension of web apps
> 
> 
> 
> Hi Jim,
> 
> Sorry  - don't think I was clear...it's not the client that 
> will change -
> in fact that will all be HTML - but the inner works of the app itself.
> 
> Say, for example, we allow users to configure devices through 
> our web app,
> and we want to now allow them to configure a new device.  We 
> want them to
> be able to drop into the webserver the files for the new device - jsp,
> html, XML, .class files - and for it to automatically pick 
> them up without
> restarting the webserver.  Another way to look at it is that 
> the web app
> doesn't know anything about the devices, but just picks up 
> what it finds
> and displays that.
> 
> I guess it links with automatically reloading the 
> struts-config and jar
> files if we add new actions or class files, but may well not 
> be limited to
> this.
> 
> Does that make any more sense?
> 
> cheers,
> 
> David
> 
> 
> 
> |---------+---------------------------->
> |         |           "Jim Barrows"    |
> |         |           <[EMAIL PROTECTED]|
> |         |           m>               |
> |         |                            |
> |         |           07/08/2004 05:03 |
> |         |           PM               |
> |         |           Please respond to|
> |         |           "Struts Users    |
> |         |           Mailing List"    |
> |         |                            |
> |---------+---------------------------->
>   
> >-------------------------------------------------------------
> --------------------------------------------------|
>   |                                                           
>                                                     |
>   |       To:       "Struts Users Mailing List" 
> <[EMAIL PROTECTED]>                                          |
>   |       cc:                                                 
>                                                     |
>   |       Subject:  RE: Dynamic extension of web apps         
>                                                     |
>   
> >-------------------------------------------------------------
> --------------------------------------------------|
> 
> 
> 
> 
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, July 08, 2004 2:00 PM
> > To: Struts Users Mailing List
> > Subject: Dynamic extension of web apps
> >
> >
> >
> > Hi,
> >
> > I need to design a web app that is extensible dynamically.
> >
> > For example, if we decide to support a different device type,
> > we need to be
> > able to drop in info for that device type and have the web
> > app pick it up -
> > these could be files of all different types e.g. jsp's, 
> html, XML, class
> > files etc..
> >
> > Has anyone done this before, or can you point me in the right
> > direction?
> >
> 
> If I understand you correctly (You're looking for a write 
> once, generate
> HTML, WAP or Voice XML files from that) , I believe JSF will 
> help you in
> your problem.  JSF will allow device independence.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to