January 2007 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: bean/mbean integration issue

by alesj

"adrian(a)jboss.org" wrote : "alesj" wrote : "adrian(a)jboss.org" wrote : This interface belongs in the dependency module that knows nothing about POJOs/services. | | | | | Where in the Context hierarchy should I put it? | | | | It's upto each implementation whether it implements it. | I did make it to extend ControllerContext. I need the target and I thought I needed name. Should I make it plain 'standalone'? I also added getClassLoader() method - to help me with getting the param TypeInfos. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002836#4002836 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002836

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: bean/mbean integration issue

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : This interface belongs in the dependency module that knows nothing about POJOs/services. | | | | Where in the Context hierarchy should I put it? | It's upto each implementation whether it implements it. anonymous wrote : | Should KernelRegistryEntry extend it? | If so, how do we handle KernelRegistryPlugin entries? You could make BasicKernelRegistryEntry implement it. But you'd need a mechanism to get the BeanInfo for the target object of the entry. I'm not sure it is worth the effort? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002826#4002826 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002826

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Plan to improve CMS integration

by julien＠jboss.com

normally, the portal-cms.sar will be nested in jboss-portal.sar so the problem will not exist (coordinated by the build system once all artifacts have been created) I agree that for development we have to find a way to make it more usable. "roy.russo(a)jboss.com" wrote : There are problem with the core-cms: | | 1. You *must* deploy the jboss-portal.sar first, and then the portal-cms.sar. If you do not, the cms will not deploy at all, due to some issues with security/identity. | | 2. If you deploy the portal-cms.sar in a running instance of AS, it will create all the resources. | a. File creation is sloooooow. | b. Also, when you log in to the cmsAdminPortlet, it doesn't show the root directory so you can't do anything. I wouldn't be surprised if this is also related to identity integration. | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002794#4002794 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002794

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Fine grained action aware interfaces (JBMICROCONT-134)

by alesj

Where do you see the problem? What I meant was that if you need to be notified of the exact state (implementing multiple KCCAware interfaces) when the awareness happens, the same method is always called, and you must look into the context to figure out what the current state is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002791#4002791 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002791

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Fine grained action aware interfaces (JBMICROCONT-134)

by bkeh12

Hi,adrian Where are you ? alesj wrote : Currently all interfaces extend KernelControllerContextAware, which is convenient for simple awareness, but might not be that useful in all cases. Do you agree this! Can talk to us, please. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002778#4002778 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002778

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean definition as value add problem (JBMICROCONT-28)

by scott.stark＠jboss.org

support for javabean ctors is working: | <javabean xmlns="urn:jboss:javabean:2.0" | class="org.jboss.test.javabean.support.SimpleBean"> |  | <constructor> |  | <property name="anObject">anObjectValue</property> | <property name="AString">StringValue</property> | <property name="AByte">12</property> | <property name="ABoolean">true</property> | <property name="ACharacter">x</property> | <property name="AShort">123</property> | <property name="anInt">1234</property> | <property name="ALong">12345</property> | <property name="AFloat">3.14</property> | <property name="ADouble">3.14e12</property> | <property name="ADate">Jan 01 00:00:00 CET 2001</property> | <property name="ABigDecimal">12e4</property> | <property name="ABigInteger">123456</property> | <property name="abyte">12</property> | <property name="aboolean">true</property> | <property name="achar">y</property> | <property name="ashort">123</property> | <property name="anint">1234</property> | <property name="along">12345</property> | <property name="afloat">3.14</property> | <property name="adouble">3.14e12</property> | <property name="ANumber" class="java.lang.Long">12345</property> | <property name="overloadedProperty">StringValue</property> | <property name="XYZ">XYZ</property> | <property name="abc">abc</property> | </constructor> | </javabean> | I'm not able to check these changes in currently though as svn seems to still be down from the upgrade effort. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002672#4002672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002672

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

"clebert.suconic(a)jboss.com" wrote : Well.. I could replicate this in a testcase.. so it is a problem. | | | You have Server1, Server2, and Server3 | | Then you have a map: | | 1->2 | 2->3 | 3->1 | | Now you kill server1: | | Map now is: | | 2->3 | 3>2 | | You don't have 1 on the MAP. | | When a connection on server1 fails.. it won't find an ID on failoverMAP. I could replicate this on a testcase. Surely you shouldn't update the failover map after node failure until all connections have failed over from the old server? Then you can prevent this "race condition" from happening in the first place? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002660#4002660 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002660

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

Clebert - I am somewhat baffled about the approach you are taking here. Can you try and describe it clearly (and slowly) so I can understand it? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002655#4002655 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002655

19 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Detached invokers are too detached from the transport

by ron.sigal＠jboss.com

I have implemented a version of the solution I suggested above and checked it in to the Remoting HEAD and remoting_2_x branches. 1. There are a couple of changes. First, the listener interface, org.jboss.remoting.socketfactory.SocketCreationListener, is | public interface SocketCreationListener | { | /** | * Called when a socket has been created. | * | * @param socket socket that has been created | * @param source SocketFactory or ServerSocket that created the socket | * @throws IOException | */ | void socketCreated(Socket socket, Object source) throws IOException; | } | and there are two distinct configuration keys for incorporating listeners into socket factories and server sockets: org.jboss.Remoting.SOCKET_CREATION_CLIENT_LISTENER (with value "socketCreationClientListener") and org.jboss.Remoting.SOCKET_CREATION_SERVER_LISTENER (with value "socketCreationServerListener") The reason for distinguishing these is that the same configuration Map can get passed to both a server and a client. For example, it could be passed to a Connector and then later to a Client used by the Connector to push callbacks. Finally, to support configuration by InvokerLocator or xml, the value of the listener parameter can be the name of a class that implements SocketCreationListener and has a default constructor. 2. The solution works for the following transports: bisocket, sslbisocket, https, multiplex, sslmultiplex, rmi, sslrmi, socket, and sslsocket. It does not work for the http transport and for the server side of the servlet transport. The reason it doesn't work for http is that HttpURLConnection does not expose its socket factory (though HttpsURLConnection does). It should be possible to write a custom http protocol handler for this purpose, but I won't unless is there is a specific request. And invocations with the servlet transport go through a servlet container, which is outside the scope of Remoting. 3. The implementation is based on the classes: CreationListenerSocketFactory, CreationListenerServerSocketFactory, and CreationListenerServerSocket in the package org.jboss.remoting.socketfactory. CreationListenerSocketFactory wraps the SocketFactory that would otherwise be used, and calls the listener whenever a socket is created. CreationListenerServerSocketFactory wraps the ServerSocketFactory that would otherwise be used, and whenever a ServerSocket is created, it wraps that ServerSocket in a CreationListenerServerSocket, which calls the listener whenever it creates a socket. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002613#4002613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002613

19 years, 2 months

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Tracing what happens before EARDeployer starts

by SmokingAPipe

And the problem is solved. One of the applications on the server was misbehaving and somehow disabling the entire logging system and System.out globally. It would be nice if JBoss would somehow block that from happening or at least intercept it and log a warning, but anyway, it's the fault of the web app. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002609#4002609 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002609

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007