Re: AW: [JBoss-dev] JB4DR1 Deadline MAY 26

2003-04-04 Thread David Jencks
If we can include/redistribute the jaxm libraries adding the ability to
accept jaxm calls from a jca 1.5  resource adapter to an mdb is very easy. 
I can't understand the license terms and the last time I asked I got no
response.

Is there another jca part to the webservices?

thanks
david jencks

On 2003.04.04 01:44 Jung , Dr. Christoph wrote:
 Until 26th of May, I will have a version of W2EE deployment ready (at
 least
 the subset of the
 webservices.xml and jaxrpc-mapping.xml that can be easily mapped via a
 XSL-driven WebServiceDeployer to the existing
 web-service.xml/AxisService;
 deployer hooks in EJBDeployer+WARDeployer-WebServiceDeployer must be
 coordinated with Bill? And Scott?). 
 
 I will also have catered for a reasonable auto-registration of web
 service
 wsdl in uddi until then.
 
 I cannot guarantuee Xdoclet support to generate J2EE1.4 webservices.xml
 and
 JAXRPC mappings. Maybe there will be a volunteer for this (one of the
 xpetstore guys was interested in trying that out?). Maybe the xdoclet
 team
 will have something in that direction anyway ...
   
 I would delay all web service extensions of JCA and JMS (just a guess
 from a
 quick look into the draft) and the tighter integration of the Axis and
 Jboss
 invocation stacks then after JB4DR1.
  
 CGJ

 
 -Urspr√ľngliche Nachricht-
 Von: Bill Burke [mailto:[EMAIL PROTECTED] 
 Gesendet: Freitag, 4. April 2003 00:28
 An: [EMAIL PROTECTED]
 Betreff: RE: [JBoss-dev] JB4DR1 Deadline MAY 26
 
 
 JBoss Remoting
 AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM
 (waiting on David's response) EMB (Enterprise Media Beans) JUDDI
 integration
 If I can get it done:  AOP + EJB (packaged extensions to EJB)
 
 and don't forget Nukes!
 
 Anybody got anything to add to this list?
 
 Who doesn't think they'll be done by May 5th?
 Who thinks they'll be cutting it close?
 
 
 
 Bill
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of 
  Dain Sundstrom
  Sent: Thursday, April 03, 2003 4:48 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26
  
  
  Ok then there are 4 weeks to get the new stuff done?
  
  Marc, Bill,  sure we could do a release but what difference would it
  make if the new features are not in it.  Is this a release just to show
 
  off AOP?  What about any of the other new stuff?
  
  Just give the users a solid 3.2 and they will be happy.
  
  -dain
  
  On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote:
  
   It will be ready and stable.  Functionality freeze is May 5th.  What 
   functionality doesn't make it by then will be left out of the 
   release.
  
   Bill
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED] Behalf Of
   Dain
   Sundstrom
   Sent: Thursday, April 03, 2003 4:01 PM
   To: [EMAIL PROTECTED]
   Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26
  
  
   I think you are delusional if you think JB4 will be ready for 
   JavaOne.
  
   -dain
  
   On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote:
  
   Guys,
  
   We are thinking a lot about the forthcoming JB4 release.  It is a
   truly
   exciting step for us as we believe we will bring a programming
 style,
   whose time has come, to a mass audience.
  
   AOP as Bill says is a clear wave for system level services on par
   with
   OOP.  On top of it and also as a proof of how powerful the approach
 
   is
   we still develop a full J2EE server.  Meaning that you can choose
 to
   live in the J2EE world work on JBoss J2EE and access all the
   prepackaged
   AOP goodies as you have been doing since JBoss2.0.
  
   There seems to be a lot of fear at SUN from what I can tell in the 
   press, that we will abandon J2EE.  We love J2EE. When really we 
   will support J2EE for the forthcoming future.  Never do we talk 
   about abandoning J2EE, we just let the user access core 
   functionality in the open server and think at the AOP level.  A 
   more fundamental construct of
   the framework.
  
   The reason we are almost there is that it is also a very old 
   implementation in JBoss.  We have been doing it for a long time 
   but never talked/packaged it this way.  We make it easy for you to 
   leverage the AOP layer. The implementation is old the way you 
   interact with JBoss
   is new.  It can also be old if you decide to stay at the J2EE level
   which will be fully supported.
  
   But you are now invited to roam in the core JBoss system, in fact 
   you may find it very cozy as you port POJO based applications to 
   JBoss. There will be a stabilization period though.  We are making 
   an aggressive push to release JB4 by JavaONE with all our 
   resources dedicated to implementing the final AOP system aspects 
   and porting some of the existing code to that.
  
   We're making an aggressive push to release JBoss 4.0 by JavaOne.
   We're
   targeting May 26th. That leaves us 2 month from now.
  
   I 

AW: [JBoss-dev] JB4DR1 Deadline MAY 26

2003-04-03 Thread Jung , Dr. Christoph
Until 26th of May, I will have a version of W2EE deployment ready (at least
the subset of the
webservices.xml and jaxrpc-mapping.xml that can be easily mapped via a
XSL-driven WebServiceDeployer to the existing web-service.xml/AxisService;
deployer hooks in EJBDeployer+WARDeployer-WebServiceDeployer must be
coordinated with Bill? And Scott?). 

I will also have catered for a reasonable auto-registration of web service
wsdl in uddi until then.

I cannot guarantuee Xdoclet support to generate J2EE1.4 webservices.xml and
JAXRPC mappings. Maybe there will be a volunteer for this (one of the
xpetstore guys was interested in trying that out?). Maybe the xdoclet team
will have something in that direction anyway ...
  
I would delay all web service extensions of JCA and JMS (just a guess from a
quick look into the draft) and the tighter integration of the Axis and Jboss
invocation stacks then after JB4DR1.
 
CGJ
   

-Urspr√ľngliche Nachricht-
Von: Bill Burke [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 4. April 2003 00:28
An: [EMAIL PROTECTED]
Betreff: RE: [JBoss-dev] JB4DR1 Deadline MAY 26


JBoss Remoting
AOP + tx, security, versioning, remoting, clustering, txlock, caching DTM
(waiting on David's response) EMB (Enterprise Media Beans) JUDDI integration
If I can get it done:  AOP + EJB (packaged extensions to EJB)

and don't forget Nukes!

Anybody got anything to add to this list?

Who doesn't think they'll be done by May 5th?
Who thinks they'll be cutting it close?



Bill

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of 
 Dain Sundstrom
 Sent: Thursday, April 03, 2003 4:48 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26
 
 
 Ok then there are 4 weeks to get the new stuff done?
 
 Marc, Bill,  sure we could do a release but what difference would it
 make if the new features are not in it.  Is this a release just to show 
 off AOP?  What about any of the other new stuff?
 
 Just give the users a solid 3.2 and they will be happy.
 
 -dain
 
 On Thursday, April 3, 2003, at 03:30 PM, Bill Burke wrote:
 
  It will be ready and stable.  Functionality freeze is May 5th.  What 
  functionality doesn't make it by then will be left out of the 
  release.
 
  Bill
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of
  Dain
  Sundstrom
  Sent: Thursday, April 03, 2003 4:01 PM
  To: [EMAIL PROTECTED]
  Subject: Re: [JBoss-dev] JB4DR1 Deadline MAY 26
 
 
  I think you are delusional if you think JB4 will be ready for 
  JavaOne.
 
  -dain
 
  On Thursday, April 3, 2003, at 02:47 PM, marc fleury wrote:
 
  Guys,
 
  We are thinking a lot about the forthcoming JB4 release.  It is a
  truly
  exciting step for us as we believe we will bring a programming style,
  whose time has come, to a mass audience.
 
  AOP as Bill says is a clear wave for system level services on par
  with
  OOP.  On top of it and also as a proof of how powerful the approach 
  is
  we still develop a full J2EE server.  Meaning that you can choose to
  live in the J2EE world work on JBoss J2EE and access all the
  prepackaged
  AOP goodies as you have been doing since JBoss2.0.
 
  There seems to be a lot of fear at SUN from what I can tell in the 
  press, that we will abandon J2EE.  We love J2EE. When really we 
  will support J2EE for the forthcoming future.  Never do we talk 
  about abandoning J2EE, we just let the user access core 
  functionality in the open server and think at the AOP level.  A 
  more fundamental construct of
  the framework.
 
  The reason we are almost there is that it is also a very old 
  implementation in JBoss.  We have been doing it for a long time 
  but never talked/packaged it this way.  We make it easy for you to 
  leverage the AOP layer. The implementation is old the way you 
  interact with JBoss
  is new.  It can also be old if you decide to stay at the J2EE level
  which will be fully supported.
 
  But you are now invited to roam in the core JBoss system, in fact 
  you may find it very cozy as you port POJO based applications to 
  JBoss. There will be a stabilization period though.  We are making 
  an aggressive push to release JB4 by JavaONE with all our 
  resources dedicated to implementing the final AOP system aspects 
  and porting some of the existing code to that.
 
  We're making an aggressive push to release JBoss 4.0 by JavaOne.
  We're
  targeting May 26th. That leaves us 2 month from now.
 
  I REPEAT TARGET FOR JBOSS4.0 DR1    MAY 26TH
 
 
  To meet this aggressive deadline, we need to set some dates.  
  There will be a functionality freeze, Monday, May 5th.  All new 
  functionality commits after May 5th must be approved by either 
  Scott Stark, or Bill Burke.  We will not branch May 5th, but 
  instead make the month of May,
  JBoss 4.0 stability en route to a Developpers Release 1 (DR1).
 
  Please think long and hard and fast about your modules.  Many of 
  you are