...
[15:52:31 CDT(-0500)] <EricDalquist> and is it something we need to fix in the uPortal distribution?
[15:54:32 CDT(-0500)] <mmoayyed> it was the xml-api file I had left in my endorsed directory for tomcat, when I was going through a shib idp install. it's not related to the dist process at all.
[15:54:38 CDT(-0500)] <EricDalquist> ah
[15:54:41 CDT(-0500)] <EricDalquist> ok good to know
[15:54:55 CDT(-0500)] <mmoayyed> thanks for the tip! very useful
[15:54:58 CDT(-0500)] <EricDalquist> that endorsed lib is a dangerous thing 
[15:55:00 CDT(-0500)] <EricDalquist> no problem
[15:55:07 CDT(-0500)] <EricDalquist> verbose:class is kinda neat
[15:55:13 CDT(-0500)] <EricDalquist> just a lot of data to sift through
[15:56:07 CDT(-0500)] <mmoayyed> yeah, spits out a ton. I somewhat wish that the exception had that info in a way, not sure how but certainly it would have saved me an hour or so, looking through the config
[16:33:29 CDT(-0500)] <mmoayyed> Question: what's the best way to resolve dup key constraints during the data import process?
[16:33:43 CDT(-0500)] <EricDalquist> depends on the data item that is failing
[16:35:15 CDT(-0500)] <mmoayyed> This is what I presently get: ERROR: duplicate key value violates unique constraint "up_layout_struct_pkey"
[16:35:15 CDT(-0500)] <mmoayyed> [java] Detail: Key (layout_id, user_id, struct_id)=(1, 14, 12) already exists.
[16:35:33 CDT(-0500)] <mmoayyed> trying to import the staff-lo fragment layout file
[16:35:49 CDT(-0500)] <EricDalquist> does the layout file have multiple nodes with the same ID attribute?
[16:36:52 CDT(-0500)] <mmoayyed> nope. all ID attributes are different