Which Web service is better EJB or RPC - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>Java - 爪哇娇娃

Which Web service is better EJB or RPC

Which Web service is better EJB or RPC# Java - 爪哇娇娃

c*c2005-01-19 08:01

1 楼

I was using EJB web services. Now I found that RPC web services is much
simpler. It also has OUT, INOUT parameter. RPC web serivces can be used by
.NET
I have to modify EJB web services to RPC web services.
What is advantage of EJB web services? Thanks

t*s2005-01-19 08:01

2 楼

What's the definition of "EJB web services" and "RPC web services"?

【在 c***c 的大作中提到】

: I was using EJB web services. Now I found that RPC web services is much
: simpler. It also has OUT, INOUT parameter. RPC web serivces can be used by
: .NET
: I have to modify EJB web services to RPC web services.
: What is advantage of EJB web services? Thanks

r*l2005-01-19 08:01

3 楼

Guess you do not know web service very well. There's no EJB web service per
se.
Web service has nothing to do with platform and a specific technology, e.g.
EJB.
Web service comes with two flavor (style) - RPC or Document.
In Java world, you can wrap a EJB with a web service. Then, your EJB will be
invoked from other language/platform, e.g. .NET. The web service on top of EJB
can be either RPC style or Document style.
So, you question itself is kind of wrong already. Web service looks simple,
but

【在 c***c 的大作中提到】

c*c2005-01-19 08:01

4 楼

Yes I am new in Web Services. My boss just gave me a concept and I have to
figure out everything
In wsdd file, there is either provider="RPC" or provider="EJB". If I am using
EJB in web services, I have toconvert java code to EJB, generate local and
remote interfaces and create ejb-jar.xml. If I do not use EJB, I can keep old
java code as business methods and simply wirte deploy.wsdd file to deploy the
web services. So I think "RPC" is much simplier.
Thank you very much. I will read more to dige

【在 r***l 的大作中提到】

: Guess you do not know web service very well. There's no EJB web service per
: se.
: Web service has nothing to do with platform and a specific technology, e.g.
: EJB.
: Web service comes with two flavor (style) - RPC or Document.
: In Java world, you can wrap a EJB with a web service. Then, your EJB will be
: invoked from other language/platform, e.g. .NET. The web service on top of EJB
: can be either RPC style or Document style.
: So, you question itself is kind of wrong already. Web service looks simple,
: but

r*l2005-01-19 08:01

5 楼

WSDD, then you are talking about Axis. It is Axis specific, about to deploy a
web service using Axis implementation.
Starts from WSDL, in WSDL, there's "RPC" style and "Document" style. Once you
understand the basic Web service better, then touch Axis.

using
old
the
per
e.g.
be
simple,
about
by

【在 c***c 的大作中提到】

: Yes I am new in Web Services. My boss just gave me a concept and I have to
: figure out everything
: In wsdd file, there is either provider="RPC" or provider="EJB". If I am using
: EJB in web services, I have toconvert java code to EJB, generate local and
: remote interfaces and create ejb-jar.xml. If I do not use EJB, I can keep old
: java code as business methods and simply wirte deploy.wsdd file to deploy the
: web services. So I think "RPC" is much simplier.
: Thank you very much. I will read more to dige

i*k2005-01-19 08:01

6 楼

In general, use pure Java (POJO) vs. EJB as much as possible.
Architecturally speaking, once you start using EJB, your web services has a
dependency on a specific implementation technology - EJB. This brings a whole
bunch of issues. First, your MTR now includes an EJB container. Second, EJB
itself is a controversial technology. Some published J2EE experts have been
evangelizing J2EE architectures without EJBs, or only stateless session beans.
Third, your collegues will laugh at your design. :-)

【在 c***c 的大作中提到】