ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Update of "Frontpage/Axis2/f2f 2/Scribe31" by DeepalJayasinghe
Date Thu, 31 Mar 2005 08:26:35 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by DeepalJayasinghe:
http://wiki.apache.org/ws/Frontpage/Axis2/f2f_2/Scribe31

------------------------------------------------------------------------------
  [10:24]<GlenD> -- If the default is "robust" then the engine can wait until it sees
either a "202 OK" or a fault on the HTTP connection before it returns.
  [10:25]<alek_s> example for one way without fault:   /** @OneWay */ public void someMethod(SomeParam)
  [10:25]<GlenD> I think the default should be "return immediately"
- 
+ <Deepal> chat log http://wiki.apache.org/ws/Frontpage/Axis2/f2f_2/Scribe31
+ [10:27]<alek_s> Glen: i agree - it is what one-way means - as son as message is out
you can start doing other things
+ [10:29]  *** alek_s is now known as aleks_12hourslag
+ [10:30]  *** aleks_12hourslag is now known as aleks_11hour_lag
+ [10:34]<GlenD> *** TAKING A TEA BREAK ***
+ [10:34]<GlenD> back in a few...
+ [10:43]<Chinthaka> listing : what we need to 1.0
+ [10:49]<Deepal> what are going to do next
+ [10:49]<Deepal> supportinng SOAP 1.1/1.2
+ [10:49]<Deepal> WSDL 1.1/2.0
+ [10:49]<Deepal> specs
+ [10:49]<Deepal> Modules
+ [10:50]<Deepal> RM , security
+ [10:50]<Deepal> session
+ [10:50]<Deepal> Transports
+ [10:50]<Deepal> HTTP/SMTP/TCP
+ [10:51]  *** GlenD quit FreeNode : Read error: 145 (Connection timed out)
+ [10:52]<Deepal> -- Providers
+ [10:52]<Deepal> Java
+ [10:52]<Deepal> E4X
+ [10:52]<Deepal> --
+ [10:53]<Chinthaka> WSA impl of 2004/08 and final version
+ [10:54]<Deepal> RPC encoding
+ [10:55]<Deepal> MIME/MTOM/SwA
+ [10:55]<Deepal> Java provider 
+ [10:55]<Deepal> RPC & MSG
+ [10:57]<Deepal> supporting WS police
+ [10:58]  *** dims left #apache-axis : 
+ [10:59]  *** chathura joined #apache-axis
+ [10:59]<Deepal> Data binding framework has to be there
+ [11:01]<Deepal> How deployment and Deployment
+ [11:01]<Deepal> Client API , modules
+ [11:02]<Deepal> interopt testing
+ [11:03]<Deepal> WS-I sample application
+ [11:03]<Deepal> java2WSDL
+ [11:03]<Deepal> and WSDL2Java
+ [11:05]<Deepal> Managment tool
+ [11:06]<Deepal> More tool (eclipce)
+ [11:08]<Chinthaka> hey guys
+ [11:08]<Chinthaka> look at http://wiki.apache.org/ws/FrontPage/Axis2/f2f-2
+ [11:08]<Chinthaka> for Axis 2 1.0 requirements
+ [11:08]<Chinthaka> its the last item
+ [11:10]<chathura> deployment
+ [11:10]<chathura> .........................................
+ [11:10]<chathura> Decession
+ [11:11]<Chinthaka> Guys, is that list ok ... ?
+ [11:11]<chathura> "We need a way to find the required services,etc ohther than in
AXIS_HOME
+ [11:12]<sanjiva_> I'd like to add one more requirement to 1.0: Support for REST Web
services too
+ [11:13]<sanjiva_> (its very easy to do)
+ [11:13]<Srinath> :)
+ [11:15]<Chinthaka> agreed, even Shawn was concerned abt this
+ [11:20]  *** ashutosh joined #apache-axis
+ [11:23]<Chinthaka> so shall we add REST support ?
+ [11:23]<Chinthaka> for Axis 2  1.0 ?
+ [11:27]  *** chathurah__ joined #apache-axis
+ [11:33]<chathurah__> Problem with deployment
+ [11:34]  *** chathura quit FreeNode : Read error: 60 (Operation timed out)
+ [11:35]<chathurah__> "How will the service isolation using seperate class loader will
affect the module which is required to be shared over services
+ [11:35]<chathurah__> "
+ [11:44]  *** Thilina quit FreeNode : Read error: 54 (Connection reset by peer)
+ [11:48]<chathurah__> Discussion :can the module in its own declare a phase inside
it
+ [11:50]<chathurah__> glen says : no reason you shouldnt
+ [11:50]<chathurah__> dr sanjiva says YAGNI
+ [11:50]<chathurah__> :d
+ [11:54]  *** GlenD joined #apache-axis
+ [12:02]<GlenD> Open topic - Module-specific phases (i.e. module.xml defines new phases)
+ [12:03]<GlenD> Open topic - referring to individual handlers within other Modules
(i.e. "I need to run after the 'authentication' handler" instead of just using phases for
constraints)
+ [12:04]<GlenD> WRT Module-specific phases, discussion included the idea that modules
are able to define new phases so that other modules can refer to them.  These phases become
available EITHER a) globally (by editing server.xml, etc) OR b) locally (i.e. that phase may
only exist for the service where the module is deployed)
+ [12:05]<Srinath> creating a list of the default pahses ..we differed for investigation
+ [12:05]<Srinath> but need to done in quickly and to do it in the mailing list.
+ [12:07]<Srinath> should we have the inter module dependancies
+ [12:07]<Srinath> ?
+ [12:08]<Srinath> we leave the Q more or less open
+ [12:21]<Srinath> To lunch
+ [12:23]  *** dasarath quit FreeNode : "Miranda IM! Smaller, Faster, Easier. http://miranda-im.org"
+ [12:33]  *** FR^2 joined #apache-axis
+ [12:54]  *** Jaliya quit FreeNode : Read error: 54 (Connection reset by peer)
+ [13:02]  *** FRQuadrat joined #apache-axis
+ [13:05]  *** FR^2 quit FreeNode : Nick collision from services.
+ [13:05]  *** FRQuadrat is now known as FR^2
+ [13:31]<Chinthaka> back after lunch
+ [13:45]<Chinthaka> back to module interface discussion
+ [13:52]  *** foxsden quit FreeNode : Read error: 110 (Connection timed out)
+ [13:53]<GlenD> No revoke() for now... if you want to deal with faults, put a handler
on the fault flow
+ [13:53]  *** Jaliya joined #apache-axis
+ [13:55]<GlenD> We discussed the possibility that various components (handlers, etc)
might want to do cleanup when a given scope (message, interaction, server) ends.  We should
note that we might want to use something like context.registerExitHandler(ExitHandler) in
order to do this - this would allow Handlers to put resources in a DB, higher level context,
etc, and then clean them up when the interaction ends (like finally {} in Java)
+ [13:55]  *** Jaliya left #apache-axis : 
+ [13:55]  *** Jaliya joined #apache-axis
+ [13:56]<sanjiva_> On the question of a handler changing the handler chain dynamically:
You are not allowed to do that. Modules can edit the handler chain the way they want at module
engagement time but once a message is flowign thru the chain the chain cannot be modified.
+ [14:00]<sanjiva_> Note: handler programming model will say its not a good idea to
do the above (and if you do then all bets are off) .. we won't write code that will check
this.
+ [14:03]  *** dasarath joined #apache-axis
+ [14:04]  *** Jaliya quit FreeNode : Read error: 104 (Connection reset by peer)
  
  }}}
  
Mime
View raw message