Marvin,

Thanks for point out that those directions are incorrect.  We've been
maintaining a sample configuration file in CVS throughout the project
lifetime that has apparently not been synced with the documentation
available on the web site.  If you would be willing to place your
instructions in our wiki, that would be great.

The CAS project has reached a point where I think we need to start looking
for volunteers to take over some documentation responsibilities from me as
I'm obviously falling behind.  I'll be posting about that in a separate
email though.

As for your suggestion about commenting the constructor-args. Its a good
suggestion though its also just one more opportunity for things to be out of
sync ;-).  I'd like to investigate an alternative that I've seen of using
meta data to give the parameters names such that they can be referenced.  It
would be self documenting and it would need to be maintained for the code to
actually work.  I've seen some people talking about it so I'm hoping someone
has started to implement it.

Thanks
-Scott

On 7/25/07, Marvin Addison <[EMAIL PROTECTED]> wrote:
>
> I wrote up some instructions based on
> http://www.ja-sig.org/products/cas/client/client-java/index.html.  A
> developer on another team just tried following them today, and ran into
> problems.  I took the Spring XML from that page verbatim, and our
> experience today suggests it is broken in at least a couple of ways:
>
> 1) The beans namespace declarations didn't work for us
> 2) There is no constructor for Cas20ProxyTicketValidator that takes 6
> arguments in the 3.0.0 client download.
>
> Studying the source and trial and error allowed us to correct what
> appeared to be wrong, and we got a working configuration.  I'm curious,
> however, about the instructions I started from.  Has
> [EMAIL PROTECTED] followed those instructions with success?  Are
> there other instructions that are more current?  If not, I'd be happy to
> document what worked for us if someone could point to a spot.
>
> Tangentially, reading the Spring XML in those instructions reminded me
> of other Spring XML configuration files I've studied in the CAS
> distribution.  I have a general recommendation:  for beans that have
> multiple argument constructors, provide comments above each one with at
> least the data type and name of the argument.  I've had to correlate
> with source on more than one occasion trying to figure out which
> constructor argument went to what property, and such comments would have
> saved me the trouble 9 out of 10 times.
>
> Regards,
> Marvin Addison
> Application Developer
> Middleware Services
> Virginia Tech
> _______________________________________________
> Yale CAS mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas
>



-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to