Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jca-dev] Name Vote
Hi,

On Wed, May 29, 2019 at 3:17 PM James Stephens <hunting@xxxxxxxxxx> wrote:

My guess is most of the experts that created and worked on this specification considered it an architecture. The JCA specifications is all about of how objects interact with each other.

Its likely some of the newer specification are architectures, but when the name was created for the specification, the architecture name was not used.


I think that for a lot of specs in the past the names were just somewhat arbitrarily chosen. It's like when two developers create business classes without any naming conventions. You'll end up with say a CustomerService and a PriceManager. Is the first more a "service" than the second is a "manager"? Likely that's not the case at all. The first dev just used "service" and the second "manager", even though those two classes would do very similar things.
 

Everyone has different name preferences, I really don't have a strong opinion on new names, but changing names after they have been used for several years always results in some confussion for both developers and customers that should be avoided unless required.


I appreciate the different name preferences everyone has, and that's of course a given. Ending each spec with "architecture" is not necessarily better or worse than ending each spec with "API" or one of the ~5 other filler words that are being used in practice.

But when looking at Jakarta EE as a whole, it's probably more confusing that only JCA is called an "architecture", while some specs are "APIs" and yet some others are nothing. People would naturally wonder what's so different about JCA that it, and only it, is an architecture. 

Just my 2 cents though

Kind regards,
Arjan

 



Thanks,


James Stephens
WebSphere RRA and J2C Team Lead
hunting@xxxxxxxxxx
Phone: (507)398-7830


Inactive hide details for arjan tijms ---05/29/2019 06:31:32 AM---Hi James, It was discussed in the issue, but still wondering.arjan tijms ---05/29/2019 06:31:32 AM---Hi James, It was discussed in the issue, but still wondering. Why according to you is

From: arjan tijms <arjan.tijms@xxxxxxxxx>
To: jca developer discussions <jca-dev@xxxxxxxxxxx>
Date: 05/29/2019 06:31 AM
Subject: [EXTERNAL] Re: [jca-dev] Name Vote
Sent by: jca-dev-bounces@xxxxxxxxxxx




Hi James,

It was discussed in the issue, but still wondering. Why according to you is JCA an architecture, but JPA is an API? And JSF and JMS are neither? Why are JASPIC and JACC not architectures?

Not trying to be clever here, but just like to make it clear why you think of all the Jakarta EE specs, JCA is one of the few to qualify to be called an architecture, while the other specs don't qualify to be called that? What's the difference?

Kind regards,
Arjan Tijms



On Tue, May 28, 2019 at 8:33 PM James Stephens <hunting@xxxxxxxxxx> wrote:

_______________________________________________
jca-dev mailing list
jca-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jca-dev

Back to the top