You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Samanth Athrey <sa...@yahoo.com> on 2001/12/06 06:10:36 UTC
turbine & weblogic
hi users,
am stuck in here pretty badly. i tried everything possible to start my
turbine sample application in weblogic. but could not. could anybody help me
pls or if u could tell me where to look for. it would be great help.
am using weblogic 5.1 with sp 8.
thanx in advance
Samanth
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
----- Original Message -----
From: Daniel Rall <dl...@finemaltcoding.com>
To: Turbine Users List <tu...@jakarta.apache.org>
Cc: Kelvin Tan <ke...@relevanz.com>
Sent: Thursday, December 13, 2001 8:56 AM
Subject: Re: [Fulcrum] Services hashtable
> Daniel Rall <dl...@finemaltcoding.com> writes:
>
> > Though I don't know the original reasoning, I would assume the two
> > hash lookups before using Class.forName() are there to avoid a race
> > condition where another instance of BaseServiceBroker (BSB) had its
> > getServiceInstance() method called with the same parameter and manages
> > to sneak in and create the service instance in between our two
> > lookups.
>
> Excuse me, I didn't mean another instace of, but rather another
> reference to the same BaseServiceBroker instance.
hhmmmm...ok
I'll go ahead without the second hash lookup, and will report if any
problems encountered.
Kelvin
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Daniel Rall <dl...@finemaltcoding.com> writes:
> Though I don't know the original reasoning, I would assume the two
> hash lookups before using Class.forName() are there to avoid a race
> condition where another instance of BaseServiceBroker (BSB) had its
> getServiceInstance() method called with the same parameter and manages
> to sneak in and create the service instance in between our two
> lookups.
Excuse me, I didn't mean another instace of, but rather another
reference to the same BaseServiceBroker instance.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Kelvin Tan" <ke...@relevanz.com> writes:
> I submitted a patch a couple of days back, but it kinda fixed only what
> needed fixing (shutdown mechanism), not the code clean-up.
Sorry, I missed that patch.
> getServiceInstance(String name) attempts to retrieve a service by
> services.get(name), failing which, it retrieves the classname from mapping
> and then tries services.get(className)?
>
> I don't see how it is possible that services.get(className) will return the
> services in any scenario, so I actually skipped the checking stage and
> directly went for Class.forName(className).newInstance().
>
> Am I missing something here?
Though I don't know the original reasoning, I would assume the two
hash lookups before using Class.forName() are there to avoid a race
condition where another instance of BaseServiceBroker (BSB) had its
getServiceInstance() method called with the same parameter and manages
to sneak in and create the service instance in between our two
lookups.
Anyhow, after the second hash check, the Service implementation is
instantiated, setup, and added to the services hash (keyed by name).
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
Thanks Daniel.
I submitted a patch a couple of days back, but it kinda fixed only what
needed fixing (shutdown mechanism), not the code clean-up.
One question.
getServiceInstance(String name) attempts to retrieve a service by
services.get(name), failing which, it retrieves the classname from mapping
and then tries services.get(className)?
I don't see how it is possible that services.get(className) will return the
services in any scenario, so I actually skipped the checking stage and
directly went for Class.forName(className).newInstance().
Am I missing something here?
Kelvin
----- Original Message -----
From: Daniel Rall <dl...@finemaltcoding.com>
To: Turbine Users List <tu...@jakarta.apache.org>
Cc: Kelvin Tan <ke...@relevanz.com>
Sent: Wednesday, December 12, 2001 4:56 PM
Subject: Re: [Fulcrum] Services hashtable
> "Kelvin Tan" <ke...@relevanz.com> writes:
>
> > From: Jason van Zyl <jv...@zenplex.com>
> >
> >> When the services were decoupled from fulcrum I started cleaning up the
> >> service code but it still needs work. It is somewhat confusing, we
know.
> >>
> >> Bottom line is that you get hold of the service by its name and not
> >> the classname. Those methods that refer to getting a service by
> >> classname should be made protected because they aren't used outside
> >> the service broker.
> >
> > Sure, and because I'm only using the framework (base classes and
> > interfaces), I hope I can help with the cleaning.
> >
> > I experienced trouble shutting down, even though initialization was
fine.
> > The problem was that shutdownService(String serviceName) obtains the
> > service's classname via the mapping hashtable, then proceeds to call
> > shutdownClass(String className). This doesn't work because
shutdownClass()
> > ...
> > Service service = getServiceInstance(className);
> >
> > attempts to retrieve the service from the services hashtable which
actually
> > maps according to serviceName:service.
> >
> > Moving the shutdown code to shutdownService() itself or changing the
mapping
> > to className:service fixed the problem.
>
> Hi Kelvin. I refactored BaseServiceBroker to use service name
> vs. class names consistantly, and in the process corrected the
> shutdown mechanism.
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Kelvin Tan" <ke...@relevanz.com> writes:
> From: Jason van Zyl <jv...@zenplex.com>
>
>> When the services were decoupled from fulcrum I started cleaning up the
>> service code but it still needs work. It is somewhat confusing, we know.
>>
>> Bottom line is that you get hold of the service by its name and not
>> the classname. Those methods that refer to getting a service by
>> classname should be made protected because they aren't used outside
>> the service broker.
>
> Sure, and because I'm only using the framework (base classes and
> interfaces), I hope I can help with the cleaning.
>
> I experienced trouble shutting down, even though initialization was fine.
> The problem was that shutdownService(String serviceName) obtains the
> service's classname via the mapping hashtable, then proceeds to call
> shutdownClass(String className). This doesn't work because shutdownClass()
> ...
> Service service = getServiceInstance(className);
>
> attempts to retrieve the service from the services hashtable which actually
> maps according to serviceName:service.
>
> Moving the shutdown code to shutdownService() itself or changing the mapping
> to className:service fixed the problem.
Hi Kelvin. I refactored BaseServiceBroker to use service name
vs. class names consistantly, and in the process corrected the
shutdown mechanism.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/8/01 2:18 AM, "Kelvin Tan" <ke...@relevanz.com> wrote:
> Sorry. Here it is again.
>
Patch is applied, thanks again!
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/8/01 2:18 AM, "Kelvin Tan" <ke...@relevanz.com> wrote:
> Sorry. Here it is again.
>
> Thought it was ok to include it in the body since I've seen others do it. :)
It always seems to get wrapped on me, and you didn't need to send the
attachement to everyone on the list ;-)
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
Sorry. Here it is again.
Thought it was ok to include it in the body since I've seen others do it. :)
Kelvin
----- Original Message -----
From: Jason van Zyl <jv...@zenplex.com>
To: Turbine Users List <tu...@jakarta.apache.org>
Sent: Saturday, December 08, 2001 3:13 PM
Subject: Re: [Fulcrum] Services hashtable
> On 12/8/01 2:07 AM, "Kelvin Tan" <ke...@relevanz.com> wrote:
>
> Kelvin,
>
> Can you send me the patch as an attachment please.
>
> >
> >>>>
> >>>> Send the patch and I'll apply it :-)
> >>>
> >>> Sure thing. Should I deprecate shutdownClass in ServiceBroker and
> >>> BaseServiceBroker as well (since it's now handled by shutdownService)?
> >>
> >> I don't think your changes should interfere with anything and Fulcrum
is
> > not
> >> released so you don't have to deprecate anything.
> >>
> >
> > Here it is. I didn't remove shutdownClass in ServiceBroker though, but
it's
> > basically not in use anymore.
> >
> > Index: src/core/java/org/apache/fulcrum/BaseServiceBroker.java
> > ===================================================================
> > RCS file:
> >
/home/cvspublic/jakarta-turbine-fulcrum/src/core/java/org/apache/fulcrum/Bas
> > eServiceBroker.java,v
> > retrieving revision 1.10
> > diff -r1.10 BaseServiceBroker.java
> > 566,568c566
> > < String className = (String) mapping.get(name);
> > <
> > < if (className != null)
> > ---
> >> try
> > 570c568,581
> > < shutdownClass(className);
> > ---
> >> Service service = getServiceInstance(name);
> >> if (service.isInitialized())
> >> {
> >> service.shutdown();
> >> ((BaseService) service).setInit(false);
> >> }
> >> }
> >> catch (InstantiationException e)
> >> {
> >> // Shutdown of a nonexistent class was requested.
> >> // This does not hurt anything, so we log the error and
> > continue.
> >> error(new ServiceException(
> >> "Shutdown of a nonexistent service " + name +
> >> " was requested", e));
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
Re: [Fulcrum] Services hashtable
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/8/01 2:07 AM, "Kelvin Tan" <ke...@relevanz.com> wrote:
Kelvin,
Can you send me the patch as an attachment please.
>
>>>>
>>>> Send the patch and I'll apply it :-)
>>>
>>> Sure thing. Should I deprecate shutdownClass in ServiceBroker and
>>> BaseServiceBroker as well (since it's now handled by shutdownService)?
>>
>> I don't think your changes should interfere with anything and Fulcrum is
> not
>> released so you don't have to deprecate anything.
>>
>
> Here it is. I didn't remove shutdownClass in ServiceBroker though, but it's
> basically not in use anymore.
>
> Index: src/core/java/org/apache/fulcrum/BaseServiceBroker.java
> ===================================================================
> RCS file:
> /home/cvspublic/jakarta-turbine-fulcrum/src/core/java/org/apache/fulcrum/Bas
> eServiceBroker.java,v
> retrieving revision 1.10
> diff -r1.10 BaseServiceBroker.java
> 566,568c566
> < String className = (String) mapping.get(name);
> <
> < if (className != null)
> ---
>> try
> 570c568,581
> < shutdownClass(className);
> ---
>> Service service = getServiceInstance(name);
>> if (service.isInitialized())
>> {
>> service.shutdown();
>> ((BaseService) service).setInit(false);
>> }
>> }
>> catch (InstantiationException e)
>> {
>> // Shutdown of a nonexistent class was requested.
>> // This does not hurt anything, so we log the error and
> continue.
>> error(new ServiceException(
>> "Shutdown of a nonexistent service " + name +
>> " was requested", e));
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
> >>
> >> Send the patch and I'll apply it :-)
> >
> > Sure thing. Should I deprecate shutdownClass in ServiceBroker and
> > BaseServiceBroker as well (since it's now handled by shutdownService)?
>
> I don't think your changes should interfere with anything and Fulcrum is
not
> released so you don't have to deprecate anything.
>
Here it is. I didn't remove shutdownClass in ServiceBroker though, but it's
basically not in use anymore.
Index: src/core/java/org/apache/fulcrum/BaseServiceBroker.java
===================================================================
RCS file:
/home/cvspublic/jakarta-turbine-fulcrum/src/core/java/org/apache/fulcrum/Bas
eServiceBroker.java,v
retrieving revision 1.10
diff -r1.10 BaseServiceBroker.java
566,568c566
< String className = (String) mapping.get(name);
<
< if (className != null)
---
> try
570c568,581
< shutdownClass(className);
---
> Service service = getServiceInstance(name);
> if (service.isInitialized())
> {
> service.shutdown();
> ((BaseService) service).setInit(false);
> }
> }
> catch (InstantiationException e)
> {
> // Shutdown of a nonexistent class was requested.
> // This does not hurt anything, so we log the error and
continue.
> error(new ServiceException(
> "Shutdown of a nonexistent service " + name +
> " was requested", e));
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/8/01 1:51 AM, "Kelvin Tan" <ke...@relevanz.com> wrote:
>
> ----- Original Message -----
> From: Jason van Zyl <jv...@zenplex.com>
> To: Turbine Users List <tu...@jakarta.apache.org>
> Sent: Saturday, December 08, 2001 2:24 PM
> Subject: Re: [Fulcrum] Services hashtable
>
>
>> On 12/7/01 10:49 PM, "Kelvin Tan" <ke...@relevanz.com> wrote:
>>
>>> attempts to retrieve the service from the services hashtable which
> actually
>>> maps according to serviceName:service.
>>>
>>> Moving the shutdown code to shutdownService() itself or changing the
> mapping
>>> to className:service fixed the problem.
>>
>> Send the patch and I'll apply it :-)
>
> Sure thing. Should I deprecate shutdownClass in ServiceBroker and
> BaseServiceBroker as well (since it's now handled by shutdownService)?
I don't think your changes should interfere with anything and Fulcrum is not
released so you don't have to deprecate anything.
> Kelvin
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
----- Original Message -----
From: Jason van Zyl <jv...@zenplex.com>
To: Turbine Users List <tu...@jakarta.apache.org>
Sent: Saturday, December 08, 2001 2:24 PM
Subject: Re: [Fulcrum] Services hashtable
> On 12/7/01 10:49 PM, "Kelvin Tan" <ke...@relevanz.com> wrote:
>
> > attempts to retrieve the service from the services hashtable which
actually
> > maps according to serviceName:service.
> >
> > Moving the shutdown code to shutdownService() itself or changing the
mapping
> > to className:service fixed the problem.
>
> Send the patch and I'll apply it :-)
Sure thing. Should I deprecate shutdownClass in ServiceBroker and
BaseServiceBroker as well (since it's now handled by shutdownService)?
Kelvin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/7/01 10:49 PM, "Kelvin Tan" <ke...@relevanz.com> wrote:
> attempts to retrieve the service from the services hashtable which actually
> maps according to serviceName:service.
>
> Moving the shutdown code to shutdownService() itself or changing the mapping
> to className:service fixed the problem.
Send the patch and I'll apply it :-)
> Kelvin
>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
----- Original Message -----
From: Jason van Zyl <jv...@zenplex.com>
To: Turbine Users List <tu...@jakarta.apache.org>
Sent: Saturday, December 08, 2001 11:23 AM
Subject: Re: [Fulcrum] Services hashtable
> On 12/7/01 9:55 PM, "Kelvin Tan" <ke...@relevanz.com> wrote:
>
> > Sorry for the repost, but no response to this, so I thought I'd try
again.
> > Maybe this belongs to Turbine-Dev though...
> >
>
> When the services were decoupled from fulcrum I started cleaning up the
> service code but it still needs work. It is somewhat confusing, we know.
>
> Bottom line is that you get hold of the service by its name and not the
> classname. Those methods that refer to getting a service by classname
should
> be made protected because they aren't used outside the service broker.
>
Sure, and because I'm only using the framework (base classes and
interfaces), I hope I can help with the cleaning.
I experienced trouble shutting down, even though initialization was fine.
The problem was that shutdownService(String serviceName) obtains the
service's classname via the mapping hashtable, then proceeds to call
shutdownClass(String className). This doesn't work because shutdownClass()
...
Service service = getServiceInstance(className);
attempts to retrieve the service from the services hashtable which actually
maps according to serviceName:service.
Moving the shutdown code to shutdownService() itself or changing the mapping
to className:service fixed the problem.
Kelvin
> >> In BaseServiceBroker, how are the services supposed to be stored in the
> >> Services hashtable?
> >>
> >> services.put(name, service) or services.put(className, service) ?
> >>
> >> Within getServiceInstance(String name),
> >>
> >> service.setServiceBroker(this);
> >> service.setName(name);
> >> services.put(name, service);
> >>
> >> But there's code elsewhere which attempts to retrieve the service by
> >> classname...
> >>
> >> Kelvin
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> >> For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >>
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Jason van Zyl <jv...@zenplex.com>.
On 12/7/01 9:55 PM, "Kelvin Tan" <ke...@relevanz.com> wrote:
> Sorry for the repost, but no response to this, so I thought I'd try again.
> Maybe this belongs to Turbine-Dev though...
>
When the services were decoupled from fulcrum I started cleaning up the
service code but it still needs work. It is somewhat confusing, we know.
Bottom line is that you get hold of the service by its name and not the
classname. Those methods that refer to getting a service by classname should
be made protected because they aren't used outside the service broker.
>> In BaseServiceBroker, how are the services supposed to be stored in the
>> Services hashtable?
>>
>> services.put(name, service) or services.put(className, service) ?
>>
>> Within getServiceInstance(String name),
>>
>> service.setServiceBroker(this);
>> service.setName(name);
>> services.put(name, service);
>>
>> But there's code elsewhere which attempts to retrieve the service by
>> classname...
>>
>> Kelvin
>>
>>
>> --
>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
Sorry for the repost, but no response to this, so I thought I'd try again.
Maybe this belongs to Turbine-Dev though...
This was found in the CVS version checked out on Dec 6. Checked again today
and no changes to that.
Kelvin
----- Original Message -----
From: Kelvin Tan <ke...@relevanz.com>
To: Turbine Users List <tu...@jakarta.apache.org>
Sent: Thursday, December 06, 2001 3:04 PM
Subject: [Fulcrum] Services hashtable
> In BaseServiceBroker, how are the services supposed to be stored in the
> Services hashtable?
>
> services.put(name, service) or services.put(className, service) ?
>
> Within getServiceInstance(String name),
>
> service.setServiceBroker(this);
> service.setName(name);
> services.put(name, service);
>
> But there's code elsewhere which attempts to retrieve the service by
> classname...
>
> Kelvin
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
[Fulcrum] Services hashtable
Posted by Kelvin Tan <ke...@relevanz.com>.
In BaseServiceBroker, how are the services supposed to be stored in the
Services hashtable?
services.put(name, service) or services.put(className, service) ?
Within getServiceInstance(String name),
service.setServiceBroker(this);
service.setName(name);
services.put(name, service);
But there's code elsewhere which attempts to retrieve the service by
classname...
Kelvin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: turbine & weblogic
Posted by Samanth Athrey <sa...@yahoo.com>.
> Have you tried with an ordinary Servlet Engine like Tomcat first??
Yes. I have tried with Tomcat 4.0.1 and it works. Thanx for the help. I
shall try this out too.
Regards
Samanth V Athrey
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: turbine & weblogic
Posted by Kasper Nielsen <ne...@kav.dk>.
Have you tried with an ordinary Servlet Engine like Tomcat first??
I've been unable to start anything in Weblogic (6.2) if I didn't specify a
Servlet-Mapping in web.xml, which the TDK dosn't specify as default
like this inside your <servlet> tags.
<servlet-mapping>
<servlet-name>catalog</servlet-name>
<url-pattern>/catalog</url-pattern>
</servlet-mapping>
- Kasper
----- Original Message -----
From: "Samanth Athrey" <sa...@yahoo.com>
To: "Turbine-User" <tu...@jakarta.apache.org>
Sent: Thursday, December 06, 2001 6:10 AM
Subject: turbine & weblogic
> hi users,
>
> am stuck in here pretty badly. i tried everything possible to start my
> turbine sample application in weblogic. but could not. could anybody help
me
> pls or if u could tell me where to look for. it would be great help.
>
> am using weblogic 5.1 with sp 8.
>
> thanx in advance
> Samanth
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: turbine & weblogic
Posted by "Dan E." <ey...@db.erau.edu>.
I am working the same problem next week. I will let you know if I get
anywhere with it.
Dan Eyassu
On Thu, 6 Dec 2001, Samanth Athrey wrote:
> hi users,
>
> am stuck in here pretty badly. i tried everything possible to start my
> turbine sample application in weblogic. but could not. could anybody help me
> pls or if u could tell me where to look for. it would be great help.
>
> am using weblogic 5.1 with sp 8.
>
> thanx in advance
> Samanth
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: turbine & weblogic
Posted by "Dan E." <ey...@db.erau.edu>.
One thing I suggest is that you define the weblogic classpath properly so
that it can find all of the JARs from TDK.
Dan Eyassu
On Thu, 6 Dec 2001, Samanth Athrey wrote:
> hi users,
>
> am stuck in here pretty badly. i tried everything possible to start my
> turbine sample application in weblogic. but could not. could anybody help me
> pls or if u could tell me where to look for. it would be great help.
>
> am using weblogic 5.1 with sp 8.
>
> thanx in advance
> Samanth
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>