From: Farrukh N. <fa...@we...> - 2009-02-27 19:16:05
|
Hi Brian, I do not have experience running on JDK 6. JDK 1.6 bundles newer JAXB, SAAJ and JAX-WS than Omar 3.1 uses. The ideal fix to this requires migrating Omar to JAX 2 stack from Sun. This sort of enhancement requires significant time and effort. If any folks are willing to commit to helping do this then please let me know and I can add you as dev team members and then we can discuss how to go about it. Until that happens the project is going to be difficult to improve in major ways with its limited dev team. It may be possible to use Java endorsed mechanism to get things to work without the migration to recent JAX stack but I have no experience or confidence in that path. Thanks. McIlwrath, BK (Brian) wrote: > Apologies if this has come up before but.... > > I can compile an omar.war under JDK1.6 and it *almost* works when Tomcat > is also running 1.6! > > Certain operations fail with the SAAJ error similar to that described at > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6463868 > (where a workaround URL is no longer accessible!) > > As it seems so close to working 100% I wonder if anyone had/could point > me towards the solution! I could spend some time trying to fix it myself > (if not already done!) with some pointers as to the likely problem. > > Regards, > > Brian McIlwrath > STFC, UK > -- Regards, Farrukh Web: http://www.wellfleetsoftware.com |