Hi Chris, excellent! It would be great if we could work together on this. I'm sure if JBoss already provides the basic functionality through Axis etc then it should be easy enough to just wrap that behind the 1.4 spec. Wonderful if we could provide the xdoclet tags for it too. I'll take a look at JBoss.net and maybe we can come up with a plan. Brian
----- Original Message ----- From: "Jung , Dr. Christoph" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "James Cooley" <[EMAIL PROTECTED]>; "Herve Tchepannou" <[EMAIL PROTECTED]> Cc: "xdoclet" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, January 30, 2003 1:41 PM Subject: [Xdoclet-user] AW: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (ba nk ws) > The integration code that puts Axis as a web service deployer into jboss is > called jboss.net > > Currently it uses a proprietary deployment model (web service archive - ..wsr > - containing serialisation code and > the native Axis wsdd deployment descriptors as meta-data) that is however > quite along the lines of > rest-J2EE. We have a special xdoclet module for generating wsdd from > annotated EJB´s and POJO´s. > > It is planned to support the J2EE1.4 deployment model until June, I cannot > give you any guarantuee > on earlier deadlines (since as it looks, I will be the one to implement it > and my schedule is quite full). I would be happy to contribute to any 1.4 > web service xdoclet module on that way. > > I would also be happy if we could work together on that issue, since you > seem to have the Weblogic experience as well and we would like to be at > least as good ;-) > > Maybe you could already have a look at what is already in jboss.net and > maybe start with our proprietary xdoclet/deployment model. Deriving a 1.4 > web service annotation and migrating the xpetstore may result in a very > simple task, then? > > CGJ > > -----Ursprüngliche Nachricht----- > Von: Brian McSweeney [mailto:[EMAIL PROTECTED]] > Gesendet: Donnerstag, 30. Januar 2003 13:56 > An: James Cooley; Herve Tchepannou > Cc: xdoclet; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Betreff: [JBoss-user] Re: FW: New file structure for xpetstore-3.0 (bank ws) > > > Hi all, > I'm sending this mail to both the jboss-user and xdoclet users lists because > although it's with regard to the xpetstore application some questions are > based on xdoclet and some on JBoss. > > Ok, for the next version of xpetstore we're looking at giving an example > implementation of a web service. The web service example that Herve has > suggested is one to process credit card information. This will be called > internally within the xpetstore application. > > The whole idea of xpetstore is to show how to write container independent > apps with xdoclet. It currently supports weblogic and jboss, so while it was > suggested that we could write the web service with JBoss' web service (is > this called > JBoss.net?) it > would be really good if we could write it based on J2EE 1.4 and thus try to > make it container independent. I know that JBoss 4 will be complient with > the J2EE 1.4 spec. and this is meant to be released by June, but are there > going to be earlier beta versions that will support this functionality so we > can test against it? If so is a time estimate possible? > > Which leads me to the xdoclet part of the question. We're promoting xdoclet > so does it plan to add this 1.4 functionality? If so, at what stage? > > anyway, thanks very much for your time and any replies. Our previous > discussion on this is attached below. Brian > > PS - As an aside is this how online sites actually do process credit card > info? I'm not so sure. Are they moving towards processing via web services? > Most people who run online sites I know, store the data and batch process > the info via a standard visa machine etc. If however the credit card > companies are moving towards web services then I think it's a wonderful > idea. Anyone know about this? > > ----- Original Message ----- > From: "James Cooley" <[EMAIL PROTECTED]> > To: "Brian McSweeney" <[EMAIL PROTECTED]> > Cc: "Herve Tchepannou" <[EMAIL PROTECTED]> > Sent: Thursday, January 30, 2003 11:52 AM > Subject: Re: FW: New file structure for xpetstore-3.0 (bank ws) > > > > I think we're reaching a point were it might be better to have these > > discussions on the dev list - there are probably some lurkers with > > experience of this out there. > > > > > > Brian McSweeney wrote: > > > > > I like the structure beneath. It's clear. > > > > > > I have two questions about the bank web service idea. > > > > Just on the bank ws - would it not be easier to do a WS to the > > petstore before getting started on the bank? The petstore has a much > > richer interface than a cc processing app. > > > > > > > > Q1: Is there no way to make the session facade itself a web service? > > > Does it have to be via a servlet? If we are going to write the bank > > > app as an ejb, I think it would be nicer to just be > > > able to say - these methods on the session facade are web service > > > enabled. > > > I know that JBoss has JBoss.net which is meant to provide like web > > > services. > > > I'm not sure how this works but we could check it out. > > > > > > > I played around with Axis and it's trivial to create a WS using it - > > there are some sample apps with it. It can create all the descriptors > > for you. JBoss uses Axis so I guess it should be easy. > > > > > Also, I know that the new version of the > > > J2EE 1.4 spec is supposed to support web services. If you read the > > > tutorial on the new web > > > service technology introduced in j2ee 1.4 there are two ways to create > > > web services - via > > > servlets and via stateless session beans: > > > > > > http://java.sun.com/j2ee/1.4/docs/tutorial/doc/NewEJB3.html#80672 > > > > > > "A Web service client can access J2EE applications in two ways. First, > > > the client can access a Web service created with JAX-RPC. Behind the > > > scenes, JAX-RPC uses a servlet to implement the Web service. Second, a > > > Web service client can access a stateless session bean through its Web > > > service endpoint interface. Other types of enterprise beans cannot be > > > accessed by Web service clients." > > > > > > I think coding to this spec would be excellent. We could be one of the > > > first groups to provide an example > > > implementation of an app using the new new spec. Opinions? > > > > Sounds good. Do any of the containers support 1.4 yet? I suppose we're > > promoting xdoclet so does it plan to add this 1.4 functionality? > > > > > > > > > > > Q2: Not as important, is this how online sites actually do process > > > credit card info? I'm not so sure. > > > Are they moving towards processing via web services? Most people who > > > run online sites I know, > > > store the data and batch process the info via a standard visa machine > > > etc. If however the credit > > > card companies are moving towards web services then I think it's a > > > wonderful idea. > > > > > > > I don't know but Struts form validation has an algorithm to check if a > > cc is valid which is probably as far so most retailers go on-line. The > > batch idea sounds about right. > > > > > Brian > > > > > > > > > Herve wrote: > > > > > > For simplification purpose, we can change the structure like this: > > > > > > xpetstore > > > | > > > +--<DIR> doc > > > +--<DIR> lib > > > +--<DIR> src > > > | > > > +--<DIR>ant > > > | | > > > | +-- build.xml > > > | +-- build.properties > > > | +--<DIR> conf [ database and j2ee configuration ] > > > | > > > +--<DIR> etc > > > | | > > > | +--<DIR> jboss [ Files to deploy to JBoss ] > > > | +--<DIR> weblogic [ Files to deploy to WebLogic ] > > > | > > > | > > > +--<DIR> apps > > > | | > > > | +--<DIR> xpetstore > > > | +--<DIR> bank [ bank as a regular .ear file ] > > > | +--<DIR> test > > > | > > > +--<DIR> web > > > | | > > > | +--<DIR> xpetstore > > > | +--<DIR> bank [ SOAP servlet ] > > > | +--<DIR> test > > > | > > > +--<DIR> ejb > > > | > > > +--<DIR> xpetstore > > > +--<DIR> bank [ EJB or POJO for payment processing ] > > > > > > > > > Each ejb component generate the following jars: > > > - <ejb-name>.jar > > > - <ejb-name>-client.jar > > > - <ejb-name>-test.jar (JUnit test-cases) > > > > > > For web components > > > - the test component will be only the JUnitEE servlet that will > > > execute all the > > > test cases of the EJB components > > > > > > For app components > > > - test will test the system. > > > The ant file will deploy it, execute all the test, generate a > > > HTML report and > > > undeploy it. > > > - bank will be a standard ear file that contains (bank.war, > > > bank.jar). > > > > > > > > > > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ########################################### > > This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. > For more information, connect to http://www.F-Secure.com/ > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com > _______________________________________________ > xdoclet-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-user > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
