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

Reply via email to