Hi,

since I made a new build this week I have problems with components which are marked as singletons in the xtype-file
but get instantiated serveral times.


my setup is the following:

<block>

 <info>
   <name>proxy-server</name>
 </info>

<implementation>
<engine>
<classpath>
<fileset dir="../common/lib/common/jentro">
<include name="com.jentro.http.jar"/> </fileset>
</classpath>
</engine>


<categories name="proxy" priority="INFO" target="log"/>

    <component name="http-server"
     class="com.jentro.http.components.impl.HttpServiceImpl">

<categories priority="INFO" />

<configuration>
<port>4848</port>
</configuration>
</component>


  . . . .
  . . . .

<container name="delegator">
<engine>
<classpath>
<fileset dir="../navigation/lib/jentro">
<include name="guidance.jar"/> </fileset>
<fileset dir="dist">
<include name="proxy.server.jar"/> </fileset>
</classpath>
</engine>
<categories name="delegator" priority="INFO" target="log"/>


<component name="find-proxy-ip"
class="com.jentro.manager.proxy.client.server.FindProxyIPComposer"
activation="startup"/>
</container>
. . . .


</block>


this configuration starts fine and works correct. but if I an add attribute
activation="startup"
to the "http-server" component than at time of instanciating the "find-proxy-ip" component I get an "address already in use"-exception, because a second instance of the "http-server" is created :-(
the old build I use the last 2-3 weeks worked fine. so the question is moreless: is this a bug or a feature ? for me the activation attribute shouldn't have any effect on the singleton attribute. the effect I have when I deploy more than one of these Composer (all different types).


I have another place where I end up with to many different instances of singletons, but before digging into that I wanted to find out, if I understand the concept of singleton within the container hierachy of a block correctly.

with best wishes Kristian





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



Reply via email to