Code Warfare and Seam

pinned down after a short skirmish the previous day
it was too quiet, spirits were dampened
earlier morning brought some hope, help would be coming
which eroded throughout the day, it was not enough
deep in the trenches, we waited still, scounts had not returned
our only option was to retreat and go around
all were hesitant, so i made the move...

summary: i hate jboss seam
or rather we all do at this point

for the past 2 days, we (the entire team including even other teams) have been researching seam issues.
including class conflict issues, instances not matching expected classes, not being able to cast, for seam core classes.
the errors had been occurring for the past few months but not caused any observable issues... until now.
and were threatening to hold up deadlines.

today we found what appears to be the cause: having two seam ears in one jboss 4 server
this apparently causes the apps to randomly step on each other,
including loading/creating core seam components from wrong classloader, from other ear.

eventually, i gave up on trying to find out why, as we all slowly did.
it didn't make any sense, all ear isolation settings had been set and no obvious causes.
many fixes/attempts were made, many possible solutions, but none had any effect.

in the end, i went forward with removing seam from one of them.
since it had been added recently for one and thankfully used very little.
so it was a viable option, and better than setting up a new jboss to run each ear in its own.

... and so the battle was won,
but the war will continue
(haha war, get it? ear-war, ok, over and out).