DO NOT REPLY [Bug 3959] New: - Resource Properties, Connection Pool
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3959. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3959 Resource Properties, Connection Pool Summary: Resource Properties, Connection Pool Product: Struts Version: 1.0 Final Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Enhancement Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It would be nice... ...to store (and of course retrieve) the resource properties in a database not in a text file. ... that html:option can retrieve values automatic from a resource file or resource databses or database via sql-select. e.g.html:option value=A key=land.a/ html:option value=D key=land.d/ html:option value=SLO key=land.slo/ html:option value=XXX key=land.xxx/ could be something like html:option keyprefix=land/ and all values in the resource that starts with land are inserted in the html statement. ... that all tags which get data from the resource file (such as bean:message and html:option) have a dynamic key, let me show an example: logic:equal value=M name=sesskey property=geschlecht bean:message key=geschl.m//logic:equal logic:equal value=F name=sesskey property=geschlecht bean:message key=geschl.f//logic:equal cold be something like this: bean:message name=sesskey property=geschlecht keyprefix=geschl/ ...to have a method which is called every time before a connection is delivered from connection pool to the application to some stuff with the connection, e.g. set some database-roles according the actual rights of the user. Now I call, every time I request for a connection, my own methot prepare(con), which sets some database-roles. This works fine in the action classes and beans, but if I want to have a connection in JSP or in some sql-JSP-tags which you will write (I read the todo-list) there I'll have a problem.
RE: OS / Browser tag?
Whoops, missed this one. We've recently discussed this over on the taglib and commons mail lists. The end resolution was that an OS/Browser checker was better fitted as a Bean that sits inside JSPTL than a custom tag library. So the next step is to work on a Bean that can analyse a request. It fits quite well with another itch I have, for a generic log reporting mechanism in Java, so I will be hoping to integrate and develop it in there. Bringing all these browser detection ideas into a common place seems the obvious thing to do, I'll forward a post I made to commons/taglib suggesting a project to improve on log-creation and log-reporting, browser-detection is an integral part of that. Sorry to butt in, Bay On Thu, 4 Oct 2001 [EMAIL PROTECTED] wrote: Hi Jay, Yeah, coming down to having two tags. Would be great to add them to logic:present tag, but not sure it would work - seems to me there is a fundamental difference in that logic:present is checking for values in the request. What do others think? Dave PS Cross posting to dev list too. Jay Patel [EMAIL PROTECTED] on 10/04/2001 11:11:34 AM Please respond to [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] cc:(bcc: David Hay/Lex/Lexmark) Subject: RE: OS / Browser tag? I like the idea for the OS and Browser check. However I would suggest that the checks be made separately and not within one tag. How about if we can modify the logic:present to have two more parameters? ( that can also go for notPresent ). E.g. logic:present os=unix !-- the code -- /logic:present logic:present browser=Netscape version=4.0 !-- the code -- /logic:present Above approach will result in less of a learning curve and fewer tags. My $0.02 Jay Patel [EMAIL PROTECTED] -Original Message- From: Assenza, Chris [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 04, 2001 8:13 AM To: '[EMAIL PROTECTED]' Subject: RE: OS / Browser tag? I have something written that will do the server-side browser detection, etc. but not a tag for it. It's actually an adaptation of a nice PHP-based script that I stumbled on a while back. :) It'd be a great idea for a tag though - go for it! :) Chris Christopher Assenza Phone:412.201.6026 Fax: 412.201.6060 Email:[EMAIL PROTECTED] ACCESSDATA Moving Your Business from Point A to Point e.SM http://www.accessdc.com/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 03, 2001 4:59 PM To: [EMAIL PROTECTED] Subject: Re: OS / Browser tag? Sorry, maybe that wasn't clear! I am basically looking for an IF tag which utilises the OS and/or the browser that the client is running on. eg IF Unix and Netscape THEN would be logic:IF_os_browser os=unix browser=Netscape //do something /logic:IF_os_browser and the tag would automatically check for current client os and browser. Hope that's clearer! Cheers, Dave David_Hay/Lex/Lexmark.LEXMARK@sweeper.lex.lexmark.com on 10/03/2001 04:17:59 PM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: David Hay/Lex/Lexmark) Subject: OS / Browser tag? Hi everyone. Just wondering if anyone has written a tag to do something specific to OS or Browser? I'm probably going to write my own if no-one else has already done it! Cheers, Dave
Log Reporting (was RE: Browser detection taglib) (fwd)
[Cross-posted to Struts-Dev] -- Forwarded message -- Date: Tue, 25 Sep 2001 18:04:24 +0100 (BST) From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: '[EMAIL PROTECTED]' [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Log Reporting (was RE: Browser detection taglib) This thread was initially a request for a browser-taglib, then it turned into a discussion on Commons' util.http.BrowserDectory, and now I'd like to nudge it in a new direction with a brain dump on an idea I've been mulling upon. The reason for a browser-detection taglib is most likely so that the developer can monitor the types of browser's hitting their website. This is commonly done by products such as Analog and Webalizer. I believe Webalizer is a C product and Analog a Perl product. The general idea is that you point the Web Log analyser at the log files and it produces pretty tables, statistics and graphs. Another product that does the same thing is thecounter.com. I imagine there are many other websites with the same service. I pay them 10 dollars a year and get some pretty pictures. All of these have some flaws however. 1) They focus hard on web-logging. 2) They aren't in Java. 3) They (seem) to be web-server based. ie) A developer can't install it, the web server admin has to. 4) They are log-file based. Pointing them at a database seems difficult. What if the log-file is XML. I could be way off base, I've not gone into the code behind any of them at all. I think a Java Generic Log Maker, Viewer and Reporter would be very very nice. Hopefully it can reuse as much existing code as possible, ie) XML parser, Log4J. Here are some ideas: 1] View a log. 1.1) Logs must be able to come from anywhere. (interface Log) 1.2) User-definable log-format. Need to support types, ie) url, date, email, number. 1.3) Need an object structure for a Log which consists of lines and fields. 2] Report on a log. 2.1) Model-based loglets that manipulate a Log, possibly into another Log. ie) averages, tables, summations etc. Statistics. 2.2) Reportlets (!). Take a Log and pretty it up. ie) piecharts, bar-graphs, ascii. 2.3) Provide different output formats. Ascii, PDF, JSP/Servlet, Swing. 2.4) Genericity of Graphing/Imaging solution. Be able to handle many image types. 3] Log Creation. Sits on top of Log4J? 3.1) Web-targetted. Browser detect, IP etc. 3.2) Generic so developers can log application logs and still use the product to analyse the logs. 4] Utilities 4.1) BrowserInfo. Database of browser versions to browser capability? ie) IE6/Mac = Java2, IE4/Win = Java1.1.4 4.2) Portlistener. Use something like this to build up information on browser http headers. Flow of control --- Application outputs a log to some LogSource. LogSource provides access to a Log which provides LogEvents. Each LogEvent has a set of LogFields, etc. Log is passed through a chain of Loglets. These would do mathematics mainly. Averaging, Summing, etc. One would be a dnslookup. Result of the Loglets stage is then passed to/through Reportlets. These would build up a report on the data. In a presentation generic way. So a Table object, an Image object. Hopefully not a lot more. Then the result of the Reportlet would be passed to a presentation layer, JSP/PDF/Email etc. = I know that's all very pie in the sky, but any ideas people have would be gratefully received. I would also love to know of any products that either do the above or are open-source-java and could fill in a part of it. I have a basic http snooping tool in Java to look at http headers (yeah I know you can do it from cmd line *nux, netcat isn't it?). I've a CSV reader/writer that might be growable to a Log-reader. And there's the BrowserDetector. Plus Log4J which this idea should be integrated as close to as possible. Maybe :) Bay
Re: Bugzilla Bug Reports
+1 Sounds like a good way to give more visibility to all the bugs. David --- Ted Husted [EMAIL PROTECTED] wrote: Originally, I think we did that just to leverage bugilla's automatic mail feature. Posting them to DEV and leaving them unassigned would seem to be a better fit with the meritocratic model. Jakarta Committers are all jointly and severally responsible for everything in their codebase. It is expected that people will be sometimes unavailable for periods of time (while meeting other milestones), and whoever is available should feel free to pitch in and do whatever they can whenever they can. So +1 for posting them to the DEV list, and dropping the auto-assignments. [EMAIL PROTECTED] wrote: I like this idea. Then I don't have to check Bugzilla for new bugs any more. Will this change affect the initial assignment of new bugs? Currently, they are automatically assigned to the component owner. I feel a little uncomfortable, sometimes, swiping bugs from other people's lists, so I'd like to see them initially unassigned, if that's possible, and other people agree. -- Martin Cooper - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, October 03, 2001 5:50 PM Subject: Bugzilla Bug Reports Hi Folks, Finally getting to breathe for a few minutes, I'm going to start whacking off a few of the outstanding Bugzilla bug reports against Struts (particularly 1.0-final related issues). While doing this, I'd like to suggest that we do what several other Jakarta projects are doing, and have new bug reports initially directed to the STRUTS-DEV mailing list. That way, they become more visible to all the developers. Then, a particular developer who wants to take ownership of a particular bug report can assign it to themselves. This seems to work pretty effectively on Tomcat -- I'd like to try it here as well. Craig __ Do You Yahoo!? NEW from Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month. http://geocities.yahoo.com/ps/info1
cvs commit: jakarta-struts/src/share/org/apache/struts/taglib/html OptionTag.java OptionsTag.java
martinc 01/10/04 22:07:48
Modified:doc struts-html.xml
src/share/org/apache/struts/taglib/html OptionTag.java
OptionsTag.java
Log:
Port fix for Bugzilla #3289 to main trunk.
PR: 3289
Submitted by: Joe Hrynyk
Revision ChangesPath
1.23 +35 -0 jakarta-struts/doc/struts-html.xml
Index: struts-html.xml
===
RCS file: /home/cvs/jakarta-struts/doc/struts-html.xml,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- struts-html.xml 2001/09/18 05:50:51 1.22
+++ struts-html.xml 2001/10/05 05:07:47 1.23
@@ -3080,6 +3080,23 @@
/attribute
attribute
+namestyle/name
+requiredfalse/required
+rtexprvaluetrue/rtexprvalue
+info
+CSS styles to be applied to this HTML element.
+/info
+/attribute
+
+attribute
+namestyleClass/name
+requiredfalse/required
+rtexprvaluetrue/rtexprvalue
+info
+CSS stylesheet class to be applied to this HTML element.
+/info
+/attribute
+attribute
namevalue/name
requiredtrue/required
rtexprvaluetrue/rtexprvalue
@@ -3228,6 +3245,24 @@
Property of the form bean, or the bean specified by the name
attribute, that will return the collection of values to returned
to the server for these options.
+/info
+/attribute
+
+attribute
+namestyle/name
+requiredfalse/required
+rtexprvaluetrue/rtexprvalue
+info
+CSS styles to be applied to this HTML element.
+/info
+/attribute
+
+attribute
+namestyleClass/name
+requiredfalse/required
+rtexprvaluetrue/rtexprvalue
+info
+CSS stylesheet class to be applied to this HTML element.
/info
/attribute
/tag
1.9 +44 -4
jakarta-struts/src/share/org/apache/struts/taglib/html/OptionTag.java
Index: OptionTag.java
===
RCS file:
/home/cvs/jakarta-struts/src/share/org/apache/struts/taglib/html/OptionTag.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- OptionTag.java2001/06/10 03:53:31 1.8
+++ OptionTag.java2001/10/05 05:07:47 1.9
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-struts/src/share/org/apache/struts/taglib/html/OptionTag.java,v 1.8
2001/06/10 03:53:31 craigmcc Exp $
- * $Revision: 1.8 $
- * $Date: 2001/06/10 03:53:31 $
+ * $Header:
/home/cvs/jakarta-struts/src/share/org/apache/struts/taglib/html/OptionTag.java,v 1.9
2001/10/05 05:07:47 martinc Exp $
+ * $Revision: 1.9 $
+ * $Date: 2001/10/05 05:07:47 $
*
*
*
@@ -82,7 +82,7 @@
* the server if this option is selected.
*
* @author Craig R. McClanahan
- * @version $Revision: 1.8 $ $Date: 2001/06/10 03:53:31 $
+ * @version $Revision: 1.9 $ $Date: 2001/10/05 05:07:47 $
*/
public class OptionTag extends BodyTagSupport {
@@ -173,6 +173,34 @@
/**
+ * The style associated with this tag.
+ */
+private String style = null;
+
+public String getStyle() {
+return style;
+}
+
+public void setStyle(String style) {
+this.style = style;
+}
+
+
+/**
+ * The named style class associated with this tag.
+ */
+private String styleClass = null;
+
+public String getStyleClass() {
+return styleClass;
+}
+
+public void setStyleClass(String styleClass) {
+this.styleClass = styleClass;
+}
+
+
+/**
* The server value for this option, also used to match against the
* current property value to determine whether this option should be
* marked as selected.
@@ -251,6 +279,16 @@
results.append( disabled=\disabled\);
if (selectTag.isMatched(value))
results.append( selected=\selected\);
+if (style != null) {
+results.append( style=\);
+results.append(style);
+results.append(\);
+}
+if (styleClass != null) {
+results.append( class=\);
+results.append(styleClass);
+results.append(\);
+}
results.append();
String text = text();
if (text == null)
@@ -278,6 +316,8 @@
