Can't locate META-INF and teething problems as a result
Sorry if sounds pathetic nevetheless i have downloaded the (mysql) mm.mysql-2.0.4-bin.jar file . I was able to get the PostgrSql to function correctly by installing dbtags taglibrary and followed the configuration steps. Anyway there is a dbtag.tld that resides in /WEB-INF sub directory of my web application is this therefore utilised by both tag library Jar Files . As i have to add a taglib element to my web app deployment descriptor in my web.xml. Thus i created my own mysql.tld as nothing else works nor this.So assume that taglib taglib-urimm.mysql-2.0.4-bin.jar/taglib-uri taglib-location/WEB-INF/mysql.tld/taglib-location /taglib So assume that the tag element below is functionally for both Jar Files. taglib taglib-urihttp://jakarta.apache.org/taglibs/dbtags/taglib-uri taglib-location/WEB-INF/dbtags.tld/taglib-location /taglib Cheers Chuck Amadi Systems Programmer -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Db Tags not able to find the oracle driver.
Hello, I have some code that connects to oracle using the classes12.zip/nls_...zip (CONTENT). I had to unzip the files and then include the top level directory to get it to work, now if I try to use the dbtags way(which will save me a lot of work) I get No Class found error. How can this be I can use the Oracle drivers in my app but not in the dbtags app? Very confused. http://www.cutthroatcom.com/ Chris Buckley Cutthroat Communications, Inc. Network Operations Bus (406) 556-1778 Fax (406) 585-9645 Bozeman, MT 59718 http://www.cutthroatcom.com http://www.cutthroatcom.com/ The Promise of Broadband access is here.?XML:NAMESPACE PREFIX = O /
RE: JSP1.2 JRun ver3.1
Tomcat 4 ( http://jakarta.apache.org http://jakarta.apache.org ) Resin 2.x ( http://www.caucho.com http://www.caucho.com ) ... -Original Message- From: Yee Tsun Min, Ben [mailto:[EMAIL PROTECTED]] Sent: woensdag 3 april 2002 9:57 To: '[EMAIL PROTECTED]' Subject: RE: JSP1.2 JRun ver3.1 which webserver's currently implement JSP ver1.2 ? i'm using JRun ver3.1 and looking through their JSP documentation they're currently implementing ver 1.1... I would also like to know whether i can configure JRun to support ver1.2 is the container available for download ?
RE: How to access initParameters in the dbtags library?
That's strange, i had tried setting them as context-param and it appeared to work fine for me. Note the context-param tag(s) go directly under the web-app tag. You may want to drop the init-param tag. web-app context-param param-namedbUrl/param-name param-valuejdbc:odbc:deved/param-value /context-param context-param param-namedbDriver/param-name param-valuesun.jdbc.odbc.JdbcOdbcDriver/param-value /context-param Also - i'm always curious to know why folks are preferring to use the DBTags lib over the SQL actions within JSTL? I had used DBTags before JSTL RI was released, and find it A LOT MORE flexible and user-friendly. (This is not to say that the DBTags team did not do a good job; it's just that JSTL has really improved on it. 8) ) Second day on custom tags and I'm having trouble accessing something the docs say I should be able to. I'm using the jakarta dbtags library and attempting to set the database url, driver, userId and password in the web.xml as initParameters as the docs suggest is possible. However I can't locate where what or how these initParameters are set. They don't seem to be normal context-params.. can anybody set me straight? The taglib itself is working fine, I just would rather store these params somewhere central. I'm using Tomcat 3.3 and the relevant bits of m web.xml currently looks like this: taglib taglib-urihttp://jakarta.apache.org/taglibs/dbtags/taglib-uri taglib-location/WEB-INF/dbtags.tld/taglib-location /taglib taglib taglib-uri/dbtags/taglib-uri taglib-location/WEB-INF/lib/dbtags.jar/taglib-location /taglib context-param init-param param-namedbURL/param-name param-valuejdbc:twtds:sqlserver://blah/blah/param-value descriptionblah blah /description /init-param /context-param and the DBtags docs suggest I should be able to do this: * Instead of including your database URL, driver name, user id, or password inside your tag body, you may optionally use the initParameter attribute: %-- store your connection info in the web.xml file --% sql:connection id=conn1 sql:url initParameter=dbURL/ sql:driver initParameter=mysqlDriver/ sql:userId initParameter=dbUserId/ sql:password initParameter=dbPassword/ /sql:connection Tref Gare Web Developer MCSD/SCJP eCommerce Group Phone:(03) 9221 4106 Mobile: 0409 556 478 Fax: (03) 9941 4295 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
date format
Hello,
Which is the input format in the dateFormat tag of JSTL.??
I'm trying to format a date in long format like MONDAY 10 JULY 2001 using the fmt tag
library.
I read the date field from a SQLserver DB, and I always got an Invalid date. (The same
if I use the datetime tag library)
fmt:formatDate pattern= d c:out value=${day}//fmt:formatDate .
So I thought that the date coming from db is invalid and I put a parseDate inside:
fmt:formatDate pattern= d fmt:parseDate
pattern=MMdd1999/07/01/fmt:parseDate /fmt:formatDate
and I got the same error Unparsable date.
Please help me.
Andrea Grittini ( mailto:[EMAIL PROTECTED])
Tel: +39-2-97482.1- Fax: +39-2-97482?
Computer Design S.r.l., Via Piave 46 - 20010 S.Stefano Ticino - ITALY
http://www.cdesign.it/
Mailer taglib Bug with addRecepient ?
Hello,
Why is the address variable not reset to null in the doAfterBody() function
? (as is done in the doStartTag() in AddReceipientTag )
The problem I had was when I was doing:
mt:addrecipient type=toc:out
value=${param.friendsEmail1}//mt:addrecipient
mt:addrecipient type=toc:out
value=${param.friendsEmail2}//mt:addrecipient
friendsEmail1 is always set, friendsEmail2 can be the empty string.
When c:out value=${param.friendsEmail2}/ outputs an empty string then
the mailer taglib sends a mail with 2 times the friendsEmail1 address in the
TO field of the email.
Adding an address = null fixes this problem.
FYI: the current code I'm talking about:
public final int doStartTag() throws JspException {
// parent tag must be a MailTag, gives access to methods in parent
myparent =
(MailTag)javax.servlet.jsp.tagext.TagSupport.findAncestorWithClass(this,
MailTag.class);
if (myparent == null)
throw new JspException(addrecipient tag not nested within mail
tag);
// Make sure type is set..either to, cc, or bcc
if ((type != null) (type.equalsIgnoreCase(to) ||
type.equalsIgnoreCase(cc) ||
type.equalsIgnoreCase(bcc))) {
if (address != null) {
// Try to see if the address attribute was used.
if (type.equalsIgnoreCase(to))
// set to in the parent tag
myparent.addTo(address);
if (type.equalsIgnoreCase(cc))
// set cc in the parent tag
myparent.addCc(address);
if (type.equalsIgnoreCase(bcc))
// set bcc in the parent tag
myparent.addBcc(address);
address = null; // reset address
return SKIP_BODY;
} else
return EVAL_BODY_TAG;
} else
throw new JspException(The type attribute is not set. +
Specify either \to\, \cc\, or
\bcc\.);
}
/**
* implementation of the method from the tag interface that tells the
JSP
* page what to do after the body of this tag
*
* @throws JSPException thrown when an error occurs while processing
the
*body of this method
*
* @return SKIP_BODY int telling the tag handler to not evaluate the
body
* of this tag again
*
*/
public final int doAfterBody() throws JspException {
if ((address = bodyContent.getString()) != null) {
// Try to see if the body was used for the address.
if (type.equalsIgnoreCase(to))
// set to in the parent tag
myparent.addTo(address);
if (type.equalsIgnoreCase(cc))
// set cc in the parent tag
myparent.addCc(address);
if (type.equalsIgnoreCase(bcc))
// set bcc in the parent tag
myparent.addBcc(address);
return SKIP_BODY;
} else
throw new JspException(Address was not found. set +
the address attribute, or place the address
in +
the body of the tag.);
}
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
i18n:formatDate...tag example
Hi All, Could anybody show me some example showing usage of i18n:formatDate tag. Currently, I'm using something like this in my JSP, but its not printing anything. i18n:formatDate value=%=new Date()% pattern=MM/dd// Thanks Regards, -- Puneet Maini This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
[New] Cache Taglib
Hi all,
Just wanted to announce the Cache Taglib, now in development at Jakarta
Taglibs.
A large web application provides many opportunities to cache content for
performance. For instance, entire pages could be cached by a filter;
whole chunks of sites could be cached behind a network edge (see
http://www.esi.org). Our Cache Taglib should help build community
experience with using JSP tag libraries to cache fragments of JSP pages
within a Java web application.
The Cache Taglib currently has two tags; they've been designed with JSTL's
principles in mind. Specifically, their goal is to let page authors focus
on presentation and not worry about too many behind-the-scenes details.
(Also, they use the JSTL expression language.) Right now, there are just
two tags: cache:cache and cache:invalidate.
The cache:cache tag lets you wrap a page fragment and indicate that it's
cachable. The tag lets you factor out the dynamic nature of such
fragments, specifying a key that represents the content. For instance,
as the page author, you might know that a large part of your page doesn't
change once a user has logged in; you might therefore use a key of
${user} to indicate that the fragment depends on the 'user' variable.
The cache:invalidate tag lets you explicitly destroy a cache entry or a
whole cache.
Applications can use the Cache Taglib with an unlimited number of caches;
the size and expiration policies of the caches are determined by back-end
code on the assumption that page authors don't frequently need to handle
such details. (There's a utility class, CacheUtil, that lets your code
easily configure the caches.)
Anyway, the tags and documentation are available from
http://jakarta.apache.org/taglibs/doc/cache-doc/intro.html
I'm happy to answer any questions you've got. Again, while the tags
should be usable as presented, this is mainly an experiment to build
experience with taglib-based caching -- so comments would be great!
Thanks.
--
Shawn Bayern
Author, JSP Standard Tag Library http://www.jstlbook.com
(coming this summer from Manning Publications)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: i18n:formatDate...tag example
Puneet: Could anybody show me some example showing usage of i18n:formatDate tag. Currently, I'm using something like this in my JSP, but its not printing anything. i18n:formatDate value=%=new Date()% pattern=MM/dd// Have you considered using the new formatting tags that are part of the JSP Standard Tag Library (JSTL)? (See Tim Dawson's attached email about migrating from the i18n taglib to the formatting tags in JSTL.) The JSTL RI (Beta 1) is available at http://jakarta.apache.org/builds/jakarta-taglibs/releases/standard/ You can read the JSTL public draft at http://jcp.org/aboutJava/communityprocess/review/jsr052 Community feedback is still actively sought. You can mail comments to [EMAIL PROTECTED] Now to answer your question from a JSTL perspective: Try using %@ taglib prefix=fmt uri=http://java.sun.com/jstl/ea/fmt; % fmt:formatDate pattern=MM/dd// Hope this helps. Jan ---BeginMessage--- The i18n taglib will be mostly replaced by tags in the standard taglib. I was able to provide some input into the shape of the i18n components of the standard taglib. At this point, I'll personally be migrating my own projects to the standard taglib and I expect most everybody else will do so as well. The question is: how do we want to go about doing deprecating this taglib and others that are similarly being obsoleted? Clearly the tags need to still be built and supported for JSP 1.1 users, but we need to make sure they are clearly deprecated so that future users go to the standard taglib equivalents. Mostly I'd think this would be done with documentation, on the website, in the tld, in the code, etc. We'd need a standard message for consistency in pointing users to the new location of the standard taglib. We should also probably show some examples of old tag/new tag use cases. I know the i18n formatting tags have definately changed in places, and a few of the i18n tags aren't being replicated in the standard taglib due to lack of use. We could actually move the source in the cvs tree but that feels like overkill. Thoughts? Tim _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] ---End Message--- -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: JSP1.2 JRun ver3.1
Tomcat version 4.X does. Rick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: How to access initParameters in the dbtags library?
Thanks Anuj, I'll give that a shot. Re: the why don't you use the JSTL library.. it's a case of ignorance on my part I'm afraid. However on my quick investigations this morning it still seems to be in beta and not advised for production systems which is what we're building at the moment. It also requires a JSP1.2 container and we're also working with Tomcat 3.3 which isn't JSP1.2 compliant. As such we don't seem to be quite ready for each other just yet. Let me know if I've got the wrong end of the stick though, as I'm a newbie in this corner. Cheers Tref Gare Web Developer MCSD/SCJP eCommerce Group Phone: (03) 9221 4106 Mobile: 0409 556 478 Fax:(03) 9941 4295 -Original Message- From: Agrawal, Anuj (Anuj)** CTR ** [SMTP:[EMAIL PROTECTED]] Sent: Wednesday,3 April 2002 8:36 To: 'Tag Libraries Users List' Subject: RE: How to access initParameters in the dbtags library? That's strange, i had tried setting them as context-param and it appeared to work fine for me. Note the context-param tag(s) go directly under the web-app tag. You may want to drop the init-param tag. web-app context-param param-namedbUrl/param-name param-valuejdbc:odbc:deved/param-value /context-param context-param param-namedbDriver/param-name param-valuesun.jdbc.odbc.JdbcOdbcDriver/param-value /context-param Also - i'm always curious to know why folks are preferring to use the DBTags lib over the SQL actions within JSTL? I had used DBTags before JSTL RI was released, and find it A LOT MORE flexible and user-friendly. (This is not to say that the DBTags team did not do a good job; it's just that JSTL has really improved on it. 8) ) Second day on custom tags and I'm having trouble accessing something the docs say I should be able to. I'm using the jakarta dbtags library and attempting to set the database url, driver, userId and password in the web.xml as initParameters as the docs suggest is possible. However I can't locate where what or how these initParameters are set. They don't seem to be normal context-params.. can anybody set me straight? The taglib itself is working fine, I just would rather store these params somewhere central. I'm using Tomcat 3.3 and the relevant bits of m web.xml currently looks like this: taglib taglib-urihttp://jakarta.apache.org/taglibs/dbtags/taglib-uri taglib-location/WEB-INF/dbtags.tld/taglib-location /taglib taglib taglib-uri/dbtags/taglib-uri taglib-location/WEB-INF/lib/dbtags.jar/taglib-location /taglib context-param init-param param-namedbURL/param-name param-valuejdbc:twtds:sqlserver://blah/blah/param-value descriptionblah blah /description /init-param /context-param and the DBtags docs suggest I should be able to do this: * Instead of including your database URL, driver name, user id, or password inside your tag body, you may optionally use the initParameter attribute: %-- store your connection info in the web.xml file --% sql:connection id=conn1 sql:url initParameter=dbURL/ sql:driver initParameter=mysqlDriver/ sql:userId initParameter=dbUserId/ sql:password initParameter=dbPassword/ /sql:connection Tref Gare Web Developer MCSD/SCJP eCommerce Group Phone: (03) 9221 4106 Mobile: 0409 556 478 Fax:(03) 9941 4295 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Taglibs and included pages
I'm seeing some strange (or maybe intended) behavior with taglibs and included files. Here's what I do: %@ taglib prefix=bean uri=/WEB-INF/struts-bean.tld % %@ taglib prefix=html uri=/WEB-INF/struts-html.tld % Normal JSP/HTML stuff... html:form action=/action.do style=margin-botton:0m TABLE jsp:include page=/Common/foo1.jsp/ !-- Page specific rows go here -- /TABLE HR TABLE jsp:include page=/Common/foo2.jsp/ !-- More page specific rows here -- /TABLE /html:form More standard jsp/html (foo1 and foo2 just contain table rows but do use the struts bean tag.) The problem is with the two include files. If I don't repeat the % taglib declarations in the included files, they don't work. It seems to me that once the libs are declared, that declaration should hold for the remainder of the page. I'm sure I'm missing something here, and I'm looking for enlightenment. Any info is appreciated. Cheers, Bryan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Taglibs and included pages
On Wed, 3 Apr 2002, Bryan P. Glennon wrote: The problem is with the two include files. If I don't repeat the % taglib declarations in the included files, they don't work. It seems to me that once the libs are declared, that declaration should hold for the remainder of the page. I'm sure I'm missing something here, and I'm looking for enlightenment. When you include files with %@ include %, they are incorporated into the source file, and you wouldn't need to re-declare taglibs with %@ taglib %. However, jsp:include lets you include full, stand-alone pages (and other resources). More formally, jsp:include includes a separate translation unit, so the target page will still need its own declarations. -- Shawn Bayern Author, JSP Standard Tag Library http://www.jstlbook.com (coming this summer from Manning Publications) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Taglibs and included pages - correction
As opposed to what I say below, leaving the %@ taglib declarations out of foo1 is ok - it displays fine. Thanks, Bryan -Original Message- From: Bryan P. Glennon Sent: Wednesday, April 03, 2002 6:27 PM To: [EMAIL PROTECTED] Subject: Taglibs and included pages I'm seeing some strange (or maybe intended) behavior with taglibs and included files. Here's what I do: %@ taglib prefix=bean uri=/WEB-INF/struts-bean.tld % %@ taglib prefix=html uri=/WEB-INF/struts-html.tld % Normal JSP/HTML stuff... html:form action=/action.do style=margin-botton:0m TABLE jsp:include page=/Common/foo1.jsp/ !-- Page specific rows go here -- /TABLE HR TABLE jsp:include page=/Common/foo2.jsp/ !-- More page specific rows here -- /TABLE /html:form More standard jsp/html (foo1 and foo2 just contain table rows but do use the struts bean tag.) The problem is with the two include files. If I don't repeat the % taglib declarations in the included files, they don't work. It seems to me that once the libs are declared, that declaration should hold for the remainder of the page. I'm sure I'm missing something here, and I'm looking for enlightenment. Any info is appreciated. Cheers, Bryan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Taglibs and included pages
Bryan == Bryan P Glennon [EMAIL PROTECTED] writes: Bryan I'm seeing some strange (or maybe intended) behavior with taglibs and Bryan included files. Here's what I do: Bryan %@ taglib prefix=bean uri=/WEB-INF/struts-bean.tld % Bryan %@ taglib prefix=html uri=/WEB-INF/struts-html.tld % Bryan Normal JSP/HTML stuff... Bryan html:form action=/action.do style=margin-botton:0m Bryan TABLE Bryan jsp:include page=/Common/foo1.jsp/ Bryan !-- Page specific rows go here -- Bryan /TABLE Bryan HR Bryan TABLE Bryan jsp:include page=/Common/foo2.jsp/ Bryan !-- More page specific rows here -- Bryan /TABLE Bryan /html:form Bryan The problem is with the two include files. If I don't repeat the % taglib declarations Bryan in the included files, they don't work. It seems to me that once the Bryan libs are declared, Bryan that declaration should hold for the remainder of the page. I'm sure I'm Bryan missing something Bryan here, and I'm looking for enlightenment. It helps to understand how the JSP include action works, as opposed to the include directive. Your main JSP and your included JSP pages are all compiled into individual servlets. They have to be able to work independently (even if they're generating only a fragment of the output). The include action happens at execution time, whereas the include directive happens at compile time. You could get away with leaving out the taglib declarations in the included pages if they were included with the directive, but not if they were included with the action. -- === David M. Karr ; Java/J2EE/XML/Unix/C++ [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: i18n:formatDate...tag example
Thanks Jan, But I'm using weblogic 5.1, which supports JSP 1.1 spec. Could anybody confirm if it would be okay to use JSTL / standard taglib with weblogic 5.1 container? I solved my problem by using datetime taglibs, like this: dt:format pattern=MM/dd/ date=%=tsDatePosted%/dt:format Thanks Regards, -- Puneet Maini -Original Message- From: Jan Luehe [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 03, 2002 11:33 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: i18n:formatDate...tag example Puneet: Could anybody show me some example showing usage of i18n:formatDate tag. Currently, I'm using something like this in my JSP, but its not printing anything. i18n:formatDate value=%=new Date()% pattern=MM/dd// Have you considered using the new formatting tags that are part of the JSP Standard Tag Library (JSTL)? (See Tim Dawson's attached email about migrating from the i18n taglib to the formatting tags in JSTL.) The JSTL RI (Beta 1) is available at http://jakarta.apache.org/builds/jakarta-taglibs/releases/standard/ You can read the JSTL public draft at http://jcp.org/aboutJava/communityprocess/review/jsr052 Community feedback is still actively sought. You can mail comments to [EMAIL PROTECTED] Now to answer your question from a JSTL perspective: Try using %@ taglib prefix=fmt uri=http://java.sun.com/jstl/ea/fmt; % fmt:formatDate pattern=MM/dd// Hope this helps. Jan This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. Visit us at http://www.cognizant.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
