On 11/3/05, Robert Butera [EMAIL PROTECTED] wrote:
I am attempting to import a JSP file into a JSP using the c:import tag.
The line looks something like this:
...
c:import url=file://c:/dira/dirb/imported-file.jsp/
..
imported-file.jsp is being found ok, but it is not being processed as a
Dylan MacDonald [EMAIL PROTECTED] wrote on 07/13/2005 05:41:46 PM:
Can someone explain the context attribute in the c:import tag?
snip/
It is used in cross-context imports and is the name of the context you're
importing from. Most containers need to be configured to enable
cross-context
: Wednesday, October 20, 2004 4:03 PM
To: Tag Libraries Users List
Subject: Re: c:import problem
Christian,
Not sure if you're still wrestling with this, but I just wanted to post
to say that I've been meaning to slap a little test app together as a
sanity check and I'll post back when I get
Christian,
Not sure if you're still wrestling with this, but I just wanted to post to say
that I've been meaning to slap a little test app together as a sanity check and
I'll post back when I get the chance to code run it...
Quoting Christian Taylor [EMAIL PROTECTED]:
Hi,
I'm new to this
I think this is addressed in the 7.4 c:import section of the JSTL 1.0
Spec. There's an explanation of how errors are handled for internal vs.
external resources. Give it a look and see if it helps.
James Watkin wrote:
There seems to be an inconsistent behavior in the way c:import throws
I'm not an expert in this area, but after looking at the spec:
http://jcp.org/aboutJava/communityprocess/final/jsr052/index.html
it seems like a JspException should be thrown, even for internal URLs. It's
quite possible that I'm overlooking something though.
- Jim
At 05:50 PM 1/22/2004 -0500,
For an internal URL, try the equivalent JSP:
%
String path = request.getParameter(pageURL);
RequestDispatcher rd = request.getRequestDispatcher(path);
rd.include(request, response);
%
It seems to behave the same way. With TC 4.1.29, I don't see any log
info about the include, but on WLS 8.1.2 I
PROTECTED]
To: Tag Libraries Users List [EMAIL PROTECTED]; Tag
Libraries Users List [EMAIL PROTECTED]
Sent: Friday, October 10, 2003 12:01 PM
Subject: Re: c:import: relative links inside WEB-INF don't work
You need to use something like struts to operate inside WEB-INF.
At 05:34 PM 10/7/2003
AIM:jmitchtx
- Original Message -
From: Micael [EMAIL PROTECTED]
To: Tag Libraries Users List [EMAIL PROTECTED]; Tag
Libraries Users List [EMAIL PROTECTED]
Sent: Friday, October 10, 2003 12:01 PM
Subject: Re: c:import: relative links inside WEB-INF don't work
You need to use something
As an aside, you certainly can, and I think should, execute JSPs within
WEB-INF. I even execute my resources within WEB-INF.
At 04:55 PM 10/7/2003 -0400, Serge Knystautas wrote:
You shouldn't be able to execute JSPs within your WEB-INF, so all 3 of
your examples should be forbidden.
I think
You need to use something like struts to operate inside WEB-INF.
At 05:34 PM 10/7/2003 -0400, Manolo Ramirez T. wrote:
Hi,
I have this problem with Tomcat 4.1.24 and taglibs-standard 1.0.3. When I
try lo include a jsp inside WEB-INF I must to use an absolute url, this
are my files:
You shouldn't be able to execute JSPs within your WEB-INF, so all 3 of
your examples should be forbidden.
I think you might want to submit a bug report to whatever servlet engine
you're using.
--
Serge Knystautas
President
Lokitech software . strategy . design http://www.lokitech.com
p.
Hi,
I'm using jsp's outside WEB-INF to include prueba and prueba1, I forget
to say that.
_
Manolo Ramirez T.
Serge Knystautas wrote:
You shouldn't be able to execute JSPs within your WEB-INF, so all 3 of
your examples should be forbidden.
I think you might want to submit a bug
Manolo Ramirez T. wrote:
Hi,
I'm using jsp's outside WEB-INF to include prueba and prueba1, I forget
to say that.
In that case, you'd want the following:
%@ taglib uri=http://java.sun.com/jstl/core; prefix=c %
c:import url=WEB-INF/prueba2.jsp/
-- Pierre
_
Manolo Ramirez
Make sure that you are clear on the differences between c:import
jsp:include and @include they are all different and in my case the fact
that the imported page has no knowledge of my context hosed me.
R
Billy Bacon wrote:
I've looked through the archives and the suggested alternative for a
Yes, I am importing the core library, I have plenty of other c: tags
within my jsp and they work perfectly that's why it confuses me that's it
not working. Seems like a pretty simple tag to use.
Before trying to convert this to JSTL I had bean:define tag (from Struts)
and a jsp:include page=%=
I tried catching any exceptions and nothing was printed to the screen :-/
On 9/17/03 10:41 AM, Rick Ross [EMAIL PROTECTED] wrote:
Also, you might wanna do this to see if an error occurred:
c:catch var=ex
c:import url=${viewPage}/
/c:catch
c:if test=${not empty ex}
c:out value=${ex}
Is xyz only a scripting variable or is it also a scoped variable?
Quoting Billy Bacon [EMAIL PROTECTED]:
Yes, I am importing the core library, I have plenty of other c: tags
within my jsp and they work perfectly that's why it confuses me that's it
not working. Seems like a pretty simple tag
It's a scoped variable. But I think the problem is elsewhere because even
this doesn't work for me and no exception is thrown...
c:import url=myJspPage.jsp /
Any ideas?
On 9/17/03 11:34 AM, Kris Schneider [EMAIL PROTECTED] wrote:
Is xyz only a scripting variable or is it also a scoped
Have you tried a context-relative path (starts with /) to the page?
Quoting Billy Bacon [EMAIL PROTECTED]:
It's a scoped variable. But I think the problem is elsewhere because even
this doesn't work for me and no exception is thrown...
c:import url=myJspPage.jsp /
Any ideas?
On
Awesome. That worked!
Thanks Kris!
- Billy -
On 9/17/03 12:05 PM, Kris Schneider [EMAIL PROTECTED] wrote:
Have you tried a context-relative path (starts with /) to the page?
Quoting Billy Bacon [EMAIL PROTECTED]:
It's a scoped variable. But I think the problem is elsewhere because even
Okay, that's good, but I use page-relative paths successfully with c:import
all the time. Are you sure the page doing the import is in the same directory as
the page being imported?
Quoting Billy Bacon [EMAIL PROTECTED]:
Awesome. That worked!
Thanks Kris!
- Billy -
On 9/17/03 12:05 PM,
Yep, all my JSPs are in the same directory.
c:import url=xyz.jsp/ // didn't work
c:import url=/jsp/xyz.jsp/ // did the trick.
Dunno...
On 9/17/03 1:14 PM, Kris Schneider [EMAIL PROTECTED] wrote:
Okay, that's good, but I use page-relative paths successfully with c:import
all the time. Are
Craig Longman wrote:
i've been trying to figure out what happens to the request object when
you import a file, but had no answers from the tomcat list, so i thought
i'd try here.
when you include a file via c:insert that actually maps to another
servlet, it appears that the request object
On Tue, 2002-09-17 at 20:52, Shawn Bayern wrote:
On 17 Sep 2002, Craig Longman wrote:
when you include a file via c:insert that actually maps to another
servlet, it appears that the request object (in tomcat 4.1.10 at
least) doesn't reflect any of the actual request being delivered.
On Fri, 9 Aug 2002, Amarant Merah wrote:
Is it possible to import a file based on full path? e.g.
E:/somepath/myfile.xml
I understand it is possible to import using full http
url or relative to webapp like these:
c:import url=http://domain.com/somepath/myfile.xml;
var=xml/
c:import
On Mon, 15 Jul 2002, Tim Ringwood wrote:
% String xmlReq = request.getParameter(xml); %
%@taglib uri=http://java.sun.com/jstl/core;
prefix=c %
%@taglib uri=http://java.sun.com/jstl/xml;
prefix=x %
c:import url=generic.xsl var=xslt/
c:import url=%=xmlReq% var=xml/
x:transform
On Thu, 6 Jun 2002, Matt Raible wrote:
I remember hearing something about JSTL offering a try/catch syntax, or
maybe it was JSP 1.2. Anywhoo, I need it.
It's c:catch, as in
c:catch var=error
c:import ... /
/c:catch
c:if test=${not empty error}
Not there!
/c:if
--
Shawn
28 matches
Mail list logo
