>
>
>|I just realized how simple it would be to do all of the same
>|functionality that DDS does and retain any URL capabilites in the same
>|component...  I was so into the local/directory only thing that I did
>|not see it.
>|
>|I will add URLDeploymentScanner tomorrow...
>
>scanning URLs is not simple, getting the last modified on a URL is trivial.
>

True, but I don't think that we want to do much more than that, as 
anything else is really protocol specific.  For example, consider a 
FTPDeploymentScanner, which would work similarly to 
DirectoryDeploymentScanner, but use the FTP protocol to get those file 
information.

Similarly, an HTTP version could be tossed together which would work off 
of FTP sites that are exposed through HTTP.

In short, this type of protocol specific fluff should be left to a 
specialized implementation.

What I meant about UDS being simple is that users specify a list of 
URLs.  If the URL protocol is file, and the file file it refers to 
exists and is a directory, then we can look for more files, else just 
treat the URL/non-directory file as a deployable.

>However before we get there, we need to make sure that the deployers work
>for url based deployments.
>
>Do you want to try to make the real URL based deployment work? I made it
>work in 3.0 pre-alpha but since then "earth bound filesystem" dirs creep
>back in.
>

I am not sure exactly what you are refering to here.  Can you be more 
specific by what you mean by "earth bound filesystem".  I know that 
referes to a local fs, but where is the dependency?

For example, there is practically no need for any reference to any of 
the base directories in the current DDS.  It is only used currently to 
generate absolutes... which I really believe should be handled elsewhere.

MD, is bound to the local fs, as it needs to unpack stuff...

Can you explain more please?

>|> I was also not planning on letting DeploymentInfo seep into this
>|> layer... but after thinking and attempting to implement this in a
>
>that is good, don't change that, I don't know what you think it is a problem
>(and don't bother answering in 3 volumes, it is a minor point).
>

The deployment system needs some work... perhaps you don't see it yet... 
but you will. =)

>|> I think that this could be fixed up with a combonation of David's xslt
>|> ideas + the Deployment/DeploymentManager bits I was talking about when
>|> I mentiond DeploymentScanner in the first place.
>
>
>don't
>

I still believe this all could be cleaned up and simplified dramatically 
by using the factory pattern here, where the MD is a factory and primary 
controller for Deployments.

There are still some details to work out, but they will settle in 
time... and once I understand better what David is thinking about.

>|> For DDS, since it is file specific I removed the small bits of code
>|> which got the last modified time from an opened connection.  The
>|> reason I did this was to keep the DDS simple by making it only have to
>|> worry about files and that is it.
>
>DDS WAS already URL/File but really we should abstract deployment location,
>wasn't there something in netbeans that abstracted files?  But first making
>it work with URL based AT ALL is the step.
>

MD was (sort of), not DDS.

You lost me on the rest of that.  Isn't deployment location a URL?

Netbeans has a FileSystem api, though I am not sure what that buys us 
here... JNDI fs context might do the same job in more portable fashion.

I don't understand what part of the system you are trying to abstract 
from files.  Please explain.

--jason



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to