No problem.  Suggestion withdrawn.
 
-Jim

        -----Original Message----- 
        From: [EMAIL PROTECTED] 
        Sent: Tue 10/16/2001 1:01 AM 
        To: [EMAIL PROTECTED] 
        Cc: 
        Subject: Re: Jonas SOAP Support?
        
        

        I agree with you that we should look forward to see what is
coming in next versions of J2EE. But shouldn't we first look at
_current_ spec? There are lots of things in J2EE 1.2/1.3 (even in EJB
2.0) that JOnAS is miles away from (Where is the new CMP model? Where is
security services? Where is container interoperability? etc.). Before we
discuss, what could be in J2EE 1.4 (e. g., what does this relate to an
EJB-container-only-product?) we should discuss how to implement the
_current_ spec. After that, we should discuss on a higher level: Is
JOnAS really only an EJB container, or will it tend to become a complete
server product that is greater than J2EE (since SOAP is not mandatory in
neither J2EE 1.2 nor 1.3, but only an option that COULD come in the next
release, that, if we are honest, does not appear before the next twelve
months). So the question is: quo vadis, JOnAS? I mean, what sense does
it make to implement SOAP ontop of JOnAS if JOnAS is currently not able
to do all !
        what EJB 2.0 tells? At
        ent, JOnAS is a horizontal layer in the J2EE architecture, with
SOAP ontop, it will become a totally specialized product. If we plan to
make JOnAS a _complete_ server product, including top-level protocols
like SOAP or HTTPS, we should make a good plan how to implement this.
        
        -------- Original Message --------
        Subject: RE: Jonas SOAP Support? (15-Okt-2001 21:32)
        From:    [EMAIL PROTECTED]
        To:      [EMAIL PROTECTED]
        
        > True, JOnAS is an EJB container only; however, there are parts
to JOnAS
        > that are not part of the J2EE specification, such as the
introduction of
        > JMX for application management.
        >
        > The thought was to incorportate JAXM, JSR-67, into JOnAS.
From the JAXM
        > v0.94 spec section 2.4, "JAXM applications may be deployed in
Servlet
        > 2.2 and/or J2EE 1.3 containers.  It is anticipated that future
version
        > of the J2EE specification will include JAXM-specific
deployment
        > information."
        >
        > From the J2EE 1.3 specification, section 11.1, "Support for
web services
        > is likely to be a primary focus for the next version of J2EE."
This
        > includes JSR-67.
        >
        > If development thinks that JAXM and web services should remain
on the
        > web tier, then I'll withdraw the suggestion.
        >
        > Jim Shain
        > Sr. Architect
        > ALLTEL Information Services
        >
        > -----Original Message-----
        > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
        > Sent: Monday, October 15, 2001 9:52 AM
        > To: [EMAIL PROTECTED]
        > Subject: Re: Jonas SOAP Support?
        >
        >
        > But what sense does this make? JOnAS is an EJB container only,
not a
        > complete server product. Or is the project target changed and
JOnAS aim
        > is now to build a complete server product?
        > ----
        > To unsubscribe, send email to [EMAIL PROTECTED] and
        > include in the body of the message "unsubscribe jonas-users".
        > For general help, send email to [EMAIL PROTECTED] and
        > include in the body of the message "help".
        >
        > To: [EMAIL PROTECTED]
        
        
        To: [EMAIL PROTECTED]
        Cc: [EMAIL PROTECTED]
        
        ----
        To unsubscribe, send email to [EMAIL PROTECTED] and
        include in the body of the message "unsubscribe jonas-users".
        For general help, send email to [EMAIL PROTECTED] and
        include in the body of the message "help".
        


Attachment: winmail.dat
Description: application/ms-tnef

Reply via email to