RE: retrieve value of Request
U might mean... request.setAttribute(mode,new Integer(1)); ..in your action. Anyway, to use is in your jsp: bean:write name=mode scope=request/ ... although scope is not required. -Yves- -Original Message- From: Raman [mailto:[EMAIL PROTECTED] Sent: Friday, December 19, 2003 4:24 PM To: Struts Users Mailing List Subject: retrieve value of Request Hello, I have a query regarding use of struts to get the request variable value. I populate a variable in request in my Action as request.setAttribute(mode,1); now how can print the value of this variable using bean:write tag Help me in this... Thanks Raman Garg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: html:img is not getting recognised.
Struts already appends the context path. html:img src=./images/cal.gif onClick=popUpCalendar(this, ParameterEditForm.endDate, 'dd-mmm-',46,735) / ...should be enough -Yves- -Original Message- From: Amit Kumar Sharma [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 17, 2003 4:33 PM To: Struts Users Mailing List Subject: html:img is not getting recognised. Dear friends, I am substituting the normal HTML image tag img src=%=contextPath%/images/cal.gif onClick=popUpCalendar(this, ParameterEditForm.endDate, 'dd-mmm-',46,735) with the shown below but is not getting recognised, can somebody guide me out how to use it, I am new to struts. html:img src=%=contextPath%/images/cal.gif onClick=popUpCalendar(this, ParameterEditForm.endDate, 'dd-mmm-',46,735) / Regards, Amit Kumar Sharma SysArris Software Pvt Ltd 120A, Elephant Rock Road, 3rd Block, Jayanagar, Bangalore - 560011 Tel.: 91-80-665 4965 / 665 5052 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: validation and DynaActionForm / concrete question
Hi Marco! I think using only one jsp wherein the number of form elements vary according to what you are doing can be considered as anti-pattern and is more of a JSP Model 1 design. The best way to make things work is to use a separate JSP for each form so that you can properly associate a separate ActionForm with each ActionMapping. If you wish to continue with the single jsp solution and still wish to use DynaValidatorForm, you can write your own Validator class and declare it in the validator-rules.xml. That way you can control how it will behave and validate the parameters... -Yves a.k.a. the witness to your long debates with Chad regarding morality and politcs :o) -Original Message- From: Marco Mistroni [mailto:[EMAIL PROTECTED] Sent: Thursday, December 18, 2003 1:30 AM To: 'Struts Users Mailing List' Subject: RE: validation and DynaActionForm / concrete question Hi Wendy, Only a little problem.. I haven't written any class for my DynaActionForm. Instead, I declare all the properties in the struts-config.xml Struts does all the rest But, anyway, can u give more details on ur solution to my problem? Regards marco -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 17 December 2003 17:06 To: Struts Users Mailing List Subject: RE: validation and DynaActionForm / concrete question well i think the problem your having is because you're using a dispatch action so the form is mapped to the action and its set to validate. You can either separte yu dispatch actions into standard actions or hack it by having a single action that calls your dispatch action much like you were suggesting doing with jsp. What about LookupDispatchAction? It uses a request parameter to figure out which method to call. I use it with hidden form fields and a bit of JavaScript. In Marco's case, overriding the validate method might work. Only call super.validate() if all of the parameters are present. -- Wendy Smoak Application Systems Analyst, Sr. ASU IA Information Resources Management - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Reloading of application resources
Create a thread in your cache manager that polls for changes in the timestamp of the properties file, say, every 5000 ms and reloads it when a new one is detected. Of course a clustered environment will complicate things a little bit but that's a another story :o) -Yves- -Original Message- From: Nicklas Karlsson [mailto:[EMAIL PROTECTED] Sent: Monday, December 15, 2003 5:10 PM To: [EMAIL PROTECTED] Subject: Reloading of application resources Hello, We have a singleton factory that watches/caches/delivers up-to-date ResourceBundles of property files based on the timestamp of the watched file. What would be the natural way of refreshing (and triggering a refresh) of a watched ApplicationResources.properties file so that e.g. a change in a language label would immediately be visible? --- Nicklas Nik Karlsson, Murkiogatan 3 B 29 20740 Åbo, 040 9000 724 [EMAIL PROTECTED] ::: http://www.abo.fi/~nickarls ::: [EMAIL PROTECTED] If a man speaks in the forest and there is no woman around to hear him - Is he still wrong? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Weblogic 6.1 SP5 JSP Compilation problems
Thought everyone concerned would be interested to know that Weblogic 6.1 SP5 (SP4 was working fine) has a problem compiling JSP pages when bean:define is used to expose a scripting variable. Example: bean:define id=myObject name=theObject scope=session type=whatever/ % myObject.myMethod(); % This produces a compilation problem by weblogic. Apparently in the SP5, it evaluates the scriptlets first before the custom tags, hence, Cannot resolve symbol 'myObject' is produced. The code was working fine until we upgraded to SP 5 which produced the errors.
ActionErrror messages from relational database
Anybody know how I can use error messages with ActionErrors that come from the database and not from the properties file?
RE: Weblogic 6.1 Compatibility Problems
Service pack 4 for Weblogic is already installed actually... We've already resorted to using a custom tag to convert primitive data type outputs to String. -Original Message- From: Mark Galbreath [mailto:[EMAIL PROTECTED] Sent: Monday, June 02, 2003 10:27 PM To: 'Struts Users Mailing List' Subject: RE: Weblogic 6.1 Compatibility Problems Yes, SP3 for WebLogic 6.1, not Windoze. -Original Message- From: Yves Sy [mailto:[EMAIL PROTECTED] Sent: Sunday, June 01, 2003 9:18 PM To: Struts Users Mailing List Subject: RE: Weblogic 6.1 Compatibility Problems i'm using XP. and anyway, its more tied with the weblogic implementation i think... -Original Message- From: Mark Galbreath [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 9:42 PM To: 'Struts Users Mailing List' Subject: RE: Weblogic 6.1 Compatibility Problems Have you installed Service Pack 3? It fixes weirdness that was screwing up my 1.0.1 app last summer. Mark -Original Message- From: Yves Sy [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:54 AM To: [EMAIL PROTECTED] Subject: Weblogic 6.1 Compatibility Problems Hi! I am currently involved in a project that uses Struts 1.1 (RC1) on Weblogic 6.1. We noticed that there seems to be a problem with Struts' bean:write tag when the property in the bean that we want to display is NOT of type String. The String properties display fine but properties of other types such as int produce a Cannot find key org.apache.struts.action.ACTION_MESSAGE error message or something similar to that. We were able to confirm that our bean does indeed contain the int value we want to display because it worked just fine when we used a scriptlet to display it. To elaborate: bean:write name=myBean property=myProperty.name/ works fine because name is a String... but... bean:write name=myBean property=myProperty.id/ does not work since id is of type int. Anyone aware of this problem with Weblogic 6.1? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Weblogic 6.1 Compatibility Problems
i'm using XP. and anyway, its more tied with the weblogic implementation i think... -Original Message- From: Mark Galbreath [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 9:42 PM To: 'Struts Users Mailing List' Subject: RE: Weblogic 6.1 Compatibility Problems Have you installed Service Pack 3? It fixes weirdness that was screwing up my 1.0.1 app last summer. Mark -Original Message- From: Yves Sy [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:54 AM To: [EMAIL PROTECTED] Subject: Weblogic 6.1 Compatibility Problems Hi! I am currently involved in a project that uses Struts 1.1 (RC1) on Weblogic 6.1. We noticed that there seems to be a problem with Struts' bean:write tag when the property in the bean that we want to display is NOT of type String. The String properties display fine but properties of other types such as int produce a Cannot find key org.apache.struts.action.ACTION_MESSAGE error message or something similar to that. We were able to confirm that our bean does indeed contain the int value we want to display because it worked just fine when we used a scriptlet to display it. To elaborate: bean:write name=myBean property=myProperty.name/ works fine because name is a String... but... bean:write name=myBean property=myProperty.id/ does not work since id is of type int. Anyone aware of this problem with Weblogic 6.1? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Weblogic 6.1 Compatibility Problems
ok thnx i'll try that... but i've done several apps in tomcat and another in jboss and they are rendering it OK. so my guess is it probably is a weblogic implementation problem more than anything else... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Melissa L Kelley Sent: Friday, May 30, 2003 10:13 PM To: Struts Users Mailing List Subject: Re: Weblogic 6.1 Compatibility Problems On Fri, 30 May 2003, Yves Sy wrote: Pardon me for not looking at the source to confirm this, but my guess on what your problem is that the bean tag will try to convert your bean property to a String before rendering it. Try making your property an Integer instead of an int and see if it renders correctly. --Melissa Hi! I am currently involved in a project that uses Struts 1.1 (RC1) on Weblogic 6.1. We noticed that there seems to be a problem with Struts' bean:write tag when the property in the bean that we want to display is NOT of type String. The String properties display fine but properties of other types such as int produce a Cannot find key org.apache.struts.action.ACTION_MESSAGE error message or something similar to that. We were able to confirm that our bean does indeed contain the int value we want to display because it worked just fine when we used a scriptlet to display it. To elaborate: bean:write name=myBean property=myProperty.name/ works fine because name is a String... but... bean:write name=myBean property=myProperty.id/ does not work since id is of type int. Anyone aware of this problem with Weblogic 6.1? -- Melissa L Kelley [EMAIL PROTECTED] www.stuology.net -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Weblogic 6.1 Compatibility Problems
Hi! I am currently involved in a project that uses Struts 1.1 (RC1) on Weblogic 6.1. We noticed that there seems to be a problem with Struts' bean:write tag when the property in the bean that we want to display is NOT of type String. The String properties display fine but properties of other types such as int produce a Cannot find key org.apache.struts.action.ACTION_MESSAGE error message or something similar to that. We were able to confirm that our bean does indeed contain the int value we want to display because it worked just fine when we used a scriptlet to display it. To elaborate: bean:write name=myBean property=myProperty.name/ works fine because name is a String... but... bean:write name=myBean property=myProperty.id/ does not work since id is of type int. Anyone aware of this problem with Weblogic 6.1? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
