Re: Yellow background color in text fields?

[Andrew Shirk]

Your google toolbar?

At 04:00 PM 2/11/2004, you wrote:
With the following code the text field background for email is yellow, 
even though the background for password is white.  I have nothing in my 
css that should trigger this.  If I change the designation "email" to 
"password" the yellow background goes away.  Anyone have any clue about 
what is causing this:

  




  

  
  




  

  


-
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: URGENT - Help defending Struts

[Andrew Shirk]

www.roomandboard.com
http://www.retrospecthome.com
At 09:48 AM 12/18/2003, you wrote:
All:



Our CIO is currently fighting the use of Struts by saying that it is not
widely used in B2C sites.  Does anyone know of any sites, preferably
commerce sites that are using Struts?  This would be extremely helpful.


The issue is that the CIO is looking for sites that may be similar to
ours that are using Struts already.


Thanks very much,

Russell



[EMAIL PROTECTED]

310-426-5587





This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information.  If you have 
received it in error, please notify the sender immediately and delete the 
original.  Any other use of the email by you is prohibited.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Container-Managed Authentication in web.xml vs . Specifying Paths in the struts-config.xml

[Andrew Shirk]

Logical paths work fine for me in web.xml (using tomcat 4.1.x):

  
 FORM
 

   /do/login/edit


   /do/login/fail

 
  
Andrew

At 03:11 PM 10/7/2003, you wrote:
People answer questions without reading my original
post.  Therefore, I must re-type my original question
again.
Before I posted my question, I had configured the
Tomcat JDBCRealm following the instructions at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/realm-howto.html
so that I can do security testing programmically, such
as isUserInRole(), in my program.
If I use form based authentication, I insert the
 and its sub-elements in my web.xml file
(see below).  As we know, the  and
 are required.
My question is that the container-managed
authentication (we provide login page and error page
in the web.xml) does not seem to be consistent with
what we usually do in struts; e.g. we state the
logical name and path for each .jsp page in the
struts-config.xml file.
What is the Struts convention in dealing with user
authentication?  Should we specify the paths for the
logon page and error page in the struts.config.xml or
we should use the  and
 in the web.xml file?
