It would be almost impossible for someone on this list to give you an answer to that question. It is very unlikely that it actually has anything to do with Wicket. I'd start by watching your actual IP traffic between the webapp and the web service to see if the requests are exactly the same / look at the results / etc.
-- Jeremy Thomerson http://www.wickettraining.com On Mon, Apr 26, 2010 at 8:13 AM, Omar Laurino <[email protected]> wrote: > Hi, > > I am experiencing a quite weird problem with wicket. > > Notice that I'm working to a project which counts several thousands of > lines > of code, so unless I understand where should I look for the problem, I > can't > post any relevant code. However, I am pretty confident the problem is > somehow wicket related, as I will show you. > > I've got some low level packages which implement the business logic my web > application exposes to the user. The basic operation is to consume SOAP > webservices and store results into a DB. > > I tested my low level classes and they work fine, but if I call these > classes' methods through the wicket web application I get far less results > (200 or 1000 out of almost 7000). > > In order to debug the application I wrote down a simple test method, listed > below. > > If I run a test program invoking the method by itself, I get the full 7k > resultset, while if i call the very same method from inside the wicket > webapp, I get just 200 (or 1000) items. > > I really can't understand what is going wrong, so any help in any direction > is greatly appreciated. Thank you. > > Here is the test method: > > ---------- > RegistrySnapshotManager snapshotManager = new > RegistrySnapshotManager(); > > RegistryInquiryJpaController inquiryController = new > RegistryInquiryJpaController(); > > RegistryInquiry inquiry = > inquiryController.findRegistryInquiry(130); > > RegistrySnapshot snapshot = snapshotManager.newSnapshot(inquiry, > Capability.CONE.getAdql() > +" or "+ > Capability.SIA.getAdql() > +" or "+ > Capability.SSA.getAdql()); > > System.out.println(snapshot.getSxapResourceList().size()); > ----------- > > The SOAP webservice operation call is nested inside my classes and third > party classes too. > However, here are some relevant method calls from these classes: > > The above snapshotManager.newSnapshot(inquiry, sql) method invokes a third > party method which hides the SOAP request. > > The third party package has been tested by several people throughout the > world. >
