Re: Struts officially supported at Ford
I didn't read anything in the quote the mentioned v1.1b2. It sounds to me like maybe IBM has tailored whatever beta version they started with to the point where they want their developers to use that as their common base. - Original Message - From: Karr, David [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Thursday, January 23, 2003 1:08 PM Subject: RE: Struts officially supported at Ford It's certainly good that they're using 1.1, but somewhat unfortunate that they stopped at b2. (snip) -Original Message- From: Hajratwala, Nayan (N.) [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 23, 2003 9:59 AM To: '[EMAIL PROTECTED]' Subject: Struts officially supported at Ford (snip) quote The Ford Servlet Framework is a packaged version of Struts 1.1 provided by and supported by IBM. This download includes Struts provided by IBM with some custom integration of the other Frameworks and services provided by the Java COE. The Java COE will only be supporting the versions of Struts downloaded from here. Application teams should NOT be downloading Struts from the Jakarta website but are encouraged to use the website for learning and documentation. /quote (snip) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Making a Form non-editable
We have a field that at times needs to be non-editable but displayed and other times editable independent of user role. To accomplish that we use a logic:equals tag to determine which to display the active inputs or the read-only display with hidden inputs. If we're displaying read-only, then we carry the actual values in a html:hidden tag and disable the corresponding input tag (e.g., checkbox)... - Original Message - From: Jarnot Voytek Contr AU HQ/SC [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 4:21 PM Subject: RE: Making a Form non-editable I put the form submit button in that tag, they can see everything else. -- Voytek Jarnot Quidquid latine dictum sit, altum viditur. -Original Message- From: Curtney Jacobs [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 7:06 AM To: Struts Users Mailing List Subject: Re: Making a Form non-editable Hello, Acutally, the user can read (see) the data, however, they cannot modify the data. What you are presenting actually prevents the user from seeing the data at all. Correct me if I am wrong. _CJ On Tuesday 21 January 2003 8:30 pm, Jarnot Voytek Contr AU HQ/SC wrote: That's what I do, I wrote a tag as such: myTags:ifUserInRole value=role1,role2 markup in here is only visible to those in role1 or role2 /myTags:ifUserInRole This breaks the 'presentation only' rule a little bit, but makes for a much more user-friendly UI. -- U-Interface.com -- 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]
Re: Making a Form non-editable
Yes, you understand me correctly. An example might be: %-- active checkbox: --% logic:equals name=myForm property=isWritable scope=request value=true html:checkbox name=myField /logic:equals %-- disabled (readonly) checkbox --% logic:equals name=myForm property=isWritable scope=request value=false input type=checkbox checked disabled html:hidden name=myField/ /logic:equals - Original Message - From: Curtney Jacobs [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 8:59 AM Subject: Re: Making a Form non-editable Hello Mark. Just so I don't misuderstand, are you saying that for each input tag there is a corresponding hidden tag. If displaying read-only data, then input tag corresponding hidden tag is shown and the input tag is disabled. Correct?? If my understanding is correct, how do you programmatically disable the input tag? I know the disable attribute has to be set to true. At what point do I do this. I am sorry if the answere to this is obvious :) _CJ On Tuesday 21 January 2003 9:41 pm, Mark Lepkowski wrote: We have a field that at times needs to be non-editable but displayed and other times editable independent of user role. To accomplish that we use a logic:equals tag to determine which to display the active inputs or the read-only display with hidden inputs. If we're displaying read-only, then we carry the actual values in a html:hidden tag and disable the corresponding input tag (e.g., checkbox)... - Original Message - From: Jarnot Voytek Contr AU HQ/SC [EMAIL PROTECTED] To: 'Struts Users Mailing List' [EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 4:21 PM Subject: RE: Making a Form non-editable I put the form submit button in that tag, they can see everything else. -- Voytek Jarnot Quidquid latine dictum sit, altum viditur. -Original Message- From: Curtney Jacobs [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 7:06 AM To: Struts Users Mailing List Subject: Re: Making a Form non-editable Hello, Acutally, the user can read (see) the data, however, they cannot modify the data. What you are presenting actually prevents the user from seeing the data at all. Correct me if I am wrong. _CJ On Tuesday 21 January 2003 8:30 pm, Jarnot Voytek Contr AU HQ/SC wrote: That's what I do, I wrote a tag as such: myTags:ifUserInRole value=role1,role2 markup in here is only visible to those in role1 or role2 /myTags:ifUserInRole This breaks the 'presentation only' rule a little bit, but makes for a much more user-friendly UI. -- U-Interface.com -- 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] -- U-Interface.com -- 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: Struts and Websphere
We've had success using Tomcat v3.3.1 and Struts 1.0.2 for development, and then testing/production on WAS v3.5.x and WAS v4.0. We probably won't try Struts v1.1 until it goes into production status. - Original Message - From: Steve Vanspall [EMAIL PROTECTED] To: Struts User Mailing List [EMAIL PROTECTED] Sent: Sunday, January 19, 2003 10:27 PM Subject: Struts and Websphere Hi there, I just wanted to see if there's anyone here who has succesfully deployed a struts-based web application onWebsphere application server. I am using Tomcat for development, but need to be able to deploy on websphere? As yet I have had no luck. I am using Struts 1.1Beta-1 Eclipse am making the war file using Eclipse, the war file works with tomcat, but not websphere. Websphere pickup my welcome page, it then calls findefault.do, but that causes a 500 error. I think there must be some added setting one of my xml files needs. Can anyone help me out Regards Steve Vanspall -- 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: [OT] Date format
RE: [OT] Date formatWith SimpleDateFormat you specify the format as a String. You surely should be able to display that string. What I am looking for is how to display the *format*, and not how to display a date in a given format. (snip)
Re: Date format
Date formatString myDate = new SimpleDateFormat(dd MMM ).format( new java.util.Date() ); comp.lang.java.programmer is a good news group for java language related questions. - Original Message - From: Suresh Addagalla To: [EMAIL PROTECTED] Sent: Thursday, January 16, 2003 9:55 AM Subject: Date format Hi, Please excuse me for the off-topic question, I need this urgently, so posting it. How can I get the current date format? (style: DateFormat.SHORT, locale: Default) I used: SimpleDateFormat formatter = new SimpleDateFormat() ; String format = formatter.toPattern() ; It gives: M/d/yy hh:mm a But what I want is *only* the date part, excluding the time part of it. Thanks, Suresh
Re: Un Subscribe
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] Please remove me from the mailing list. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Migrating from 1.0 to 1.1 ERRORS
Another potential cause in your case -- if you're using Tomcat 3.2.x, you'll need to upgrade. That version has some nasty bugs in its class loader than make Struts 1.1 not work. Is Tomcat v3.3.1 sufficient for Struts v1.1 (we need to use a Tomcat engine that's like WebSphere v4.0)? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Migrating from 1.0 to 1.1 ERRORS
IMO - I don't mind upgrading to the latest and greatest production release, but that bit me once with WAS incompatibility. If it doesn't have the teeth, it can't bite me again. - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Wednesday, January 15, 2003 4:43 PM Subject: Re: Migrating from 1.0 to 1.1 ERRORS On Wed, 15 Jan 2003, Mark Lepkowski wrote: Date: Wed, 15 Jan 2003 16:07:13 -0500 From: Mark Lepkowski [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Subject: Re: Migrating from 1.0 to 1.1 ERRORS Another potential cause in your case -- if you're using Tomcat 3.2.x, you'll need to upgrade. That version has some nasty bugs in its class loader than make Struts 1.1 not work. Is Tomcat v3.3.1 sufficient for Struts v1.1 (we need to use a Tomcat engine that's like WebSphere v4.0)? It should be. You'll also like the performance improvements of either 3.3.1 or 4.1.18 :-). Note also that 4.1.18 can be used to develop Servlet 2.2/JSP 1.1 apps (compatible with WebSphere v4.0), as long as you're careful to avoid the features from the newer specs. Craig -- 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]
A Struts Haiku
a Struts Haiku model view control struts is good for this model simple it is not
Re: A Struts Haiku
JT, pearls of wisdom Your action is null. So your form will not process. Edit struts-config. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: A Struts Haiku
This bug is fixed in v1.1 version one point one it's pre-prod but it's better waiting for its time Jakarta Struts rules learn it, code it, live it .NET is evil HaikuParsingException: Line 2 must contain 7 sylables in WasteEnormousAmountsOfTime.composePoems James -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: how can I use the tag value in another tag?
Why are JSP scriptlets to be avoided? snip It's considered a good idea to avoid using runtime JSP expression scriptlets... /snip -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: reset doesn't work well
In my experience, the reset condition is the state that the form was in when it was
loaded. So if you have a checkbox set when the form is loaded, uncheck it, and click
[Reset], the checkbox becomes checked again.
- Original Message -
From: Doug Ogateter [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Friday, December 20, 2002 3:37 PM
Subject: reset doesn't work well
Hi:
I have a problem with reset button. In my jsp file, I have
html:reset/. In my form class, I have:
public void reset(ActionMapping mapping, HttpServletRequest request) {
amount = null;
password = null;
}
in the struts-config.xml file, it has:
actionpath=/xxx
type=yyy
name=myForm
scope=request
input=/zzz.jsp
forward name=success path=/zzz.jsp/
/action
I filled out the fields, if I click reset button before submit the form,
the fields are cleared. But if I submit the form first, and it detects
some error(for example: the password is not correct), the form is showed
with error message. In this case, when I click reset button, the fields
are not cleared. What is wrong with this. I really want the fields can
be cleared if errors are detected. Could someone help me out?
Thanks.
Doug
-
Post your free ad now! Yahoo! Canada Personals
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: how to assign values to hidden form variables
how about: html:hidden property=myProperty/ how to assign values to hidden parameters in a form using struts? -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: session form bean reuse
How do you get session A information available to session B without persisting it somehow (the HttpSessionContext interface is depracated in Java Servlet API v2.1for security reasons...)? Struts will not itself reuse form bean instances across sessions (although your application could copy one if it really wanted to).
Re: session form bean reuse
How do you get session A information available to session B without persisting it somehow (the HttpSessionContext interface is depracated in Java Servlet API v2.1for security reasons...)? (snip) Use servlet context attributes to share information between all the sessions in your webapp. Thanks for the info. I knew there had to be something in the servlet scope, but didn't know quite where to find it. The following works in any of our classes that extend Action: servlet.getServletContext().setAttribute( myAttribute, myAttribute ); and likewise MyAttribute myAttribute = (MyAttribute)servlet.getServletContext().getAttribute( myAttribute ); I noticed that: - servlet is declared a protected transient ActionServlet in ActionServletWrapper, - ActionForm has the getter method for the wrapper, - RequestUtils.populate() calls the getter, - ActionServlet calls RequestUtils.populate() What I don't follow is how the servlet object is exposed in the Action subclasses. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Page flow diagrams for Struts
napkins work well. they are usually folded so you can open them for more writing surface. the drawback is the paper is thin and sometimes will tear, but if you use ballpoint the advantage is it can be used to wipe coffee spills. - Original Message - From: Nick Sharples To: [EMAIL PROTECTED] Sent: Thursday, November 21, 2002 9:43 AM Subject: Page flow diagrams for Struts Hi all, I was wondering if anyone has a good diagramatic representation of page flow that also captures forms and Action processing from submit buttons and links. I've have my own representation of course, but I was wonder what other people do. I suppose what I'm really after is a good story boarding technique that I can standardise on. Cheers ..Nick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Struts file upload validation problem
You could have the user enter the meta data first, and then after it's validated let the user choose the file to upload. - Original Message - From: Poynter, Stephen To: Struts Users Mailing List (E-mail) Sent: Wednesday, November 20, 2002 12:03 PM Subject: Struts file upload validation problem I have just written a document upload tool for a customer using the struts upload functionality. My upload jsp consists of one form that is of course a multipart/form-data form. The form consists of the file field along with other text fields where the user enters various information( owner, title, etc.) about the file to be uploaded. The problem I'm having is that once you submit the form struts immediately starts uploading the file before any of the other data in the form is validated. So, in my case, the user tries to upload a large file but enters invalid information for the other text fields. Struts then uploads the file before validating the form data. So when the user corrects their mistake they have to re-upload the file yet again. Is it possible to have the form data validated before the file is uploaded? I would rather not use javascript for error checking. Any help is appreciated. Thanks... Steve -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
