WSAD error accessing css in jsp

[Jason Kretzer]

Hello all,
Getting a strange error message in WSAD. I am testing my app on the default WSAD server.
I start the server and goto the built-in web browser and access the login.html.
This posts to a servlet which then verifies and forwards to the next window which is a
jsp. When it gets to the jsp, the css it is supposed to use does not get used. I
get this error in the console window

  
[2/10/04 10:46:39:329 GMT-05:00]  96325cb OSEListenerDi E PLGN0021E: Servlet Request Processor Exception: 
Virtual Host/WebGroup Not Found : The web group /css/nyk-style-00.css has not been defined 

In relation to the jsp the css file is ../css/nyk-style-00.css. In the jsp I am using the following to load it.

    
<% 
String css = "@import url(\"../css/nyk-style-00.css\");"; 
%>
< META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
< META name="GENERATOR" content="IBM WebSphere Studio">
< style>
<%=css%>
</style>

I have also tried it the following way without the quotes.

  
<% 
String css = "@import url(../css/nyk-style-00.css);"; 
%>
< META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
< META name="GENERATOR" content="IBM WebSphere Studio">
< style>
<%=css%>
</style>

I have also tried it straight without an intermediate string.

  
< META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
< META name="GENERATOR" content="IBM WebSphere Studio">
< style>
@import url(../css/nyk-style-00.css); 
</style>

Anyone have any ideas? It works when I use the full path to the css instead of the relative path.
[ February 10, 2004: Message edited by: Jason Kretzer ]

[Tony Chen]

What is this /css/nyk-style-00.css ? Where is it defined? In your web appliation (WAR)?

[Jason Kretzer]

I have found a solution besides calling the full path. When you run a JSP on the test server, the test server treats it as a servlet and as such the ../css/SomeCSS.css does not exist. It can be referenced from css/SomeCSS.css. Also, the paths of the links need to be adjusted as well.
Does anyone know if this is expected behavior? Will it act this way when it is deployed?