getRealPath returns null in JBoss 3 beta

[per_nyfelt]

I'm trying to use the Java webstart servlet with JBoss 3 with Tomcat 4.0.2 but it relies heavily on getRealPath() to create a File that is used to get resources and handle versioning etc.

Here's an example

String realPath = _servletContext.getRealPath( path ); // path is /app/lib
File file = new File( realPath ); // this throws a null pointer exception
if( file.exists() && file.isDirectory() ) {
File afile[] = file.listFiles();
...

The documentation on ServletContext says "This method returns null if the servlet container cannot translate the virtual path to a real path for any reason (such as when the content is being made available from a .war archive" and this is definitely the case here since I'm deploying everything in an EAR file but on the other hand this worked without problems in JBoss-2.4.0_Tomcat-3.2.3

Any suggestions would be most appreciated.

[townsendmerino]

I'm in the same situation - will this be fixed?

[jules]

If it's a Tomcat feature/problem, then you are at the mercy of Jakarta - and should be lobbying them.

If you try it with Jetty and find the same problem, I will look at it.

Jules

[dnamiot]

The same is true for Weblogic too by the way :)
The only workaround for us was to deploy unpacked.

>this worked without problems in JBoss-2.4.0_Tomcat-3.2.3
it was unpacked actually by JBoss itself

[opi99]

damn ...

... is there an other way to get this information out?

Is it possible to get an option in jboss where I can say to jboss unpack the war's self or not?

[ppetit]

It works for me with JBoss 3.0.1 and Jetty.
I got it working before with JBoss 3.0.O and Tomcat 4.0.2b2, but it's not working anymore with JBoss 3.0.1 and Tomcat 4.0.4...

Hope this helps
Philippe

[didi]

it doesnot work for me either.

but a small hint for per_nyfelt: you should not use File in a EJB. Use FileDataSource (from javax.activation. instead)

[ppetit]

IMHO, It seems to be an issue due to the fact that Tomcat 4.1.x may now be clustered. So they can't anymore manage absolute path to a file or directory.
It would explain why this method works with previous releases of Tomcat and Jetty...

I can be wrong however...

[didi]

that could be right ....

but how can I handle this now? How do I realize a file upload? Is it only possible to common shared directories? (like /tmp/)

[didi]

that could be right ....

but how can I handle this now? How do I realize a file upload? Is it only possible to common shared directories? (like /tmp/)

[didi]

that could be right ....

but how can I handle this now? How do I realize a file upload? Is it only possible to common shared directories? (like /tmp/)

[didi]

that could be right ...

but how can I handle this now? How do I realize a file upload? Is it only possible to common shared directories? (like /tmp )

[didi]

but how can I handle this now? How do I realize a file upload? Is it only possible to common shared directories? (like /tmp)

[didi]

sorry, some how my browser went crazy.
But the question is still serious