> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Meyer-Willner, Bernhard
> Sent: Wednesday, February 19, 2003 7:11 AM
> To: '[EMAIL PROTECTED]'
> Subject: Re: [JBoss-user] Is 4.0 new or evolution of 3.2?
>
>
> Bill,
>
> you write in your mail "Is 4.0 new or evolution of 3.2?":
>
> "In 4.0, we want to generalize interceptor technology and detached
> invocations so that any
> type of object or any plain old Java Class can leverage these
> technologies.
> We want to bring J2EE services transparently and implicitly to plain old
> java objects and classes and truly isolate business logic from
> infrastructure."
>
> True, this sounds extremely cool, but what about J2EE portability? By
> introducing your new concepts, you're contributing to making J2EE
> portability even more of a myth, or aren't you?
>

J2EE is our bread and butter.  We will still be improving our J2EE
implementation and strictly following the J2EE specifications.  If you don't
want to use our new AOP services, then don't use them.

> OK, if I will only and forever use JBoss it will certainly be
> awesome to use
> POJO's having the same capabilities as, for instance, EJB 2.x CMP entity
> beans w/o having all that entity bean overhead (extra interfaces
> and so on).
> But if I want to keep my app portable - regarding providing
> persistence - I
> would rather look at JDO and other commercial or open source O/R mappers
> than using the then proprietary JBoss AOP solution. Or are there plans to

That's your perogative.  We want to be leaders for once and not followers.
I think our approach is going to be revolutionary and we will become our own
standard.  We're in this for the long haul and not just for the lifespan of
these clunky specifications that are designed by committee.  I saw CORBA
stagnate because of the political OMG committees.  IMHO, J2EE is now
suffering from this as well.  DCE, CORBA, J2EE were all fine iterations the
Nirvana of distributed computing.  Its time to innovate and iterate again.

> make this, for example, JDO-like?
>


I'm not sure what the persistence layer will look like.  We're hoping that
the AOP framework and the new persistence engine design will allow us to
look like anything, but those are high naive hopes.  There's also been talk
about being JDO-like, but you'll have to go on the persistence development
forums to find out what's going on.

> Will it also be possible to use a POJO as a session bean which
> has the same
> capabilities? If so, will it be possible to automatically convert this
> "Session POJO" to a standard EJB Session Bean or will this again be
> proprietary - so to speak, neat, if I'm gonna use JBoss forever, but
> otherwise unusable in other appservers.
>

Again, leaders not followers.  You'll see soon.  The whole industry will be
moving in this direction of AOP and AOP services.  We hope to be there first
and leverage our strengths in J2EE.


> I'm just afraid of pushing JBoss into a niche where it doesn't belong, by
> promoting to use POJOs behaving like EJBs when using JBoss, however
> resulting in a non-portable solution. What are your thoughs, JBoss team?
>

Leaders not followers.

> Anyway, general architecture sounds real interesting and I would love
> pointers to whitepapers and docs about the upcoming release, if available.
>

Look on the development forums and browse around the projects link on the
website.  I just posted some crappy AOP framework docs.  The AOP framework
generally works, but our AOP services are basically whiteboard right now.
Whitepapers will be coming out once we get some AOP services working and the
AOP framework more finalized.

XXXXXXXXXXXXXXXX
Bill Burke
Chief Architect
JBoss Group, LLC
XXXXXXXXXXXXXXXX



-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to