Ivelin (& others), Wrt the rollback and how this will affect JB.net, Anil, Bill and me came to the conclusion that the 3.2 code [that already builds upon Axis1.1Final] would be a sufficient base for the next 4 weeks [in which I am on "baby holiday" and most likely neither online nor sitting on a computer anyway ;-] Hence I do not want to turn your current attention from where it is needed now.
>From my experiences, most people currently work on a combination of the 3.2 runtime and the "head" xdoclet module. Thanks to Neal Sanche, there is a compiled version available at http://www.nsdev.org/jboss/stories/xdoclet-module-jboss-net.jar (not to forget his valuable walkthrough at http://www.nsdev.org/jboss/stories/jboss-net.html). Anil who is now the co-lead would then have a look at porting the UDDI server and driving the JAXR interfaces forward; I would care about reimplementing the WS4EE spec [since the "legacy" 4.0 version builds upon too much deployment code that has definitely faded - especially the xsl deployer which was introducing too much runtime/configuration instabilities]. Nevertheless we need to broaden the team to reach the overall vision of making JBoss.net a "nexus of interoperability" in JBoss4 which is a good opportunity for developers to get aquainted to web services technology (in the order of priority): - We could need someone integrating the still separate junit tests of jb.net (we were an optional module in 3.2!) with the overall testsuite. - We could need someone looking at the xdoclet module (there is a JSR on "Web Service Metadata" pending for which I saw a sneak preview by BEA somewhere ... if we could manage to use these doclet tags as the basis of a WS4EE-xdoclet module, that would be of tremendous usefulness IMHO). - Someone should specialize in making JMX-based web services as comfortable as possible. - Someone should specialize in EJB-based web services and drive forward the existing provider code. - We need an interface to the messaging and remoting modules in order to remove code redundancies. - We need a M$.NET specialist in order to address interoperability issues with C#,VB, etc-Clients. Same holds for Macromedia Flash and JAXRPC4ME. - Someone should get deep knowledge in WS-Security with all its signing, encryption, etc bits and improve the existing connection between JB.Net Security handlers and the jboss security architecture in that direction. - We could need someone having a look at the rolled back smtp/saaj support. These are IMHO extremely fascinating topics for tech-heads and will be highly requested by employers in the next years. Please refer to jboss-devel/anil if you have interest. I´ll send a notice (with a baby picture ;-) when I´m back (and unbelievably keen on doing computing again ;-) Best, CGJ > -----Original Message----- > From: Ivelin Ivanov [SMTP:[EMAIL PROTECTED] > Sent: Donnerstag, 28. August 2003 19:24 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] 4.0 rollback 1st phase complete > > Bill, > > All my recent commits were in Branch_3_2. > Do I need to do something to merge them into HEAD or you already did that? > > How can I help with the web services work? Where to start? > > > ########################################### This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange. For more information, connect to http://www.F-Secure.com/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
