[JBoss Microcontainer Development] New message: "Re: Activating OnDemand beans from child controller"
by Kabir Khan
User development,
A new message was posted in the thread "Activating OnDemand beans from child controller":
http://community.jboss.org/message/520261#520261
Author : Kabir Khan
Profile : http://community.jboss.org/people/kabir.khan@jboss.com
Message:
--------------------------------------------------------------
> mailto:kabir.khan@jboss.com wrote:
>
> Fixing http://lists.jboss.org/pipermail/jboss-development/2010-January/015434.html I am adding a ScopedOnDemandDependencyTestCase (extends OnDemandDependencyTestCase similar to (Scoped)DuplicateAliasTestCase), but have found a deeper problem. If an OnDemand bean is installed in the main controller and is depended on by a bean in a child controller the OnDemand bean never gets activated and the child controller bean's dependency never resolved.
> I install Bean1 with OnDemand, goes to Describe state
> I install scoped Bean2 with Automatic and a dependency on Bean1, goes to Instantiated state fine
>
> When trying to move Bean2 to Configured state it does not resolve for the following reasons:
> When enabling ondemand beans in AbstractDependencyItem.resolve(), it was looking at the wrong controller, I changed:
>
> *if* (unresolvedContext != *null* && ControllerMode.ON_DEMAND.equals(unresolvedContext.getMode()))
> {
> *try*
> {
> controller.enableOnDemand(unresolvedContext);
>
>
>
>
> to
>
>
> *if* (unresolvedContext != *null* && ControllerMode.ON_DEMAND.equals(unresolvedContext.getMode()))
> {
> *try*
> {
> unresolvedContext.getController().enableOnDemand(unresolvedContext);
>
>
>
>
>
>
> Now Bean1 correctly gets its requiredState set to INSTALLED. Unfortunately this is not enough.
>
>
>
> In the normal/unscoped mode the mechanism is that AbstractDI.resolve() returns false, and we end up back in the resolveContexts() loop which finds Bean1 is not in its requiredState (INSTALLED).
>
>
>
> In the scoped test, it does not get picked up since Bean2 was installed in the scoped controller whose resolveContexts() does not involve the main controller so Bean1 is never found.
>
>
>
> I'll see if I can fix this
>
>
After a trying a few different things what I have now is.
-Leaving DependencyItem as is
-Modifying AbstractController.enableOnDemand() to set onDemandEnabled for the initiating controller (i.e. scoped in this case) and also for the controller the OnDemand context actually belongs to.
-Modifying the AbstractController.resolveContexts() loop to record if onDemandEnabled was true, and if it was when finishing the loop to call resolveContexts() on the parent controller.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/520261#520261
16 years, 3 months
[jBPM] New message: "Re: TaskService issue"
by Tej jbpm
User development,
A new message was posted in the thread "TaskService issue":
http://community.jboss.org/message/520252#520252
Author : Tej jbpm
Profile : http://community.jboss.org/people/tejJBPM
Message:
--------------------------------------------------------------
Hi Santanu
Thanks for the reply.
I am using a transaction manager and it is my hiberate which is doing the talking with the database.
Here is my config. Do you see anything wrong with this? Do I have to declare any additional params for cleanup.. Thanks in advance
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE hibernate-configuration PUBLIC
"-//Hibernate/Hibernate Configuration DTD 3.0//EN"
"http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"><hibernate-configuration>
<session-factory>
<hibernate-configuration
<property name="hibernate.dialect">org.hibernate.dialect.MySQLInnoDBDialect</property>
<property name="hibernate.connection.driver_class">com.mysql.jdbc.Driver</property>
<property name="hibernate.connection.url">jdbc:mysql://localhost/mydb</property>
<property name="hibernate.connection.username">username</property>
<property name="hibernate.connection.password">password</property>
<property name="hibernate.format_sql">true</property>
<mapping resource="jbpm.repository.hbm.xml" />
<mapping resource="jbpm.execution.hbm.xml" />
<mapping resource="jbpm.history.hbm.xml" />
<mapping resource="jbpm.task.hbm.xml" />
<mapping resource="jbpm.identity.hbm.xml" />
</session-factory>
</hibernate-configuration>
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/520252#520252
16 years, 3 months
getting rid of ssl authentication asked by second server in load balanced mode...
by Neha Mehta
Hi,
I have successfully load balanced jboss (version 4.2.2) servers using apache http server(version 2.2).
But when the load balancer switches client request from one server to another(as they are in load balanced mode), the second server also asks for ssl authentication and relogin. Say client has placed a request that is served by server1. SSL authentication is done by the server.Then again when client requests, within the same browser session the load balancer redirects the request to server2, now server2 asks for ssl authentication again. I want to get rid of this ssl authentication, the second time. Once both the servers get ssl authentication, then switching of requests between both the servers and session replication is being handled properly.
Is there any way, that the second server does not ask for ssl authentication,when request for the same client are being served by both the servers in load balanced mode???
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Thanks & Regards,
Neha Mehta
Innovation Group - L&T Infotech | Mumbai
Contact : 02267954324 | Mob: 9769472267
[cid:image002.jpg@01CA95F0.29000FC0]<http://www.lntinfotech.com/>
________________________________
This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
______________________________________________________________________
16 years, 3 months