[ http://issues.apache.org/jira/browse/AXISCPP-282?page=comments#action_12319565 ]
Samisa Abeysinghe commented on AXISCPP-282: ------------------------------------------- Yes init is called for every method invocation right now. If we want one off activities, whay cant we use the constructor? Would it be a bad idea to have the database connection opening in the constructor? > Every request triggers the init() function on server side. Should call only > once for initing > -------------------------------------------------------------------------------------------- > > Key: AXISCPP-282 > URL: http://issues.apache.org/jira/browse/AXISCPP-282 > Project: Axis-C++ > Type: Bug > Components: Server - Engine > Versions: 1.4 Alpha > Environment: All platforms > Reporter: Samisa Abeysinghe > Assignee: Chinthana Danapala > > It appeared to me that every request triggers the init() function. For > the > short-term, I moved the code from init() to the constructor. I expect > someone will have a proper fix soon. > -Duke > -----Original Message----- > From: Mauro Tosca [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 23, 2004 3:50 PM > To: [email protected] > Subject: connection to database > Hi. > I am trying to publish a web service to access a database: a client > calls the ws, the ws makes a query to the database and returns the > retrieved data as a string. > Modifying the skeleton generated by axis, i've written in the init > method of MyClassPortType.cpp the code to open a connection to the > database. I thought it would be the only connection of the ws, shared > by all > the client's requests. But i noticed the service is quite slow: i > suppose that the init method is executed for EVERY client's request. > Am I wrong? > If the init method is executed every time, for every call to the ws, > what's for? In this way, if i understood, the web service is > completely stateless...or have i completly misunderstood everything?? > ..you know, it's really likely! :) > thanks a lot! > Mauro -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
