Wanted to get feedback before starting to implement...
;)
The current support for loading deployment units has several special
cases
to deal with loading from the network e.g. in
SARDeployer.parseXMLClasspath(), NetBootHelper.getDefaultListUrl() or
even
HttpURLDeploymentScanner itself.
Specifically what are the special cases? It has been a while since I
looked, refresh my memory. Some work still needs to be done to remove
all of the http: specific bits are replace them with plain
URLConnnection bits.
I would like to make changes to simplify this and at the same time
offer
additional flexibility.
The main change would be to factor out the URL listing functionality
into
helpers with a factory to create them based on the scheme. Examples
would
be:
* file: using java.io.File as now
* http(s): using DAV
* http: using the current listing mechanisms (if still applicable)
others could be added as needed (e.g ftp:)
Explain some of the details here.
The DAV client would allow JBoss to be netbooted from any web server
supporting DAV, either directly (e.g. Tomcat 4.1, Apache+mod_dav or
even
IIS) or via a helper servlet (which could read either the content of
its war
or config of its host).
I am all about more network proto support. Can this be abstracted into
a URL Handler & used with a URLConnection?
This change would isolate the SARDeployer and the
URLDeploymentScanner's
from the different URL schemes and remove the special cases.
Again, explain some details please.
=]
--jason
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
