RE: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-12-05 Thread Jakob Roesgaard Færch
I have begun work to make the Adventure Buolder sample app run. The first step I'm trying to accomplish is to get as far as the community has gotten - i.e. to reach the situation described by Saraswathi in message http://www.mail-archive.com/dev@geronimo.apache.org/msg12717.html I have checked

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-12-05 Thread Jacek Laskowski
Jakob Roesgaard Færch wrote: I have begun work to make the Adventure Buolder sample app run. Hi Jakob, Excellent! The team of people who are looking into deploying AB consists of 3 members - you, Saraswathi and me. Is there anybody else? ;) It would be much appreciated if AB could be

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-12-05 Thread Jakob Roesgaard Færch
Jacek Laskowski wrote: Jakob Roesgaard Færch wrote: I have checked out the Geronimo sources and built the server. Using the code in sandbox/adventurebuilder merged with the AB 1.0.1 application from Sun as described on the Wiki page http://wiki.apache.org/geronimo/AdventureBuilder, I

RE: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-23 Thread Selvaraj, Saraswathi \(Cognizant\)
Hi, The url issue has been resolved and the purchase order checkout is working fine. But when invoking OrderTracking its giving the exception message: faultString: Web Service EJB Invocation failed: method public abstract com.sun.j2ee.blueprints.opc.otwebservice.OrderDetails

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-20 Thread Jacek Laskowski
Selvaraj, Saraswathi (Cognizant) wrote: Hi, We have deployed the adventure builder in geronimo. But the issue that we are getting is “CheckoutHTMLAction Exception: (404) Not Found” - Error. The Stack trace is (404)Not Found at

RE: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-18 Thread Selvaraj, Saraswathi \(Cognizant\)
Hi, We have deployed the adventure builder in geronimo. But the issue that we are getting is CheckoutHTMLAction Exception: (404) Not Found - Error. The Stack trace is (404)Not Found at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744) at

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-16 Thread Preben Thorø
Hi I vaguely recall a similar problem trying to port AB to JBoss - I will try to dig into it. Meanwhile, I hope our AB porting to the Trifork server can give you a few hints about where to go. I have attached our deployment plans (ie. server specific deployment desc.) to this mail - they

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-16 Thread Jacek Laskowski
Preben Thorø wrote: Meanwhile, I hope our AB porting to the Trifork server can give you a few hints about where to go. I have attached our deployment plans (ie. server specific deployment desc.) to this mail I couldn't expect a better response! Thanks for the deployment descriptors.

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-15 Thread David Blevins
On Nov 15, 2005, at 3:15 PM, Jacek Laskowski wrote: Hi, Just a quick update on the work around the Java Adventure Builder Reference 1.0.1 application. I've just committed the first configuration files of the application. Although I don't think the web services references configuration

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-15 Thread Arun Venugopal
Hi Jacek, We tried to see if we can get Adventure builder to work on geronimo. We managed to get all the modules (ears) deployed. Currently we are dealing with an Axis fault (seems to be some sort of a url not found issue, we are yet to dig deep into it). We had an issue with unknown primary

Re: Java Adventure Builder Reference 1.0.1 webapp deployed

2005-11-15 Thread Jacek Laskowski
Arun Venugopal wrote: Hi Jacek, We tried to see if we can get Adventure builder to work on geronimo. We managed to get all the modules (ears) deployed. Currently we are dealing with an Axis fault (seems to be some sort of a url not found issue, we are yet to dig deep into it). We had an