>
>
>What is this problem? I think any reproducible 1-1 mapping will work, but I
>don't know of any other than using the whole URL.
>david jencks
>
The problem is that on windows (ick) it limits the length of a filename
unreasonabily. This problem shows up with the currently deployment
scheme of taking the entire URL of a deployment and using that as the
path under the ${jboss.server.home.dir}/tmp/deploy directory. This
means that the length of the filename is now
"${jboss.server.home.dir}/tmp/deploy".length + url.toString.length. If
this is > then the giving crappy limit on win32 we are hosed.
It would be *safer* to employ a different method for the url suffix
bits, as the first part is a sunk cost. Sure we can tell users to run
from a different directory, using a shorter name, but we can't really
control the URLs that come in for deployment.
I personally have the following setup (which I don not think unreasonable):
base project dir: /home/jason/workspace/jboss/jboss-all (prefixed by
c:\cygwin for winblows)
This means that the final value for ${jboss.server.home.dir} is:
C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2\server\default
Now the deployments live under conf/ and deploy/ relative to this path,
longest filename currently seems to be:
new-hsqldb-default-service.xml
which makes the actual deployment file:
C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2\server\default\deploy\new-hsqldb-default-service.xml
Now this full path will be constructed under:
C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2\server\default\tmp\deploy
making the full deployed filename:
C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2\server\default\tmp\deploy\C:\home\jason\workspace\jboss\jboss-all\build\output\jboss-3.0.0beta2\server\default\deploy\new-hsqldb-default-service.xml
with translations applied, I am too lazy for this at the moment.
Now in comes the cache repository. If I employed the same scheme, then
the deployment URL which is given to MainDeployer would be about as long
as the tmp\deploy version... which would then become even longer once it
was copied to tmp\deploy.
See what I mean? If this is all because of security policies, then I
suggest we need to find another way to implement the policy, perhaps
even punting easier configuration until 1.4 is the defacto. If not
please explain why we need this, cause I just don't understand.
These insanely long filenames are going to bite us... they have already
bitten me several times.
There must be a better solution, which does not force users to hack up
there environment to work around this OS limitation... perhaps there are
other OS'n out there which have similar limits... who knows. Lets not
stick our necks out to find out.
Can you please explain all of the details why we need these long
filenames. I don't get it.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
