Hi Justin,

thanks for your reply. Yes, there is a method getRegistry() - but it requires the RequestContext as parameter. I don't have access to it :(

-andi



On Jul 11, 2005, at 14:45 Uhr, Stanczak Group wrote:

Look at the filter class it's self. There's a static method to get the
registry from the servlet request.

Andreas Aderhold wrote:


Hi,

I'm pretty new to HiveMind and setup a some services today (basically
following the article on tss) using hibernate + interceptors. I like
it very much, it's simple and easy. Everything works fine on
commandline. Now i want to access the services from a web-framework
and registered the filter provided by hivemind in the web.xml. so far
so good.

but how do i obtain the registry from inside my webapp?

in spring i could just get the application context by a static
lookup. i found nothing similar in HiveMind. Using RegistryBuilder is
way to expensive (builds up everything on each request, uahh). I only
need the registry build exactly one time (at deploy) and shutdown on
un-deploy.

I excpected to find something static like HiveMind.getRegistry() to
obtain a reference to the built up registry or even
HiveMind.getService(..). But i can't find anything like that. I know
that the filter puts the registry on the request context, but I don't
have access to it.

hints or directions where to look?

thanks
andi


PS: why did SDL have to go?? i find it much more readable than xml :/
any chance for a comeback?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: hivemind-user- [EMAIL PROTECTED]




--
Justin Stanczak
Stanczak Group
812-735-3600

"All that is necessary for the triumph of evil is that good men do nothing."
Edmund Burke

..________...............__.................
./  _____/..____..._____/..|_..____...____....
/...\..____/.__.\./....\...__\/.._.\./._..\....
\....\_\..\..___/|...|..\..|.(..<_>.|.<_>..)....
.\______../\___.._\__|../__|..\____/.\____/......
........\/.....\/.....\/..........................


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to