The actual reason why the URL has changed between 2.4.4 and 3.x is 
because you're using Tomcat 4.x in JBoss 3 and you were using Tomcat 3.x 
previously. Between these two versions, there was a change from using 
file based urls to JNDI based urls for file system lookups.

-javier

[EMAIL PROTECTED] wrote:
> Further to my earlier mail, I do not think this is a bug!
> 
> I think this issue is because the Petstore code uses URL.toString() 
>[MainServlet.java] at one point to get a String representation of the URL and then at 
>another point uses the String to get a URL back [ScreenFlowXmlDAO].
> 
> Sorry for the false alarm.
> 
> Mak 
> 
> 
> 
> 
> 
>> from:    [EMAIL PROTECTED]
>> date:    Thu, 18 Jul 2002 12:34:36
>> to:      [EMAIL PROTECTED]
>> subject: Re: [JBoss-user] BUG?: JBoss 3 & ServletContext.getResource()
>>
>>
>>Hi 
>>
>>I am having some trouble getting a resource in a WAR using JBoss 3. This is related 
>to trying to deploy Petstore on JBoss 3.
>>
>>In version 2.4.4 when you use ServeletContext.getResource("/<somefile>"), you get a 
>file URL starting with file:C:\...
>>
>>In version 3.0.0 I am getting a URL beginning with jndi:\\ (by using 
>URL.toString()). However if I now try to re-create the supposedly valid URL beginning 
>with jndi:, it fails with the message java.net.MalformedURLException: unknown 
>protocol: jndi!!
>>
>>Can anyone please help me with this?
>>
>>Thanks a lot
>>Mak
>>
>>
>>
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
> 




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to