...
[15:02:38 CDT(-0500)] <kickehy> oh...this is for setting up the jpaticketregistry
[15:02:42 CDT(-0500)] <foxnesn> it should include directions for setting up the ticket reg if it is required for service management
[15:03:20 CDT(-0500)] <foxnesn> The prefix "tx" for element "tx:annotation-driven" is not bound.
[15:03:22 CDT(-0500)] <foxnesn> that's my error
[15:04:42 CDT(-0500)] <foxnesn> looks like i have to setup jpa lol
[15:04:50 CDT(-0500)] <kickehy> heh
[15:04:58 CDT(-0500)] <kickehy> i wish i could be more clear for you
[15:05:08 CDT(-0500)] <kickehy> i don't 100% fully understand it all
[15:05:17 CDT(-0500)] <foxnesn> im assuming "is not bound" means it doesnt know what "transationManager" is pointing to since it is not created
[15:05:42 CDT(-0500)] <foxnesn> it's fine, it is a learning experience
[15:05:49 CDT(-0500)] <kickehy> agreed
[15:05:54 CDT(-0500)] <foxnesn> documenting this is going to a freaking manual
[15:05:58 CDT(-0500)] <kickehy> it made sense the other day 
[15:07:23 CDT(-0500)] <kickehy> yeah...i only just started my documenation on it
[15:07:34 CDT(-0500)] <kickehy> i've been sidetracked with this wireless project
[15:08:00 CDT(-0500)] <kickehy> but i guess based on my priority of projects....CAS has sidetracked my wireless project
[15:08:18 CDT(-0500)] <foxnesn> really? who decided the priority
[15:08:26 CDT(-0500)] <kickehy> my boss
[15:08:30 CDT(-0500)] <foxnesn> ah
[15:08:37 CDT(-0500)] <foxnesn> you showed him your progress
[15:08:43 CDT(-0500)] <foxnesn> and i bet he got all excited
[15:09:12 CDT(-0500)] <kickehy> well...he's not a huge fan of SSO
[15:09:18 CDT(-0500)] <foxnesn> why not?
[15:09:45 CDT(-0500)] <kickehy> plus...the only reason we started this project is because that's how orgsync said to do it
[15:09:54 CDT(-0500)] <kickehy> foxnesn: not too sure
[15:10:15 CDT(-0500)] <kickehy> old school maybe?
[15:11:07 CDT(-0500)] <foxnesn> ahh
[15:15:41 CDT(-0500)] <kickehy> i can see it being very useful for non-critical applications, and by non critical i mean our Admin system
[15:15:50 CDT(-0500)] <kickehy> wait
[15:16:00 CDT(-0500)] <kickehy> take that second non out of there
[15:16:11 CDT(-0500)] <kickehy> admin system would be considered critical
[15:16:12 CDT(-0500)] <foxnesn> hehe
[15:16:12 CDT(-0500)] <kickehy> hehe
[15:16:35 CDT(-0500)] <kickehy> plus the password policy they have on the admin system is insane
[15:16:50 CDT(-0500)] <foxnesn> at least 64 characters
[15:16:51 CDT(-0500)] <foxnesn> lol
[15:17:06 CDT(-0500)] <kickehy> it's more of the fact your password expires every 3 months
[15:17:15 CDT(-0500)] <kickehy> and it remembers the last 5 passwords you entered
[15:17:24 CDT(-0500)] <foxnesn> what wow
[15:17:28 CDT(-0500)] <kickehy> i don't even try logging in anymore
[15:17:35 CDT(-0500)] <kickehy> i just hit the password reset button
[15:17:39 CDT(-0500)] <foxnesn> haha
[15:18:51 CDT(-0500)] <foxnesn> what day were you working with atilling on this?
[15:18:58 CDT(-0500)] <foxnesn> i can check it in the irc log
[15:19:22 CDT(-0500)] <kickehy> ummm i think thursday or friday
[15:19:32 CDT(-0500)] <foxnesn> ok
[15:19:47 CDT(-0500)] <foxnesn> im wrapping up here and dont want to get more into this hah
[15:20:02 CDT(-0500)] <kickehy> haha
[15:20:51 CDT(-0500)] <foxnesn> so he told you NOT to include the transation manager in your deployer BUT to include it in the ticketregistry?
[15:21:52 CDT(-0500)] <kickehy> well he didn't say that, that's just what the wiki did
[15:22:17 CDT(-0500)] <foxnesn> so you have them in both?
[15:22:30 CDT(-0500)] <foxnesn> cause the service manager wiki has it and so does the ticket reg
[15:22:43 CDT(-0500)] <foxnesn> in fact having both as is would include a ton of redundant info
[15:23:05 CDT(-0500)] <kickehy> the two wiki articles kind of overlap
[15:23:40 CDT(-0500)] <foxnesn> i wonder if including it in both would make duplicate entries in the db somehow
[15:23:48 CDT(-0500)] <kickehy> the services registry one has the transaction manager/ticket registry setup a different way than the jpaticketregistry wiki says
[15:23:58 CDT(-0500)] <kickehy> and!
[15:24:10 CDT(-0500)] <kickehy> it'll probably error on you anyways
[15:24:20 CDT(-0500)] <kickehy> because you'll have two beans that are trying to do the same thing
[15:24:26 CDT(-0500)] <foxnesn> right
[15:24:43 CDT(-0500)] <kickehy> since those individual xml files get made into one big one at runtime
[15:24:46 CDT(-0500)] <foxnesn> no wonder institutions just pay these guys to do it haha
[15:25:55 CDT(-0500)] <kickehy> since i already had the transaction manager setup inside the ticketregistry.xml...i didn't need to add it to the deployerconfig like the services registry wiki states
[15:26:06 CDT(-0500)] <foxnesn> i see
[15:26:19 CDT(-0500)] <kickehy> and in fact i do recall asking that question to atilling
[15:30:38 CDT(-0500)] <kickehy> at least you're not documenting switch ports
[15:30:55 CDT(-0500)] <kickehy> and putting descriptions on them all
[22:53:26 CDT(-0500)] <foxnesn1> im trying to setup pooling and i keep meeting the error:
[22:53:53 CDT(-0500)] <foxnesn1> Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'poolingContextSource' defined in ServletContext resource [/WEB-INF/deployerConfigContext.xml]: Instantiation of bean failed; nested exception is java.lang.NoClassDefFoundError: org/apache/commons/pool/KeyedObjectPool
[22:54:16 CDT(-0500)] <foxnesn1> i setup pooledcontextsource just like the wiki describes
[22:54:23 CDT(-0500)] <foxnesn1> and put the pooled properties in cas.properties
[22:55:01 CDT(-0500)] <foxnesn1> if i remove pooledcontextsource bean and its reference in the ldapbind then it runs fine
[22:55:05 CDT(-0500)] <foxnesn1> something about that line...
[22:57:49 CDT(-0500)] <foxnesn1> looks like i need a jar for pooling but the wiki has no mention of it
[23:08:24 CDT(-0500)] <foxnesn1> ah, i had to add commons-pool-1.5.2.jar to tomcat lib to get pooling to work