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

[Design the new POJO MicroContainer] - Deployer ClassLoader dependencies and OSGi

by adrian＠jboss.org

For the "version" of a deployment/module I'm currently using the OSGi version class. See deployers-structure-spi/org.jboss.deployers.structure.spi.classloading.helpers.VersionImpl Doing this will make it easier to interoperate with OSGi in the future, but it does introduce a dependency of the OSGi core jar into the bootstrap classloader. Can anybody think of alternate way to do this? The basic problem is if we want multiple Version implementations then they will like have to understand each other to implement: | Comparator<Version>.compareTo(Version other) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071188#4071188 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071188

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Alias status inside Controller

by alesj

Is this a valid method on Controller? | /** | * Get the alias status. | * | * not present : Not_Installed | * pending: Start | * installed : Installed | * | * @param alias the alias | * @return status | */ | ControllerState getAliasStatus(Object alias); | Since it hides the alias impl details (lookup of Context with this name: alias + "_Alias"). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071186#4071186 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071186

18 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - EJB3 SPI for WS

by thomas.diesler＠jboss.com

Hi Carlo, please pull in | https://svn.jboss.org/repos/jbossws/container | there you find the integration layers for AS40, AS42, AS50 This code will eventually end up in the AS code base or the respective projects. For example the EJB3 invokers should be part of the EJB project and only have a dependency on the JBossWS SPI. It should be transparent to the invoker what stack there is deplyed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071148#4071148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071148

18 years, 8 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Failure handling

by bill.burke＠jboss.com

For JBoss at least, the retry count is configured at the MDB level. You pass it in as container configuration or as an activation property. Felt like writing about this here: http://bill.burkecentral.com/2007/08/06/guaranteed-jbpm-failure-handling/ I discussed why the Synchronization approach wouldn't work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071135#4071135 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071135

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Missing BeanFactory with no class usage

by alesj

"alesj" wrote : I guess we never tested this - beanfactory having no class/bean set. | Since this code woudn't work then. ;-) | | | public Object createBean() throws Throwable | | { | | ClassLoader cl = Configurator.getClassLoader(classLoader); | | BeanInfo info = configurator.getBeanInfo(bean, cl); | | | I've added this fix | public Object createBean() throws Throwable | { | ClassLoader cl = Configurator.getClassLoader(classLoader); | BeanInfo info = null; | if (bean != null) | info = configurator.getBeanInfo(bean, cl); | | Joinpoint joinpoint = configurator.getConstructorJoinPoint(info, constructor, null); | Object result = joinpoint.dispatch(); | if (info == null && result != null) | info = configurator.getBeanInfo(result.getClass()); | and also added tests that use constructor's factory + factoryMethod or factoryClass + factoryMethod. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071132#4071132 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071132

18 years, 8 months

1
0
0 / 0

[Design of JBoss Web Services] - JBossWS without EJB3 support

by thomas.diesler＠jboss.com

in jbossws.sar/META-INF/jboss-services.xml you comment out |  | in jbossws.sar/jbossws.beans/META-INF/jboss-services.xml you comment out | <bean name="WSApplicationMetaDataAdapterEJB3" ... --> | <bean name="WSSecurityHandlerEJB3" ... --> | <bean name="WSDeployerHook_JAXWS_EJB3" ... --> | basically everything ending with 'EJB3' I tried it out on jbossws-4.2.1.GA View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071091#4071091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071091

18 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Can not deploy helloworld portlet

by xhuang＠jboss.com

Did you see t"HelloWorldPortletInstance" in Portlet Instances Tab of Management Portlet? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071024#4071024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071024

18 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: User Portlet Discussion

by thomas.heute＠jboss.com

"Antoine_h" wrote : Hello, | | ******************** | Ordering the view of users, or roles. | ******************** | Makes sense. "Antoine_h" wrote : | ******************** | configurable list of user | ******************** | Makes sense even more since the list of attributes could be changed "Antoine_h" wrote : | ******************** | Multi selection screens, with action on the selected list. | ******************** | Makes sense as of today, but this would somehow duplicate the notion of group that will probably happen in the identity service "Antoine_h" wrote : | ******************** | Logged in users | ******************** | I was more seeing this as an additional portlet. "Antoine_h" wrote : | ******************** | Packaging the user stuff appart | ******************** | a separate packaging for the user/role gui admin | The initial idea is to "move" this to the core-admin module (where the admin portlet leaves, after refactoring). I was thinking of a core-identity module instead, both solutions have advantages and drawbacks. But this will definitely move away the core module. "Antoine_h" wrote : | a separate packaging for the identity services (this is not gui, but this is important too). | It is already the case in 2.6 (module called "identity") "Antoine_h" wrote : | ******************** | RichFaces ? | ******************** | I guess Emanuel will use anything he may need and is ready to use. But this is not a sample portlet so the goal is not to use a particular technology for the sake of using it. Thanks a lot for the feedback and the new ideas to keep in mind. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070987#4070987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070987

18 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: User Portlet Discussion

by anders3

"thomas.heute(a)jboss.com" wrote : | I find this quite offending since i already explained that to you. | Upgrading to 2.6.1.GA has nothing to do with JSF changed. ... | | My objectives are not to offend anybody, so sorry if that is the case. My objectives are to ensure that uses can migrate to new versions of the portal as easy as possible. I think my mission is complete in this discussion View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070980#4070980 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070980

18 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: User Portlet Discussion

by thomas.heute＠jboss.com

"anders3" wrote : An example NOT to follow was the upgrade to 2.6.1.GA where the JSF changed. This did not make happy existing users. I find this quite offending since i already explained that to you. Upgrading to 2.6.1.GA has nothing to do with JSF changed. You had 2.6.0.GA running on JBoss AS 4.0.5 ? Fine, run 2.6.1.GA on JBoss AS 4.0.5, we made everything so that it can work on both. Again, the bundle version is now including JBoss AS 4.2.1.GA (instead of JBoss AS 4.0.5), the bundle version is targeting people who want to get an easy start (not for a migration then). There was no breaking change between 2.6.0.GA and 2.6.1.GA only bug fixes. Now on the User portlet changes, i still don't understand your issues, can you please give me a clear use case. If the portlet changes from JSP to JSF and is reorganized *internally* would that have an impact on your end-users ? We'll keep the code of the former one, but what i don't want is to bring confusion by having 2 user portlets deployed out of the box. Only the new one will be deployed. That said, we didn't talk yet about having the new portlet in 2.6 Branch or 2.8. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070959#4070959 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4070959

18 years, 8 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 August 2007