The docBase bug exists for 4.0.3SP1 and 4.0.4RC1
To work around this I had to add mkdir calls to my server start task as this
bug entls the docBase not creating the directories needed in order to run.
If a jboss.org guy can bug this that would be nice.
| !-- Start Server--
|
Well thats pretty nasty...
How am I suppose to deploy a product to the field? Assume that all docBase
paths are going to be unique?
Why can't it be relative? Who wrote that code?
I am finding myself having to not only articulate/fabricate the root drive
directory and the install directory
Well I tried the suggested advise and it did not work.
[java] 10:19:26,493 ERROR [StandardContext] Error starting static Resources
[java] java.lang.IllegalArgumentException: Document base
C:\jboss-4.0.4RC1\server\tapestry-proto-1.0\.\work\jboss.web\localhost\MySQLContext
does not
Here is the configuration...
| Context path=/MySQLContext
docBase=C:/jboss-4.0.4RC1/server/tapestry-proto-1.0/work/jboss.web/localhost/MySQLContext
| debug=5 reloadable=true crossContext=true
|
|
View the original post :
Alright, I had to manually goto that directory and reset the readonly access
bit of the directory off
This seems to have resolved the directory thing.
But now I am receiving errors on the resource-ref for the data source.
Can someone elaborate on how this is suppose to be configured. I believe
The docBase problem should be bugged and fixed for win32. I have to manually go
and set the directory access missions after each iteration of build/deploy.
I can understand neglecting win32 for the sake of linux open source... but it
is the shear runnabilty of this stuff on win32 that makes
docBase must be an absolute path which generally requires the drive prefix on
win32. Use C:/the-full-path/MySQLContext/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3927903#3927903
Reply to the post :
