Support Forums: Message List - J2EE Connector Architecture or Web Services for Integration?

great job

Tue, 05 Feb 2013 02:39:29 -0500

J2EE is the best out there?

J2EE Connector Architecture or Web Services for Integration?

Tue, 04 Jun 2002 11:37:24 -0400

I'm new to JCA and wonder if a JCA adapter can be plugged into every J2EE compliant container. I would like to use JCA to build a messaging system (hub) for different ERP systems using a SOAP engine....

J2EE Connector Architecture or Web Services for Integration?

Wed, 15 May 2002 21:58:13 -0400

Tyler, Tyler, Tyler. :-)...

J2EE Connector Architecture or Web Services for Integration?

Wed, 15 May 2002 16:35:18 -0400

"Real-world integration requires the application of a continuum of technologies, not a "one size fits all" approach."...

J2EE Connector Architecture or Web Services for Integration?

Wed, 15 May 2002 14:03:01 -0400

Steve, Steve, Steve. I had done such a good job of keeping vendor perspectives out of the article and thread. Honestly, why do you think I wrote the article in the first place? It's because BEA WebLogic Platform 7.0 does everything that you describe,...

J2EE Connector Architecture or Web Services for Integration?

Tue, 14 May 2002 17:02:20 -0400

One of the fundamental assumptions that Tyler's article and much of the discussion stemming from it seem to make is that you have to choose between tight coupling, via something like JCA, or loose coupling, via something like Web Services. In the real...

J2EE Connector Architecture or Web Services for Integration?

Tue, 14 May 2002 10:36:16 -0400

Agree partly. IMO the Web Service and JCA shall be used together probably and each has its own place in big picture, though all the pieces have to be developed before that. Conceptually If I am a service provider and have legacy data, I will use an...

J2EE Connector Architecture or Web Services for Integration?

Sat, 11 May 2002 11:47:20 -0400

WS and JCA are likely to become part of a bigger solution indeed. The loosely coupled model is not replacing the tightly coupled model. The lines between application development and application integration are blurring. What customers want is to develop...

J2EE Connector Architecture or Web Services for Integration?

Wed, 08 May 2002 10:11:14 -0400

...

J2EE Connector Architecture or Web Services for Integration?

Wed, 08 May 2002 02:52:52 -0400

For an API Provider with a sound multi tier architecture it shouldn't be a big problem to both expose an API as a web service, a JCA or whatever comes tomorrow, should it ? For the people who are about to use the API, the question is more difficult, of...

J2EE Connector Architecture or Web Services for Integration?

Wed, 08 May 2002 01:18:58 -0400

Tyler's got some excellent points in this article, which I generally I agree with....

J2EE Connector Architecture or Web Services for Integration?

Tue, 07 May 2002 12:51:54 -0400

If I need to expose a service to various people (to divisions in my large company, or to partners) then...

J2EE Connector Architecture or Web Services for Integration?

Tue, 07 May 2002 12:46:04 -0400

The comment I would have is that web services span a wider area of integration than JCA. I wish the whole world is using java and J2EE, and that simply is not true....

J2EE Connector Architecture or Web Services for Integration?

Tue, 07 May 2002 10:58:22 -0400

I think Tyler made a very good point on "intrusion." Most web services evangelists paint a picture where in some piece of legacy can just be exposed as a "service" so that it is immediately available to every computing device out...

J2EE Connector Architecture or Web Services for Integration?

Tue, 07 May 2002 08:17:02 -0400

The whole article talks from the data integration point of view thus overshadowing Webservices. Webservices is all about exposing a service(which is nothing but a business component serving some functionality)to the external world. So it will be very...