Sorry guys, I think I've found the real problem. When I was debugging, the exception was being thrown, but as I was running the app as a servlet, the tomcat was involking the doGet() method and inside it the exception was being thrown, however the ide couldn't trace the code inside the Tomcat. The Tomcat was printing the exception on the html it generates. Sorry, it was my mistake :S, I'm still learning how to deal with servlets.
I think the JIRA is no more useful, how can I close it? Adriano Crestani On 12/8/06, Luciano Resende <[EMAIL PROTECTED]> wrote:
Thanks Adriano, I updated the JIRA with the affected version... but at the moment you are not going to be able to set it to your name..... When you have the fix, you are going to generate a svn diff > tuscany985.patch and then attach the result file to the JIRA, and a commiter is going to review and apply the fix. -- Luciano Resende http://people.apache.org/~lresende On 12/7/06, Adriano Crestani <[EMAIL PROTECTED]> wrote: > > I created the JIRA and defined it as a bug: > http://issues.apache.org/jira/browse/TUSCANY-985 > > As this is my first time creating a JIRA I'm not sure if everything is ok. > Can anybody check it? > > I have one question, how can I edit a JIRA? Because I'm wanting to set me > as > the assignee. > > Adriano Crestani > > On 12/7/06, Adriano Crestani <[EMAIL PROTECTED]> wrote: > > > > Yes, I'm interested ; )...I will see how to create a Jira and any doubt > (I > > think there will be many) I will post it here, ok?! > > > > Adriano Crestani > > > > On 12/7/06, Luciano Resende <[EMAIL PROTECTED]> wrote: > > > > > > Hi Adriano > > > > > > I had an offline chat with Brent, and we agreedn that this looks > like > > > a > > > simple case where would be a great oportunity for you to create a JIRA > > > and > > > try to submit a patch for it if you are interested... please let us > know > > > if > > > this is ok, and if you need any guidance on any steps... > > > > > > -- > > > Luciano Resende > > > http://people.apache.org/~lresende > > > <http://people.apache.org/%7Elresende> > > > > > > On 12/7/06, Brent Daniel < [EMAIL PROTECTED]> wrote: > > > > > > > > Hi Adriano, > > > > > > > > Thanks for reporting this. I'm surprised it's not throwing an > > > > exception -- I'll look into it. > > > > > > > > Brent > > > > > > > > > > > > On 12/6/06, Adriano Crestani <[EMAIL PROTECTED]> wrote: > > > > > I was executing a query using a stored procedure that was defined > in > > > a > > > > .xml > > > > > file. The procedure was a simple select: <Command name="all cart > > > items" > > > > > SQL="SELECT * from CART_ITEM WHERE CART_ID = ?" kind="Select"/> > > > where I > > > > just > > > > > need to set one parameter. But I mistakenly set 2 parameters. Then > I > > > ran > > > > the > > > > > application, there was no exception, but it didn't worked as > > > expected. > > > > So I > > > > > debugged the code and I found what was happening. The DAS tried to > > > > execute > > > > > the query, but as there was more parameters than expected it threw > > > an > > > > > exception inside the method > > > > > org.apache.tuscany.das.rdb.impl.ReadCommandImpl.executeQuery(). I > > > don't > > > > know > > > > > if the jdbc generated this exception or whatever, but the point is > > > that > > > > a > > > > > problem occurs and no exception was reported and I couldn't know > > > what > > > > was > > > > > happening. I suggest that if an exception be thrown it should be > > > > reported to > > > > > the user, in the SDO/DAS case, the coder, in other words, at least > > > an > > > > > Exception.printStackTrace() should be called. Anyway, this is only > > > my > > > > > suggestion ; ) > > > > > > > > > > Adriano Crestani > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > >
