On Fri, Jul 16, 2010 at 1:00 AM, Sam Carleton
<[email protected]> wrote:
> Shankar,
>
> First off, for my sake, this has become a much larger deal then it
> should have been, fore I am already passing other info from the server
> to the buz logic, I am in the process of taking this info on to that
> as well, but if I am not mistaken it is a bit of a hack and ideally I
> would like a more official way of doing it.
>
> To answer your questions:  My application run under a server other
> then the one that comes with Axis2/C, Apache to be specific.  The
> application is made of two major packages:
>
> 1: C modules/handlers that are native to the server (aka custom apache 
> modules)
> 2: Axis2/C web services
>
> Both packages need some "context".  The context consists of
> configuration data and a connection to the database.  The C modules
> setup the context for each request and uses that one context through
> out the request.  Rather then having to recreate this context and have
> a separate pool management system for the Axis2 web services, I would
> like to simply pass the context from the server to web service.


I am assuming the "context" are passed as part of the "request_rec"
strcture from "custom apache modules" to Axis2/C. If my assumption is
correct, my suggestion is to modify apache2_worker to pass the
"request_rec" structure as part of the message context's property map.
One possibility is we always include this detail in the message
context property map as an opaque parameter (for example property
map's key will be always "SERVER_REQUEST"), so that user's logic can
search for that key..

Regards,
Shankar


>
> Sam
>
> On Thu, Jul 15, 2010 at 12:08 AM, Selvaratnam Uthaiyashankar
> <[email protected]> wrote:
>> Sam,
>>
>> Let me try to understand your question correctly. If you want to pass
>> a void* from the server to business logic, you can pass it as part of
>> the context hierarchy. Create a void*, and put it inside the parameter
>> of configuration context. Axis2/C engine will pass it through, without
>> touching it.. Will it solve your problem?
>>
>> I think I am missing something here. Can you explain a bit more? Where
>> are you creating the token/connection pool and where are you using it?
>>
>> Regards,
>> Shankar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>



-- 
S.Uthaiyashankar
Senior Software Architect
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to