what is core java and advanced java?

S

Silvio Bierman

Core Java about euqals j2se (standard edition) which comprises about
everuything usefull. Add a serious servlet container and some additional
packages and you have really all you need.

Advanced Java would probably be j2ee (enterprise edition). Watch out for
that one because it contains Enterprise Java Beans, which is total crap.

Good luck,

Silvio Bierman
 
S

Sudsy

Silvio Bierman wrote:
Advanced Java would probably be j2ee (enterprise edition). Watch out for
that one because it contains Enterprise Java Beans, which is total crap.

Now why do you say that? For enterprise application architectures EJBs
such as stateless session beans can be a godsend. High-performance and
scalability are just two of the many benefits to the technology.
It's not the right solution for everyone, but it certainly has a place.
Granted, there were some limitations in previous incarnations (the lack
of ORDER BY in EQL was particularly missed) but the additional layer of
abstraction provided by entity EJBs decouples the application from the
underlying RDBMS. Again, it might not be important to any but the larger
installations but being able to swap out Oracle for DB/2 could be hugely
beneficial, e.g. consolidation subsequent to a merger.
 
S

Silvio Bierman

Sudsy said:
Silvio Bierman wrote:


Now why do you say that? For enterprise application architectures EJBs
such as stateless session beans can be a godsend. High-performance and
scalability are just two of the many benefits to the technology.
It's not the right solution for everyone, but it certainly has a place.
Granted, there were some limitations in previous incarnations (the lack
of ORDER BY in EQL was particularly missed) but the additional layer of
abstraction provided by entity EJBs decouples the application from the
underlying RDBMS. Again, it might not be important to any but the larger
installations but being able to swap out Oracle for DB/2 could be hugely
beneficial, e.g. consolidation subsequent to a merger.

Sudsy,

Understand me correctly, I am all in favour of using proper abstractions.
The perhaps the most important abstraction may be hiding the physical
database structure and implementation/supplier.

I believe in separating large applications in a central logic-server that
has no UI and contains system wide state/logic and multiple applications or
application servers that implement (G)UIs. The internal communication can be
anything that is XML over HTTP, SOAP is a tolerable pick be it somewhat
bloated.

I really dislike object marshalling in any form. That means DCOM, CORBA, EJB
or andy variation on the theme is a no-no for me. I prefer to keep OO inside
architectural components and not let it shine through to the architectural
level itself. I have never seen any good reason or heard any good argument
for doing otherwise.

In my opinion DCOM/CORBA/EJB is just a shortcut to component communication
leading to sub-optimal solutions at best. EJB has the additional drawback of
also providing a shortcut to database abstraction leading to even poorer
results.

Telling my customers they need at least four times the amount of iron to run
applications than they striktly should need is not something I take pride in
also.

Regards,

Silvio Bierman
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top