Hello,
I already saw that when writing the first extension, which is why I ended up
using the GET mechanism to quickly have something working. If you want to
make a second extension, I suggest it to be a real WebDAV one ;)
You should check this as well:
OK. Good luck.
Cheers,
sacha
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]De la part de
Jeremy Boynes
Envoyé : mercredi, 11 décembre 2002 16:56
À : [EMAIL PROTECTED]
Objet : RE: [JBoss-dev] Proposal for changes to URL deployment to clean
up netboot
tisdagen den 10 december 2002 kl 19.03 skrev Jeremy Boynes:
I lean toward A) as there are existing dependencies during boot (e.g.
getopt, gnu-regexp, log4j) but I realise that adding more is
undesirable.
Functionality is desired ... when 'one' dives in a prob on a moving xp
target - the 'one'
Hello Jeremy,
I did the recent netboot changes to allow for HTTP hot-redeployment and
wildcard usage. That was a first step and the usage of WebDAV is a must (I
spoke about this to Greg in Geneva). And I agree, there is an inconsistency
about the root used for file listing: the current advanced
A factory + interface is the way to go, otherwise looks good.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, December 07, 2002 11:59
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.
I would like
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.
