After further trouble shooting, The problem for Jrun
not accepting absolute context path was due to our
installation. We created a virtual directory on IIS
which have the same name with our JRun virtual
directory. This confused the hell out of Jrun
So the remaining problem is JBuilder not accepting
relativeURLSpec.
This case is closed!!
-D
----- Original Message -----
From: "Dan Tran" <[EMAIL PROTECTED]>
To: "JRun-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, August 23, 2001 8:30 AM
Subject: JBuilder and JRun
> Hello experts,
>
> I am on a mission of looking a good JSP/JAVA IDE for my group
> to develop, debug, and finally deploy on a JRun server
>
> I am evaluating both JBuilder and JRunStudio
>
>
> Most of our JSP files do a <%@ include file="..\include\...." using the
> relative path. JRun runtime is very happy about it
>
> JBuilder is not happy about that declaration and throws "Bad file arguments
> .." (ofcourse lots of them)
>
> So I change them to <%@ include file=/include/..." using the application
> root path.
>
> Now JRun runtime is unhappy about it.
>
> I thought JSP is part of J2EE specification. And all IDE vendor should be
> able to complile all JSP code.
>
> What is going on? Whois the fault here? Jbuilder or Jrun?
>
>
> Thousand thanks
>
>
> -Dan
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
