Hi everyone,
I have created a JSP page that use the xml tag library, specifically using
xpath. Everything works perfectly fine as long as I don't have a doctype
definition like the following in my XML instance:
If I remove it, life is great, but if I don't, I get a java error like this:
org.ap
No problem, glad it's working.
Quoting Michael Duffy <[EMAIL PROTECTED]>:
>
> I know - I deserve a dope slap for this one. ;)
>
> But you're absolutely right - I've been trying to slow
> down and be a little more careful with my query. I
> must have done something wrong with a parameter in a
I know - I deserve a dope slap for this one. ;)
But you're absolutely right - I've been trying to slow
down and be a little more careful with my query. I
must have done something wrong with a parameter in a
previous incarnation, because now I'm getting a good
result back.
I apologize for takin
[EMAIL PROTECTED] wrote:
Well, if I take a look at jstl.jar, it shows in
javax.servlet.jsp.jstl.core.Config the following:
final public static java.lang.String FMT_LOCALIZATIONCONTEXT =
"javax.servlet.jsp.jstl.fmt.localizationContext";
(viewed with Eclipse).
If so you're using a pre-release version
Well of course the data access stuff shouldn't be embedded in a JSP ;-). But it
should still work. Actually, it sounds like you might have a mismatch between
the types you're using for your input parameters and the column types your
querying against. Can you build your query up param by param to se
1.0.2 actually... looks like I need an update :-)
-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 9. Juli 2003 18:40
To: Tag Libraries Users List
Subject: RE: How to create a general resource bundle for JSTL?
Which release of the Standard taglib are you
Which release of the Standard taglib are you using? My output was from 1.0.3.
>From CVS, this appears to have been fixed in version 1.7 of the Config.java
file. Looks like you've got an older release...
Quoting [EMAIL PROTECTED]:
> Well... my class didn't compile with FMT_LOCALIZATION_CONTEXT...
Well... my class didn't compile with FMT_LOCALIZATION_CONTEXT...
Perhaps someone from the JSTL team could clarify things?
Best regards,
Eric
-Original Message-
From: Kris Schneider [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 9. Juli 2003 18:07
To: Tag Libraries Users List
Subject: RE: How t
I made a bonehead error on that one, Kris. My
original query had parameters in it. When it failed,
I stripped it down to "SELECT * FROM DEFECT" - but in
my haste I forgot to remove the tags
underneath. Once I saw that, the simple query worked
just fine.
Once that was working, I put back my lo
So you're saying something simple like:
SELECT * FROM DEFECT
is blowing up?
Quoting Michael Duffy <[EMAIL PROTECTED]>:
>
> Good check, Kris, but I did have the EL notation.
>
> I stripped my query down (it got big with joins) to a
> "SELECT * FROM DEFECT". I still get an "invalid
> colum
But javap reports:
Compiled from Config.java
public class javax.servlet.jsp.jstl.core.Config extends java.lang.Object {
...
public static final java.lang.String FMT_LOCALIZATION_CONTEXT;
...
}
Quoting [EMAIL PROTECTED]:
> Well, if I take a look at jstl.jar, it shows in
> javax.servle
Well, if I take a look at jstl.jar, it shows in
javax.servlet.jsp.jstl.core.Config the following:
final public static java.lang.String FMT_LOCALIZATIONCONTEXT =
"javax.servlet.jsp.jstl.fmt.localizationContext";
(viewed with Eclipse).
Best regards,
Eric
-Original Message-
From: Martin va
Now you're confusing me;)
The spec clearly states that the Config class has a:
public static final String FMT_LOCALIZATION_CONTEXT;
Therefore this IS the correct spelling...
Martin
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: woensdag 9 juli 2003 17:
Good check, Kris, but I did have the EL notation.
I stripped my query down (it got big with joins) to a
"SELECT * FROM DEFECT". I still get an "invalid
column exception". The query runs fine in Oracle's
SQL*Plus.
I wrote a simple JSP a while back that lets me type an
ad-hoc query into an HTML
Hi Martin
Yup, I noticed it and told Shawn Bayern, because in JSTL in Action it's
written as FMT_LOCALIZATION_CONTEXT (which would be the right way to spell
it IMHO).
Best regards,
Eric
P.S. Good luck with the path!
-Original Message-
From: Martin van Dijken [mailto:[EMAIL PROTECTED]
Se
Hey Eric,
I've got to start working heavily with I18N currently and am investigating some of the
same paths you go along. You did notice that the FMT_LOCALIZATIONCONTEXT is not the
correct naming, but that FMT_LOCALIZATION_CONTEXT is? I guess you must have because
stuff probably doesn't compile
Are you using:
instead of:
Quoting Michael Duffy <[EMAIL PROTECTED]>:
>
> I've got a question that will turn out to be simple,
> but I'm not seeing it.
>
> I'm writing an SQL query that has a date parameter, so
> I'm using the tag nested underneath my
> tag, with the type="date" attribut
I've got a question that will turn out to be simple,
but I'm not seeing it.
I'm writing an SQL query that has a date parameter, so
I'm using the tag nested underneath my
tag, with the type="date" attribute set.
"JSTL In Action" tells me that the value for
has to be a scoped variable of type
j
I have the following JSP that is using to do a
transformation. The xsl that I am using has "" tags that are
used to
import other needed xsl documents. The import in main xsl works correctly,
but the
file it imports does an include. This include causes the error below to
occur. I
thought I
Silly? I disagree.
Filters are about more than removing whitespace.
I want the whitespace when I'm developing, because
readability and understanding is very important to me.
When I use a filter, I can keep the whitespace when I
develop and remove it when it really matters - when
sending a mi
Hi,
Maybe I'm the wacky programmer here, but I don't just program Java/JSP I also do quite
a lot of Javascript and stylesheet programming. Specifically when debugging javascript
applications, it's very annoying if the line numbers that get reported by the browser
don't match the line number in
21 matches
Mail list logo
