If the suggestion is to do timeouts in a similar way to the soap 1.1/1.2 intent then you can see some code for that in Axis2ServiceClient method requiresSOAP12, the testcase HelloWorldSOAP12TestCase and its HelloWorldSOAP12.composite, and the definitions.xml file in the axis2 binding test resources folder. Basically, add the detail of the new intent to definitions.xml, add the requires="xxx" in the .composite, then the runtime does everything automatically to pick up the intents and the binding impl code can just access the intents by casting the Binding to IntentAttachPoint.
HTH, ...ant 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] > > > > > > > > >
