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

[Design of JBoss Remoting, Unified Invokers] - Re: Duplicate mbean removal

by scott.stark＠jboss.org

Service lifecycle is independent of existence as an mbean. There still is not enough code here for me to understand what the invoker/connector relationship is. It looks like registration and the jboss service lifecycle are being mixed up here. The question is, what is actually creating the invoker mbean, the Connector? You can cycle an mbean service through start, stop, start and this should have no impact on whether the service exists as an mbean. The only time a service should be registering an mbean is if its acting as a container that fully owns the mbean; meaning its not exposed to the jboss service deployment layer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098563#4098563 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098563

17 years, 2 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Duplicate mbean removal

by ron.sigal＠jboss.com

This is related to changes I made for JBREM-747 "org.jboss.remoting.transport.Connector should unregister server invoker from MBeanServer". Connector.init(), which is called from Connector.create(), used to have the code | ObjectName objName = new ObjectName(invoker.getMBeanObjectName()); | if (!server.isRegistered(objName)) | { | server.registerMBean(invoker, objName); | invoker.setMBeanServer(server); | } | The problem was that when a Connector stops and restarts, it sees that it's already registered, doesn't pass the MBeanServer to the invoker, and the invoker is unable to see other MBeans. So I changed it to | ObjectName objName = new ObjectName(invoker.getMBeanObjectName()); | if (!server.isRegistered(objName)) | { | server.registerMBean(invoker, objName); | } | else | { | log.warn(objName + " is already registered with MBeanServer"); | } | invoker.setMBeanServer(server); | I also added | if (server != null) | { | try | { | ObjectName objName = new ObjectName(invoker.getMBeanObjectName()); | server.unregisterMBean(objName); | } | catch (Exception e) | { | log.error("invalid Object Name", e); | } | } | to Connector.stop(). I'm confused. Judging from the original code, Connector clearly expects to register itself. And since Connector is registering itself, I thought it should also unregister itself. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098555#4098555 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098555

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-4890:EJBAccessException: Caller unauthorized

by anil.saldhana＠jboss.com

"scott.stark(a)jboss.org" wrote : That was what my TODO question was about. Yeah, we still push a null runas (as per my latest change). Wonder why u pushed an "anonymous", rather than a null? RunAs takes preference in authorization and programmatic security (isUserxxx. isCallerXXX, getCallerP). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098550#4098550 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098550

17 years, 2 months

1
0
0 / 0

[Design of JBoss Build System] - Repository Cleanup

by pgier

This is just a notice that I'm doing some maven repository cleanup, and I'm going to remove any snapshot versions of projects that I see in the jboss maven repository (http://repository.jboss.org/maven2). Snapshot versions should only be deployed to the snapshot repository (http://snapshots.jboss.org/maven2). If this causes problems for anyone please let me know and I will help to find a solution to the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098548#4098548 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098548

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: QName unmarshalling

by alex.loubyansky＠jboss.com

It's fixed in XB trunk. I haven't updated the snapshot repository. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098546#4098546 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098546

17 years, 2 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: Generate SSOID in WebAuthentication

by anil.saldhana＠jboss.com

Remy, thanks for making the visibility access changes needed for bringing in the SingleSignOn aspect into Programmatic Web Authentication. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098545#4098545 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098545

17 years, 2 months

1
0
0 / 0

[Design of JBoss Serialization] - Interop sanity check

by dennisbyrne

We can do this, right? JBossOutputStream on JVM for vendor 1 -> JBossInputStream on JVM for vendor 2 And this holds true regardless of whether the serialVersionUID is specified in code? In other words, JBoss serialization has *nothing* to do w/ the serialization algorithm on the JVM from which it is running in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098543#4098543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098543

17 years, 2 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: SingleSignOn method visibility change

by anil.saldhana＠jboss.com

Those changes were made as part of bringing in the SingleSignOn capabilities to Programmatic Web Authentication. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098542#4098542 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098542

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: QName unmarshalling

by alex.loubyansky＠jboss.com

This is fixed now. The test still fails for other reasons. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098541#4098541 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098541

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-4890:EJBAccessException: Caller unauthorized

by scott.stark＠jboss.org

That was what my TODO question was about. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098540#4098540 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098540

17 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2007