Although it may be an unrelated issue, there is a known problem with OC4J's xml parser that shows up when two consecutive pages both contain components with the same name. The error shows up as some sort of non-unique element id exception (cant remember the exact Exception off the top of my head).
I use OC4J and have had to enforce a naming convention where I prefix every component in a page file with the page name. Its a problem in OC4J 9.0.4 and earlier. Its apparently fixed in 10.1.2, although Ive not had the oppertunity to test it. On 06/04/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > Could you give the full stack trace of your exception? > > On 4/5/06, yesidredondo <[EMAIL PROTECTED]> wrote: > > > > Hi, i need some help with tapestry, i 've made a big application with > > tapestry and it works fine in jboss, but when i place it in the oc4j > > server, > > it have an strange mistake: > > > > Whenever i go to a page for first time it throws a RuntimeException > "Could > > not parse specification context:/WEB-INF/myPage.page" but if i try to go > > to > > that page again, it works!.. and it works forever!. I do not know why is > > this happening. > > > > I am installing this application in a big enterprise and need a quick > > solution, Thanks. > > > > Hermann Yesid Redondo Eslava > > IT-GROUP > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://opennotion.com > >
