Hi Chris, There's not much that is specific to Tuscany with Policy Framework other than what you could understand from the specs. Here is the link to the specs...
http://osoa.org/download/attachments/35/SCA_Policy_Framework_V100.pdf?version=1 The specs should give you a good idea of how to define intents and policies, about where you should be defining them and, in general how the policy framework overlies the assembly model and the SCA runtime in terms of how various SCA elements (composite, components, services and references) could specify intents and policysets and how they are to be computed / interpretted by the runtime and the extensions. There are two things with policies - 1) about how you could represent them or specify them 2) about how this representation could be interpretted and put into effect by the SCA runtime or / and its extensions. For 1) we have a standardization for webservices coming in the way of WS-Policy specifications. Alternatively, to start with, you could also come up with your own ways of representing policies which i what has been done to quickly enable ws-security in our Axis2 binding i.e. we have devised our own policy structure to represent axis2 configuration parameters. Here is a sample of that https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/helloworld-ws-service-secure/src/main/resources/definitions.xml. Check the policy sets that have been defined in this definitions.xml For 2), specific to web-services we have quite a bit of Apache software that can read up ws policies and put them into effect for ws-security or ws-reliable messaging and so on. (Neethi, Rampart, Sandesha). These are Axis2 modules that can be loaded for effecting various QoS characteristics. For the policy structure we have defined in the sample above, we have taken care of the processing i.e. loading the policy and handing it out to the Axis2Binding. In the Axis2Binding this policy is interpretted and having to do with config params whatever is read is appropriately injected into the Axis2 config. This is where Tuscany stops and Apache Rampart takes over providing ws-security over our Axis2Binding. Hope this helps :) Thanks - Venkat On 9/26/07, Chris Lo <[EMAIL PROTECTED]> wrote: > > Hi, > > Thanks for all your suggestions. I am kind of new to this policy > framework. > Is there some documentation or code snip someone could provide me so I can > get a starting point? > > Thanks, > Chris > > > On 9/25/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I am not speaking here as policy spec expert but just as somebody who is > > familiar with how its implemented for Tuscany ;-). > > > > It does seem that Sebastien has a point here about getting to specify > > these > > things using policies. > > > > As far as our policy fwk implementation goes with our release 1.0, users > > can > > define as policies anything that can be configured using the Axis2 > > configuration parameters and set this policies on services that they > thing > > should be configured. The axis2 binding will pick up these polices and > > set > > up the parameters appropriately. > > > > - Venkat > > > > On 9/25/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > > > > > Raymond Feng wrote: > > > > Hi, > > > > > > > > AFAIK, the timeout is hard-coded in > > > > org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.java(line > > > > 100): > > > > > > > > requestMC.getOptions().setTimeOutInMilliSeconds(120000L); // 2 > minutes > > > > > > > > Thanks, > > > > Raymond > > > > > > > > ----- Original Message ----- From: "Chris Lo" <[EMAIL PROTECTED]> > > > > To: <[email protected]> > > > > Sent: Monday, September 24, 2007 2:05 PM > > > > Subject: Axis Timeout Setting Inquiry > > > > > > > > > > > >> Hi, > > > >> > > > >> > > > >> > > > >> I am currently experiencing Axis Timeouts when using a jsp to hit > my > > > >> service > > > >> (the service requires a long time to process the request). I notice > > > >> in the > > > >> tuscany-binding-ws-axis2-0.99-incubating.jar, there is a file > called > > > >> axis2.xml in which I think I can specify a timeout value. I was > > > >> wondering is > > > >> this the only way I can do this, or can I specify the timeout value > > > >> in the > > > >> default.composite file / within the wsdl / set some SCADomain > > property? > > > >> > > > >> > > > >> > > > >> Thanks, > > > >> > > > >> Chris > > > >> > > > > > > > > > > I think that this is the kind of thing that could be configured using > a > > > policy intent. That new intent would have to be defined and > implemented > > > in the WS binding runtime. > > > > > > What do our policy spec experts think about this? > > > > > > -- > > > Jean-Sebastien > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > >
