| Alisa Morse 2005-06-05, 5:45 pm |
| You are correct that the HATS entry servlet typically initializes the
runtime.
If you project is a "non HATS" web project or a "non HATS" EJB project, you
need to include the code from the Programmer's Guide:
http://publib.boulder.ibm.com/infoc...doc/pgcusio.htm
to initialize the runtime.
You should only have to initialize the runtime once. For example, you could
do it in
the init method of a servlet.
Thanks.
"David Smart" <dsmart@isi.com.au> wrote in message
news:d1db40$3df4$2@news.boulder.ibm.com...
> The HATS entry servlet is set to load on startup and seems to initialise
the
> runtime. So if our project is a HATS web project we don't seem to need to
> initialise the runtime. But what about a non-HATS web project? What if
we
> want to use integration object in our own (non-tool generated) web
> services - or making web services out of our own stateless session EJBs
that
> call IOs?
>
> There is a lack of clarity in the documentation about the initialisation
of
> the HATS runtime, be it in the EJB container, or the Web.
>
> Can someone make it clear how the initialisation should work. We are
trying
> to workout the best implementation for using our own custom web services
> that have to call integration objects.
>
> Do we use static code in the class to initialise the HATS runtime once?
>
> What happens if two calls try to initialise the runtime?
>
> Do we initialise it on every call?
>
> If so, that's a bit expensive isn't it?
>
>
> "KBDRand" <kbdrand@hotmail.com> wrote in message
> news:cn349j$59kk$1@news.boulder.ibm.com...
I[vbcol=seagreen]
or[vbcol=seagreen]
for[vbcol=seagreen]
IO.[vbcol=seagreen]
>
>
|