AW: Old torque bugs from scarab
I think it is better to have just one jira Key for Torque. It isn't so confusing. It is easier to get an overview. And it isn't understandable why there is an OLD key, just because the bugs in it are imported from Scarab. -Ursprüngliche Nachricht- Von: Thomas Fischer [mailto:[EMAIL PROTECTED] Gesendet: Samstag, 30. September 2006 09:20 An: torque-dev@db.apache.org Betreff: Old torque bugs from scarab Jeff turner has imported the old bugs from Scarab into jira, they can be found in http://issues.apache.org/jira/browse/TORQUEOLD The question si now whether they should be left under a separate key, or whether the issues should be bulk moved to the current Torque project. I have started to look through the open issues (beware: you cannot use the standard outstanding filter, as the resolution is set to unresolved for all issues which were not changed in the meantime), and resolved those which are fixed, and set those to wontfix which make suggestions which do not fit into current Torque architecture. If you do not agree with a change I have made, please complain. Note:currently no change mails are sent to the torque mailing lists, so whenever you want to discuss something, also mail to torque-dev to direct people to the spot. Note2: Many things (e.g. comments, attachments) were lost in the export/import process, becaause the old version of scarab we were using left out many fields on the TSV export. My personal impression is that many things are still relevant to Torque, but most are things which should be hcanged and not many explicit bugs. So I'm still divided whether we should keep the old issues separate or not. Any opinions ? Thomas P.S. I'm away on vacation next week. I'lll look though the remaining issues when I'm back. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Torque Issue
Hi, I am using torque with weblogic 8.1 and running into a runtime issue with some of the torque classes. The code complies clean but for when I execute the code I get the following issue. Let me know if you need more details Below is the exception Oct 6, 2006 9:15:52 AM PDT Error HTTP BEA-101020 [ServletContext(id=801 860,name=private-banking,context-path=/private-banking)] Servlet failed with Exc eption java.util.NoSuchElementException at java.util.Vector.firstElement(Vector.java:446) at com.wellsfargo.pcsweb.om.GeographicEntity.getParent(GeographicEntity. java:210) at com.wellsfargo.pcsweb.om.Pbuser.getCompanyIdAsString(Pbuser.java:376) at com.wellsfargo.pcsweb.controller.EditShawAdvanceTransactionAction.per form(EditShawAdvanceTransactionAction.java:94) at org.apache.struts.action.ActionServlet.processActionPerform(ActionSer vlet.java:1787) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:158 6) at com.wellsfargo.pcsweb.servlet.SecureActionServlet.process(SecureActio nServlet.java:86) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run (ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm pl.java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm pl.java:348) at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispat cherImpl.java:322) at org.apache.struts.action.ActionServlet.processActionForward(ActionSer vlet.java:1759) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:159 6) at com.wellsfargo.pcsweb.servlet.SecureActionServlet.process(SecureActio nServlet.java:86) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:492) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run (ServletStubImpl.java:1072) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm pl.java:465) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm pl.java:348) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio n.run(WebAppServletContext.java:6981) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate dSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java: 121) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe rvletContext.java:3892) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm pl.java:2766) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) Thanks, Aditi Ambashta.