Thanks.
--- "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote:
> Caroline Jen wrote:
>
> >But, I do not want to use BASIC authentication.  I
> >have many different roles and hundreds of people
> per
> >role.  Users' name, role, etc. are stored in a
> >database.
> >
> How authentication is performed (BASIC, form-based,
> DIGEST, or SSL
> client certificates) and how users are stored
> (database, directory
> server, local XML file, ...) are two separate
> questions.  For most
> servers , any combination is possible.  With Tomcat,
> for example, you
> can configure JDBCRealm to point at your user and
> role definitions in a
> database, and then use those users with any of the
> authentication
> methods.  For more information, see:
>
>
>
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/realm-howto.html
>
> The choice between BASIC and form-based
> authentication, then, can be
> based on user interface related concerns, rather
> than worrying about a
> database.
>
> Craig
>
> >--- Matt Raible <[EMAIL PROTECTED]> wrote:
> >
> >
> >>A JDBCRealm can use BASIC authentication - it
> >>doesn't require form-based.
> >>Here's an example app that might help you out:
> >>
> >>
> >>
> >>
>
>http://raibledesigns.com/wiki/Wiki.jsp?page=SecurityExample
> >
> >
> >>HTH,
> >>
> >>Matt
> >>
> >>-Original Message-
> >>From: Caroline Jen [mailto:[EMAIL PROTECTED]
> >>Sent: Monday, October 06, 2003 4:45 PM
> >>To: [EMAIL PROTECTED]
> >>Subject: Container-Managed Authentication
> >> in web.xml vs.
> >>Specifying Paths in the struts-config.xml
> >>
> >>
> >>I use the Tomcat.  I configured the Tomcat
> JDBCRealm
> >>so that I can use programmic security testing,
> such
> >>as
> >>isUserInRole(), in my program.
> >>
> >>Because Tomcat JDBCRealm is form based, I inserted
> >>the
> >> and its sub-elements in my web.xml
> >>file
> >>(see below).  As we know, the 
> and
> >> are required.
> >>
> >>My question is that the container-managed
> >>authentication does not seem to be consistent with
> >>what we usually do in struts; e.g. we state the
> >>logical name and path for each .jsp page in the
> >>struts-config.xml file.
> >>
> >>What is the Struts convention in dealing with user
> >>authentication?  Should we specify the paths for
> the
> >>logon page and error page in the struts.config.xml
> >>or
> >>we should use the  and
> >> in the web.xml file?
> >>
> >>
> >>
> >>
>
>==
> >
> >
> >>
> >>   
> >>
> >>SalesInfo
> >>  /SalesInfo/*
> >>  GET
> >>  POST
> >>   
> >>   
> >>  manager
> >>   
> >>   
> >>
> >>NONE
> >>   
> >>
> >>
> >>
> >>   FORM
> >>   
> >>
> >>
> >>
> >>
>
>/authentication/login.html
> >
> >
> >>
> >>
> >>
> >>
>
>/authentication/error.html
> >
> >
> >>
> >>
> >>
> >>
> >>
> >>   manager
> >>
> >>
> >>
> >>
> >>
> >>__
> >>Do you Yahoo!?
> >>The New Yahoo! Shopping - with improved product
> >>search
> >>http://shopping.yahoo.com
> >>
> >>
> >>
> >>
>
>-
> >
> >
> >>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]
> >>
> >>
> >>
> >
> >
> >__
> >Do you Yahoo!?
> >The New Yahoo! Shopping - with improved product
> search
> >http://shopping.yahoo.com
> >
>
>-
> >To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> >For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
> >
>
>
>
>
---

RE: [OT] Web Services, what have I done?

[Andrew Shirk]

Yes, SOAP, WSDL and UDDI are THE standards for web services. The primary 
motivation for web services is interoperability among disparate systems. 
Without the using the standards, you won't get the interoperability. The 
Java Web Services Developer Pack (JWSDP - http://java.sun.com/webservices/) 
from Sun including JAX-RPC make it relatively painless to develop your web 
service in a standardized way. You should probably also read the tutorial: 
http://java.sun.com/webservices/docs/1.2/tutorial/doc/index.html

Andrew

At 10:35 AM 8/21/2003 -0400, you wrote:
Many thanks for your input,

I am trying to justify converting my implementation to use SOAP and
WSDL. My main concern is in the complexities that this would introduce
into this web service. If a large majority of developers out there are
not familiar with SOAP and WSDL it might add a large learning curve for
the clients of the web service.
Is this standard really taking off, enough to justify my time and
efforts in the conversion and my clients in learning SOAP and WSDL or am
I in the dark and most already know it?
One of my main objectives right now is to document the web service and
love the idea of being able to use WSDL to do it. Having to document my
whole implementation will take some time and would prefer only having to
document the RPC's and functionality not to mention using a commercial
approach that probably handles many issues I have not yet encountered.
Greg



 -Original Message-
> From: Andrew Hill [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 20, 2003 11:58 PM
> To: Struts Users Mailing List
> Subject: RE: [OT] Web Services, what have I done?
>
> Im just getting started looking at web services myself , so dont have
a
> detailed technical grasp, but a seminar I attended a couple of days
ago is
> still fresh in my mind so Ill have a go at fielding this one...
>
> What you have done would fit into the 'academic' definition of a 'web
> service quite nicely'. Of course it doesn't make use of the standards
> (SOAP,
> WSDL) which means its a proprietary implementation of a web service
and
> for
> anyone to use it they would have to use your methodology and message
> format.
> Roughly speaking, your dtd seems to be taking the place of of the wsdl
> document, and your own xml format taking the place of the SOAP
envelope &
> data.
>
> The 'popular' conception of a web service is of course one that
involves
> the
> use of SOAP, WSDL, UDDI and such like, so when you talk about 'web
> services'
> this is what comes to peoples minds.
>
> Id most strongly suggest that you now convert (or investigate how
> difficult
> it would be to convert) what you have done to make use of soap and
wsdl to
> make it easier for others to make use of your service. Having
reinvented
> parts of those wheels yourself, you will probably find it a quite
> interesting exercise to see how what you do compares with the
standards.
> With the knowledge you gained doing it your way, you should find
learning
> the standard way much easier as you will see much of the reasoning
behind
> things in the standard having covered that ground yourself already!
>
> You will want to take a look at the AXIS project first as you will
> probably
> want to make use of it:
> http://ws.apache.org/axis/
>
> IBM are pretty big on Web Services (and have donated a ton of web
services
> stuff to the opensource community) so go take a look at whats
available on
> their developerWorks site:
> http://www-106.ibm.com/developerworks/webservices/
>
> And of course the w3c web service stuff is at:
> http://www.w3.org/2002/ws/
>
> And the WS-I at:
> http://www.ws-i.org/
>
>
>
>
> -Original Message-
> From: Greg Hess [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 21 August 2003 03:11
> To: Struts
> Subject: [OT] Web Services, what have I done?
>
>
> Hi All,
>
> This post might seem odd but I am looking for some insight into a
solution
> that I have implemented. I am trying to get a better understanding of
how
> my
> implementation fits into the grand scheme of a Web Service and how I
might
> document this implementation. I have been reading about WSDL and about
> SOAP
> and am still not sure what I have done J, and how my implementation is
> compatible or not compatible with what the industry is calling a Web
> Service
> mainly for documentation purposes even though I would love to build
this
> functionality based on industry standards.
>
> I have built a web app using STRUTS of course that allows for external
> remote systems to invoke RPC's (Remote Procedure Call) on an area of
the
> apps functionality. I allow remote systems to communicate using XML
over
> HTTP POST. Communication involves the invocation request and response.
I
> have created a invocation.dtd that defines the invocation data
structure
> and
> all the supported methods and arguments and the response.dtd that
defines
> the result data structure returned by any invocation.
> As far as I can understand so far this is very sim

Re: Nesting

[Andrew Shirk]

The struts-nested taglib that ships with Struts.

At 06:05 PM 3/5/2003 +0200, you wrote:
For adding  which tag lib do I have to add?

yaron
- Original Message -
From: "Andrew Shirk" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
Sent: Wednesday, March 05, 2003 5:25 PM
Subject: Re: Nesting 
> Try using the method I suggested in this message:
> http://marc.theaimsgroup.com/?l=struts-user&m=104575299502257&w=2
> At 03:53 PM 3/5/2003 +0100, you wrote:
>
> >Hi Sundar,
> >
> >I tried it both ways, but I _always_ get a Jsp compile error, saying
> >that _jspx_xxx_1 is already defined, where xxx stands for the
> >id-attribute (e.g. "element") of the inner  !
> >
> > > I've had luck with patterns similar to what others have suggested, but
> > > if you have plain lists or vectors inside lists or vectors.. a better
> > > route to go is to try
> > >   
> > >   
> > >  
> > >   
> > > I don't happen to have my examples handy (I'm still at home :), but
> > > hope you get the idea.
> > >
> > > As another person suggested if you have the inner "element" defined as
> > > a bean property on the object bound to "row".. then you can use
> > > name/property as well.
> > >
> > > The scoping gotchas of struts are plenty -- this is one of them that I
> > > stumble across often :)
> > >
> > >
> >
> >--
> >
> >
> >-
> >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: Nesting

[Andrew Shirk]

Try using the method I suggested in this message:
http://marc.theaimsgroup.com/?l=struts-user&m=104575299502257&w=2
At 03:53 PM 3/5/2003 +0100, you wrote:
Hi Sundar,

I tried it both ways, but I _always_ get a Jsp compile error, saying
that _jspx_xxx_1 is already defined, where xxx stands for the
id-attribute (e.g. "element") of the inner  !
> I've had luck with patterns similar to what others have suggested, but
> if you have plain lists or vectors inside lists or vectors.. a better
> route to go is to try
>   
>   
>  
>   
> I don't happen to have my examples handy (I'm still at home :), but
> hope you get the idea.
>
> As another person suggested if you have the inner "element" defined as
> a bean property on the object bound to "row".. then you can use
> name/property as well.
>
> The scoping gotchas of struts are plenty -- this is one of them that I
> stumble across often :)
>
>
--

-
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: More Than Form On A JSP

[Andrew Shirk]

One method would be to encode the form info into the urls of the next and 
previous button links. Then in your action, get the request parameters and 
populate the form.

At 02:38 PM 2/26/2003 -0800, you wrote:
I am developing an architecture for the rest of my
development staff to use on a new J2EE project
starting next month.
I have the following situation:

A JSP contains a form which allows the user to lookup
a list of information. For example, if you enter an
SSN the JSP will display some demographic information
about the person associated with the SSN (first name,
last name, etc) along with a list in an HTML table of
payment history.
The HTML table displays a subset of data, say 10 rows
at a time. The total number of rows could be much
higher. The table comes with buttons to navigate
through the next and previous rows in the table.
The point is the user can display the "previous" and
"next" items in the table while the demographic
information at the top remains displayed.
The HTML table is built using a custom taglib I've
developed. I also wrote a custom Action, called
NavigateAction, which handles all the logic associated
with clicking "previous" and "next". I've wrapped the
HTML table in a form so that Struts can direct it to
NavigateAction. NavigateAction gets the next 10 rows
of data, puts them into the request object, and
forwards to the same page we came from. Finally, the
taglib builds the table from the data stored in the
request. All that is working fine.
All this allows my developers to reuse this HTML table
logic on any JSP that has a similar appearance (static
data at the top and scrollable data at the bottom).
There is a problem however. After the page is
redisplayed, the top part of the page contains no
data. All of it has been lost because the form
associated with it is out of scope (it was scoped to
the request).
I don't want to scope the forms to the session as they
will accumulate as the user navigates through the
application, plus the data in them will be stale if
the user returns to a JSP they were at a while ago.
Does anyone have any ideas how to solve this?

__
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
-
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: Passing parameters to Actions

[Andrew Shirk]

No need for that either since the superclass constructor is implicitly called.

At 01:38 PM 2/25/2003 -0700, you wrote:
maybe a super() call in the constructor. But you shouldn't need anymore than
that.
Brandon Goodin
Phase Web and Multimedia
PO Box 85
Whitefish MT 59937
P (406) 862-2245
F (406) 862-0354
[EMAIL PROTECTED]
http://www.phase.ws
-Original Message-
From: Guido [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 1:32 PM
To: Struts Users Mailing List
Subject: RE: Passing parameters to Actions
I wonder if MyExtendedActionMapping is as simple as:

public class MyExtendedActionMapping extends ActionMapping {
private String xxx;
public void setXXX(String xxx) { this.xxx = xxx; }
public String getXXX() { return xxx; }
}
Should I implement any other method...?

Thanks.


Guido García Bernardo
[EMAIL PROTECTED]
Spain is different.
On Tue, 25 Feb 2003, Brandon Goodin wrote:

} Here is a config sample:
}
} 
} 
} 
} 
} 
-
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: Nested iterate tags

[Andrew Shirk]

Using the nested:iterate inside of logic:iterate should work. I've modified 
the code below, but of course have not tested this.



">
name="comp" property="component_ID"/>





">
property="part_ID"/>

property="description"/>






At 07:32 PM 2/19/2003 -0500, you wrote:
Hi, I'm hoping someone can help me out.

I have a vector object where each element contains an object, which has
another vector element.

I need to traverse through the first one, while inside the loop, also
traversing the vector within each object.

Can someone give me a lead on how can this possibly be accomplished.

I've tried just nesting one iterate tag within the other and use the
first one's item property for the second one's iteration, but I keep
getting an error that even my outter iterate is telling me that it can't
find a getter method, which exists.



">




">






Can someone please help or give a simple example.

Thanks.

Ilya

-
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: Re[4]: [OT] conn pooling - what next?

[Andrew Shirk]

Hi Rick,

My understanding is that people still successfully use Poolman in 
production environments. However, I would be worried about using any 
product that will likely never be updated. Over the weekend, I migrated 
one of my apps from Poolman to Tomcat 4.1.9 connection pooling (which 
uses commons-dbcp). Flakiness that I had experienced with Poolman 
(probably due to a mis-configuration problem that I couldn't pinpoint) 
seemed to vanish using Tomcat, and as an added bonus, I was able to rid 
myself of a configuration file! Performance seems just as good, and I 
have the piece of mind of knowing that I'm using a codebase that is 
evolving and will be updated. It's super easy to set up using the 
documentation at: 
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html
And yes it does provide, as an option, the ability to validate 
connections. This is mentioned in the documentation.

There is one small typo in the configuration information though. Where 
it says:

 
   user
   dbusername
 

should actually be:

 
   username
   dbusername
 

Andrew

On Tuesday, August 27, 2002, at 10:23  AM, Rick Reumann wrote:

> On Tuesday, August 27, 2002, 11:10:53 AM, Kevin wrote:
>
> KAS> If you're not concerned about these other errors, then Poolman
> KAS> (if you can still find it) might be a good fit. If I remember
> KAS> correctly, you could specify a SQL statement for it to execute
> KAS> ("select 1 from dual") before allocating a connection from the
> KAS> pool. If it got a SQLException, it would establish a new
> KAS> connection and return that.
>
>  That would be perfect! So just a few questions:
>
>  1) Should I be weary of going to with Poolman if it's not being
> supported anymore?
>  2) Does anyone know if the struts or tomcat pooling behaves like
> above (as an option maybe?) where it will check to see if a
>  connection is valid before allocating it?
>  3) Drawbacks going wtih poolman over some other solutions?
>
>
>  Thanks again!
>
>
>
> --
>
> Rick
> mailto:[EMAIL PROTECTED]
>
>
> --
> To unsubscribe, e-mail:    [EMAIL PROTECTED]>
> For additional commands, e-mail:  [EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: SOLVED: Losing my sanity: 1.1b & Validator problems

[Andrew Shirk]

Not sure what you mean here. My understanding was that .do was only 
necessary for sub-applications.

On Wednesday, August 21, 2002, at 04:17  PM, Richards, Devin N (Devin) 
wrote:

> What about using *.do not path mapping with /do/*, I know that 1.1 
> likes the *.do better.
>
> web.xml:
> 
>
> 
> action
> *.do
> 
>
> -Devin
>
>
>
>
> -Original Message-
> From: Andrew Shirk [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 4:46 PM
> To: Struts Users Mailing List
> Cc: [EMAIL PROTECTED]
> Subject: SOLVED: Losing my sanity: 1.1b & Validator problems
>
>
> I think it's time for a beer.
>
> I changed my action mapping definition from:
>
> type="com.myapp.action.RegistrationAction"
>  name="registrationForm"
>  validate="true"
> parameter="save"
> scope="request"
> input="/registration.jsp">
> 
>  path="/do/registration/confirm"/>
>   
>
>
> to:
>
>   name="registrationForm"
> type="com.myapp.action.RegistrationAction"
>input="/registration.jsp"
>scope="request"
>parameter="save"
> validate="true">
>
> path="/do/registration/confirm"/>
>  
>
> and it worked.
>
> Andrew
>
>
> On Wednesday, August 21, 2002, at 11:17  AM, Richards, Devin N (Devin)
> wrote:
>
>> You have all of your validations in the XML?
>> Have you tried adding the  to the
>> JSP page to see if the validation is working correctly? Once you have
>> this you can "view source" and see the validation code it generated.
>> This will show you if the validator plug-in is setup correctly and that
>> your XML is correct.
>>
>> BTW: we are most likely going to production on 1.1-b2
>>
>> Good luck.
>>
>> -Devin
>>
>> -Original Message-
>> From: Andrew Shirk [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, August 21, 2002 12:13 PM
>> To: Struts Users Mailing List
>> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>> Subject: Re: Losing my sanity: 1.1b & Validator problems
>>
>>
>> Devin, thanks for further the further explanation. I replied to your
>> previous email earlier this morning, but it seems to have been lost in
>> the ether. Anyway, I also tried including super.validate() in my form
>> bean, which confirmed that Validation is in fact being done. The 
>> mystery
>> is why validation is being performed but control is never returned to
>> the JSP. It simply dies. No error. Nothing. I didn't change anything in
>> the code when moving to 1.1b, so am beginning to wonder if this is a 
>> bug
>> of some sort.
>>
>> I've spent way too many hours trying to track down the problem and may
>> have to just go back to 1.1a if I can't find a solution today.
>>
>> Thanks again for the help.
>>
>> Andrew
>>
>> On Wednesday, August 21, 2002, at 10:16  AM, Richards, Devin N (Devin)
>> wrote:
>>
>>> I had some validation that was done in the validation.xml
>>> (required/minlenght etc) and then I wanted to do some business rule
>>> validation that I could not do in the XML. When I put the code into my
>>> form bean's validate() method, I got all of the business validations,
>>> but none of my basic required/minlenght validations that were done in
>>> the XML. Once I added a call to super.validate() it picked them up.
>>>
>>> Here is part of the struts-config.xml:
>>> >> path="/rmaFormSubmit"
>>> name="rmaForm"
>>> type="com.lucent.portal.rma.RmaFormAction"
>>> input="rmaFormDef"
>>> scope="request"
>>> parameter="submit"
>>> validate="true">
>>> 
>>> 
>>>
>>> 
>>> >> value="/WEB-INF/validator-rules.xml,
>>> /WEB-INF/validation.xml,
>>> /WEB-INF/classes/com/lucent/portal/rma/RmaValidation.xml" />
>>> 
>>>
&

Re: SOLVED: Losing my sanity: 1.1b & Validator problems

[Andrew Shirk]

Funky results indeed. However, it's clear the order is not strictly 
enforced. Struts's own example application and online documentation have 
example after example of "out of order" parameters. Actually, I'm pretty 
sure my mapping was originally copy and pasted from the example 
application.

On Wednesday, August 21, 2002, at 03:38  PM, Jerry Jalenak wrote:

> Andrew,
>
> It's been my experience that if you don't specify parameters in the 
> order
> the DTD specifies, you can get some funky results..
>
> Jerry
>
>> -Original Message-
>> From: Andrew Shirk [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, August 21, 2002 3:46 PM
>> To: Struts Users Mailing List
>> Cc: [EMAIL PROTECTED]
>> Subject: SOLVED: Losing my sanity: 1.1b & Validator problems
>>
>>
>> I think it's time for a beer.
>>
>> I changed my action mapping definition from:
>>
>>   >  type="com.myapp.action.RegistrationAction"
>>  name="registrationForm"
>>  validate="true"
>> parameter="save"
>> scope="request"
>> input="/registration.jsp">
>> > path="/registration.jsp"/>
>> > path="/do/registration/confirm"/>
>>   
>>
>>
>> to:
>>
>>  > name="registrationForm"
>> type="com.myapp.action.RegistrationAction"
>>input="/registration.jsp"
>>scope="request"
>>parameter="save"
>> validate="true">
>>
>>> path="/do/registration/confirm"/>
>>  
>>
>> and it worked.
>>
>> Andrew
>>
>>
>> On Wednesday, August 21, 2002, at 11:17  AM, Richards, Devin
>> N (Devin)
>> wrote:
>>
>>> You have all of your validations in the XML?
>>> Have you tried adding the > formName="yourForm"> to the
>>> JSP page to see if the validation is working correctly?
>> Once you have
>>> this you can "view source" and see the validation code it
>> generated.
>>> This will show you if the validator plug-in is setup
>> correctly and that
>>> your XML is correct.
>>>
>>> BTW: we are most likely going to production on 1.1-b2
>>>
>>> Good luck.
>>>
>>> -Devin
>>>
>>> -Original Message-
>>> From: Andrew Shirk [mailto:[EMAIL PROTECTED]]
>>> Sent: Wednesday, August 21, 2002 12:13 PM
>>> To: Struts Users Mailing List
>>> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
>>> Subject: Re: Losing my sanity: 1.1b & Validator problems
>>>
>>>
>>> Devin, thanks for further the further explanation. I replied to your
>>> previous email earlier this morning, but it seems to have
>> been lost in
>>> the ether. Anyway, I also tried including super.validate()
>> in my form
>>> bean, which confirmed that Validation is in fact being
>> done. The mystery
>>> is why validation is being performed but control is never
>> returned to
>>> the JSP. It simply dies. No error. Nothing. I didn't change
>> anything in
>>> the code when moving to 1.1b, so am beginning to wonder if
>> this is a bug
>>> of some sort.
>>>
>>> I've spent way too many hours trying to track down the
>> problem and may
>>> have to just go back to 1.1a if I can't find a solution today.
>>>
>>> Thanks again for the help.
>>>
>>> Andrew
>>>
>>> On Wednesday, August 21, 2002, at 10:16  AM, Richards,
>> Devin N (Devin)
>>> wrote:
>>>
>>>> I had some validation that was done in the validation.xml
>>>> (required/minlenght etc) and then I wanted to do some business rule
>>>> validation that I could not do in the XML. When I put the
>> code into my
>>>> form bean's validate() method, I got all of the business
>> validations,
>>>> but none of my basic required/minlenght validations that
>> were done in
>>>> the XML. Once I added a call to super.validate() it picked them up.
>>>>
>>>> Here is part of the struts-config.xml:
>>>>>>>path="/rmaFormSubmit"
>>>>  

SOLVED: Losing my sanity: 1.1b & Validator problems

[Andrew Shirk]

I think it's time for a beer.

I changed my action mapping definition from:

  


  


to:

 
   
   
 

and it worked.

Andrew


On Wednesday, August 21, 2002, at 11:17  AM, Richards, Devin N (Devin) 
wrote:

> You have all of your validations in the XML?
> Have you tried adding the  to the 
> JSP page to see if the validation is working correctly? Once you have 
> this you can "view source" and see the validation code it generated. 
> This will show you if the validator plug-in is setup correctly and that 
> your XML is correct.
>
> BTW: we are most likely going to production on 1.1-b2
>
> Good luck.
>
> -Devin
>
> -Original Message-
> From: Andrew Shirk [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 12:13 PM
> To: Struts Users Mailing List
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Losing my sanity: 1.1b & Validator problems
>
>
> Devin, thanks for further the further explanation. I replied to your
> previous email earlier this morning, but it seems to have been lost in
> the ether. Anyway, I also tried including super.validate() in my form
> bean, which confirmed that Validation is in fact being done. The mystery
> is why validation is being performed but control is never returned to
> the JSP. It simply dies. No error. Nothing. I didn't change anything in
> the code when moving to 1.1b, so am beginning to wonder if this is a bug
> of some sort.
>
> I've spent way too many hours trying to track down the problem and may
> have to just go back to 1.1a if I can't find a solution today.
>
> Thanks again for the help.
>
> Andrew
>
> On Wednesday, August 21, 2002, at 10:16  AM, Richards, Devin N (Devin)
> wrote:
>
>> I had some validation that was done in the validation.xml
>> (required/minlenght etc) and then I wanted to do some business rule
>> validation that I could not do in the XML. When I put the code into my
>> form bean's validate() method, I got all of the business validations,
>> but none of my basic required/minlenght validations that were done in
>> the XML. Once I added a call to super.validate() it picked them up.
>>
>> Here is part of the struts-config.xml:
>>  >  path="/rmaFormSubmit"
>>  name="rmaForm"
>>  type="com.lucent.portal.rma.RmaFormAction"
>>  input="rmaFormDef"
>>  scope="request"
>>  parameter="submit"
>>  validate="true">
>>  
>>  
>>
>>  
>>  >  value="/WEB-INF/validator-rules.xml,
>>  /WEB-INF/validation.xml,
>>  /WEB-INF/classes/com/lucent/portal/rma/RmaValidation.xml" />
>>  
>>
>> The "rmaAckDef" as well as "rmaFormDef" are Tiles definations.
>>
>> Here is part of RmaValidation.xml:
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>
>> For these validations I use the  tag in the form JSP
>> to catch all normal validations before submit.
>>
>> Here is part of the RmaForm.java (extends ValidatorForm):
>>  public ActionErrors validate(ActionMapping mapping,
>> HttpServletRequest request)
>>  {
>>  //
>>  // Do validations from XML
>>  
>>  ActionErrors errors = super.validate(mapping, request);
>>
>>
>>  //
>>  // Extended validation checking
>>  
>>  if(this.isDoa())
>>  if(!checkDosOrderNumber())
>>  errors.add("dosOrderNumber", new
>> ActionError("rma.errors.form.dosOrderNumber"));  
>>
>>  return errors;
>>  }
>>
>> In order to get the validatios from RmaValidation.xml I had to put the
>> call to super.validate().
>>
>> HTH
>>
>> -Devin
>>
>> -Original Message-
>> From: Ralf Lorenz [mailto:[EMAIL PROTECTED]]
>> Sent: Wednesday, August 21, 2002 10:21 AM
>> To: Struts Users Mailing List
>> Subject: Re: Losing my sanity: 1.1b & Validator problems
>>
>>
>> Devin

Re: Losing my sanity: 1.1b & Validator problems (more info)

[Andrew Shirk]

Yes. I've checked repeatedly and all the validations are there. Again, 
the validations *are* being performed. In fact, if I print the number of 
errors, the plugin seems to be catching the errors properly. Even 
stranger, if I post the form w/o any errors (the form has been filled 
out correctly) validation passes and control is *successfully* forwarded 
to the confirmation page!! Still though, when there are errors, they're 
caught, but control never makes it back to the JSP. The process just 
dies. White. This leads me to the conclusion that there is either 
something wrong with the way I've configured the action, or this is a 
bug. Here's the action mapping again:

  


  

On a side note, I am using, and have configured in my xml file, custom 
validators to do two field comparisons, and to validate that a check box 
is checked. Again though, validation seems to be working so I don't 
think this is the problem. Here are the configurations anyway:


   
  
  
   
   
  
  



Does anyone know what else changed from 1.1a to 1.1b that could be 
creating this problem??

Thanks for all the suggestions,

Andrew


On Wednesday, August 21, 2002, at 11:17  AM, Richards, Devin N (Devin) 
wrote:

> You have all of your validations in the XML?
> Have you tried adding the  to the 
> JSP page to see if the validation is working correctly? Once you have 
> this you can "view source" and see the validation code it generated. 
> This will show you if the validator plug-in is setup correctly and that 
> your XML is correct.
>
> BTW: we are most likely going to production on 1.1-b2
>
> Good luck.
>
> -Devin
>
> -Original Message-
> From: Andrew Shirk [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 12:13 PM
> To: Struts Users Mailing List
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Losing my sanity: 1.1b & Validator problems
>
>
> Devin, thanks for further the further explanation. I replied to your
> previous email earlier this morning, but it seems to have been lost in
> the ether. Anyway, I also tried including super.validate() in my form
> bean, which confirmed that Validation is in fact being done. The mystery
> is why validation is being performed but control is never returned to
> the JSP. It simply dies. No error. Nothing. I didn't change anything in
> the code when moving to 1.1b, so am beginning to wonder if this is a bug
> of some sort.
>
> I've spent way too many hours trying to track down the problem and may
> have to just go back to 1.1a if I can't find a solution today.
>
> Thanks again for the help.
>
> Andrew
>
> On Wednesday, August 21, 2002, at 10:16  AM, Richards, Devin N (Devin)
> wrote:
>
>> I had some validation that was done in the validation.xml
>> (required/minlenght etc) and then I wanted to do some business rule
>> validation that I could not do in the XML. When I put the code into my
>> form bean's validate() method, I got all of the business validations,
>> but none of my basic required/minlenght validations that were done in
>> the XML. Once I added a call to super.validate() it picked them up.
>>
>> Here is part of the struts-config.xml:
>>  >  path="/rmaFormSubmit"
>>  name="rmaForm"
>>  type="com.lucent.portal.rma.RmaFormAction"
>>  input="rmaFormDef"
>>  scope="request"
>>  parameter="submit"
>>  validate="true">
>>  
>>  
>>
>>  
>>  >  value="/WEB-INF/validator-rules.xml,
>>  /WEB-INF/validation.xml,
>>  /WEB-INF/classes/com/lucent/portal/rma/RmaValidation.xml" />
>>  
>>
>> The "rmaAckDef" as well as "rmaFormDef" are Tiles definations.
>>
>> Here is part of RmaValidation.xml:
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>
>> For these validations I use the  tag in the form JSP
>> to catch all normal validations before submit.
>>
>> Here is part of the RmaForm.java (extends ValidatorForm):
>>  public ActionErrors validate(ActionMapping mapping,
>> HttpServletRequest request)
>>  {

Re: Losing my sanity: 1.1b & Validator problems

[Andrew Shirk]

Devin, thanks for further the further explanation. I replied to your 
previous email earlier this morning, but it seems to have been lost in 
the ether. Anyway, I also tried including super.validate() in my form 
bean, which confirmed that Validation is in fact being done. The mystery 
is why validation is being performed but control is never returned to 
the JSP. It simply dies. No error. Nothing. I didn't change anything in 
the code when moving to 1.1b, so am beginning to wonder if this is a bug 
of some sort.

I've spent way too many hours trying to track down the problem and may 
have to just go back to 1.1a if I can't find a solution today.

Thanks again for the help.

Andrew

On Wednesday, August 21, 2002, at 10:16  AM, Richards, Devin N (Devin) 
wrote:

> I had some validation that was done in the validation.xml 
> (required/minlenght etc) and then I wanted to do some business rule 
> validation that I could not do in the XML. When I put the code into my 
> form bean's validate() method, I got all of the business validations, 
> but none of my basic required/minlenght validations that were done in 
> the XML. Once I added a call to super.validate() it picked them up.
>
> Here is part of the struts-config.xml:
>  path="/rmaFormSubmit"
>   name="rmaForm"
>   type="com.lucent.portal.rma.RmaFormAction"
>   input="rmaFormDef"
>   scope="request"
>   parameter="submit"
>   validate="true">
>   
>   
>
>   
>  value="/WEB-INF/validator-rules.xml,
>   /WEB-INF/validation.xml,
>   /WEB-INF/classes/com/lucent/portal/rma/RmaValidation.xml" />
>   
>
> The "rmaAckDef" as well as "rmaFormDef" are Tiles definations.
>
> Here is part of RmaValidation.xml:
>   
>   
>   
>   
>   
>   
>   
>   
>   
>   
>
> For these validations I use the  tag in the form JSP 
> to catch all normal validations before submit.
>
> Here is part of the RmaForm.java (extends ValidatorForm):
>   public ActionErrors validate(ActionMapping mapping, 
> HttpServletRequest request)
>   {
>   //
>   // Do validations from XML
>   
>   ActionErrors errors = super.validate(mapping, request);
>
>
>   //
>   // Extended validation checking
>   
>   if(this.isDoa())
>   if(!checkDosOrderNumber())
>   errors.add("dosOrderNumber", new 
> ActionError("rma.errors.form.dosOrderNumber"));   
>
>   return errors;
>   }
>
> In order to get the validatios from RmaValidation.xml I had to put the 
> call to super.validate().
>
> HTH
>
> -Devin
>
> -Original Message-
> From: Ralf Lorenz [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 21, 2002 10:21 AM
> To: Struts Users Mailing List
> Subject: Re: Losing my sanity: 1.1b & Validator problems
>
>
> Devin,
> can you please explain that a little further? The problem that Andrew
> describes sounds familiar to me.
> I started using struts1.1b with validator and everything worked fine, 
> just
> using a DynaValidatorForm.
> But then when I introduced Tiles to my application the validation didn't
> take place. Although the
> ValidatorPlugIn was loaded and there was no Exception ( looking into the
> logs). It's just that
> it don't happen.
> I don't know what you mean by putting a super.validate() as the first 
> line
> ... because I just use
> given validation-rules (required, minlength ...) and some
> DynaValidatorForms.
> Any help on that ;-?
> Ralf
>
> - Original Message -
> From: "Richards, Devin N (Devin)" <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> Sent: Wednesday, August 21, 2002 3:19 PM
> Subject: RE: Losing my sanity: 1.1b & Validator problems
>
>
>> I noticed that when I went to 1.1b2 I had to insert a call to
> super.validate() as the first line in my validate() code to pick up all 
> of
> the validations I set in my validation.xml file.
>>
>> -Devin
>>
>>
>>
>> -Original Message-
>> From: An

Losing my sanity: 1.1b & Validator problems

[Andrew Shirk]

I upgraded to Struts 1.1b last week (and to Tomcat 4.1.9 - which is 
great great stuff) and everything seemed to go fine. However, today, I 
was demonstrating my app to a friend when I noticed Validator 
validations were not being performed. I checked the logs and the 
validation configuration files are being loaded just fine, but still no 
validation errors were being caught. I also noticed in the archives 
mention of a change in the way the plugin is configured in struts-
config.xml. I made the change in my struts-config.xml thinking that must 
have been the problem, but alas, things got worse! Now, when the 
ValidatorForm is posted to the server, nothing happens at all! After 
about 10 seconds of processing, the browser seems to receive an empty 
response. A blank document is all that's received. I checked the logs, 
and no exceptions are being thrown. I have checked everything I can 
think of 4 or 5 times, and don't know what else to do. This worked 
perfectly in 1.1a.

Please help if you have any ideas.

Thanks very much,

Andrew

registrationForm extends ValidatorForm

 
   
   
 


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

bug? Re: Dynamic Message Keys

[Andrew Shirk]

I came up with a straightforward solution that uses the  
tag rather than . It seems  doesn't allow 
the body to be specified, which I couldn't find in the documentation. I 
had tried line 2 exactly last week using nested:define but it kept 
failing, which is why i resorted to the scriptlet.


type.description.<%=type%>


On Friday, June 7, 2002, at 03:59  PM, Andrew Shirk wrote:

> I need to construct a message key dynamically, and am looking for a 
> solution that does not use scriptlets. Can anyone suggest an 
> alternative to the code below, which works but is ugly.
>
> 
> <% String key = "type.description." + type; %>
> 
>
> Thanks very much,
>
> Andrew
>
>
> --
> To unsubscribe, e-mail:   <mailto:struts-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:struts-user-
> [EMAIL PROTECTED]>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Dynamic Message Keys

[Andrew Shirk]

I need to construct a message key dynamically, and am looking for a 
solution that does not use scriptlets. Can anyone suggest an alternative 
to the code below, which works but is ugly.


<% String key = "type.description." + type; %>


Thanks very much,

Andrew


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Dynamically constructing a resource key

[Andrew Shirk]

I'm new to Struts and have been using the archives for the last few 
weeks. However, now I need some feedback.

Is there a prettier or more appropriate way of constructing or 
concatenating a string using Struts in an effort to use the constructed 
string as some key? I could only get this ugly approach to work.


<% String key = "type.description." + type; %>


Thanks very much,

Andrew


--
To unsubscribe, e-mail:   
For additional commands, e-mail: