May 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: DESCRIBE phase - Dependency builders for MC Beans

by jaikiran

While i am trying these things out i'll also check, in the current AS, how many beans need this AOPDependencyBuilder. Just want to reduce the number of MC clients that need to add this additional configuration to override the behaviour. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230471#4230471 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230471

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Naming, @JNDI and OnDemand

by adrian＠jboss.org

"alesj" wrote : | "adrian(a)jboss.org" wrote : | | That's why it is called "Described" and its where "On Demand" originally left things until "PreInstall" was introduced. | Really? | | Hmmm, I though our PreInstall didn't change things. | Or why we now leave them in Not_Installed? We'll maybe I'm dreaming and didn't actually implement it properly (yet ;-) The same issue is also required for this feature: https://jira.jboss.org/jira/browse/JBMICROCONT-78 where an "on demand" pojo is registered in JMX before the instance exists with a simple mbean that just has a "start" operation until you click/invoke it to create the real pojo. You aren't going to know whether to register it in JMX unless you've looked at the annotations (both instance and class) which happens in the describe stage. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230470#4230470 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230470

16 years, 11 months

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by jaikiran

"adrian(a)jboss.org" wrote : 3) Using ObjectName.quote() is probably not the same thing. It would lead to a mangled | and probably unreadable ObjectName. | Thanks, i wasn't aware of that. I did notice Ales mentioning similar thing about this, but did not get a chance to try it out. Letting it remain the way it is won't be a big deal, once we take care of not registering the optional MBeans, by default. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230466#4230466 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230466

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Naming, @JNDI and OnDemand

by adrian＠jboss.org

"alesj" wrote : WRT | - initial ml post: http://lists.jboss.org/pipermail/jboss-development/2008-November/012997.html | - the latest ml post (where Adrian moves his code to svn): http://lists.jboss.org/pipermail/jboss-development/2009-May/014341.html | | A few questions after checking the code. | (1) | | | /** | | * JNDI. | | * | | * TODO move to AS integration project | | * @author <a href="adrian(a)jboss.com">Adrian Brock</a> | | | Where exactly would you wanna move this? | What should we do with "duplicated" @JndiBinding in AOP-MC-int? | We need a standard annotation that is provided independent of the implementation. AS integration project is here: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/integration/ as previously discussed on the dev list it is supposed to allow users to not have to worry about the implemementations of how it is actually implemented. e.g. in maven you import org.jboss.integration:naming not jnpserver or aop. anonymous wrote : | (3) Basically the OnDemand test is completely broken. :-) | I said it was largely untested, but you were in a hurry for me to commit it. :-) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230465#4230465 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230465

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Naming, @JNDI and OnDemand

by alesj

"adrian(a)jboss.org" wrote : | Why does it defeat the purpose of "On Demand"? | I thought it was meant to do *nothing*. :-) "adrian(a)jboss.org" wrote : | That's why it is called "Described" and its where "On Demand" originally left things until "PreInstall" was introduced. Really? Hmmm, I though our PreInstall didn't change things. Or why we now leave them in Not_Installed? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230464#4230464 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230464

16 years, 11 months

1
0
0 / 0

[Design of JBoss Identity] - JBoss Identity IDM 1.0.0.Alpha5 released

by bdaw

JBoss Identity IDM component 1.0.0.Alpha5 was tagged today. Major changes are: 1) Support for Sybase and DB2. Addition to the automated testsuite in hudson: http://hudson.jboss.org/hudson/view/JBoss%20Identity/ 2) Query API implementation: http://anonsvn.jboss.org/repos/jbossidentity/idm/tags/1.0.0.Alpha5/idm-ap... http://anonsvn.jboss.org/repos/jbossidentity/idm/tags/1.0.0.Alpha5/idm-ap... 3) Improved JBoss AS integration. Currently IDMService can create hibernate SessionFactory from specified configuration file, check if database schema exist, export it and execute bsh script to populate initial content. See authentication example below 4) Initial implementation of JBossIdentityIDMLoginModule. It can validate user password and resolve associated groups from a configured group type. See authentication example below 5) JEE Authentication example project: http://anonsvn.jboss.org/repos/jbossidentity/idm/tags/1.0.0.Alpha5/exampl... It is a maven2 project that creates a SAR containing a simple WAR with secured jsp page. IDMService is used to bootstrap IdentitySessionFactory and pre populate database with two default users. JBossIdentityIDMLoginModule validates user credentials. http://anonsvn.jboss.org/repos/jbossidentity/idm/tags/1.0.0.Alpha5/exampl... Sample idm-example-auth.sar is ready to use without any additional configuration. Just put it into JBoss Application Server 5 and point your browser to "http://localhost:8080/idm-example-auth"... 6) Maven structure reorganization. GroupId was changed to "org.jboss.identity.idm" and module "idm" was split into: - idm-core - containing core API/SPI implementation with minimal additional dependencies (like jaxb) - idm-hibernate - containing HibernateIdentityStoreImpl and all needed hibernate entities - idm-ldap - containing LDAPIdentityStoreImpl - idm-cache - initial cache implementation with JBossCache. More changes to come in this area.... Everything is plugable so it is possible to use only "idm-core" with custom SPI (IdentityStore) implementation. Pending issues can be tracked with JIRA: https://jira.jboss.org/jira/browse/JBID/component/12312180 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230460#4230460 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230460

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Naming, @JNDI and OnDemand

by adrian＠jboss.org

"alesj" wrote : "alesj" wrote : | | What to do? :-) | | (a) have OnDemand stay in Pre_Install | | (b) add extra Not_Installed AOP lifecycle hook | | | As seen, none of these two will work. | Only moving On_Demand to Describe will work, | but that defeats the purpose of On_Demand. | Why does it defeat the purpose of "On Demand"? The idea of On Demand is to not create the bean, we can still look at its metadata and see what we would do if we were to construct it and activate it. That's why it is called "Described" and its where "On Demand" originally left things until "PreInstall" was introduced. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230455#4230455 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230455

16 years, 11 months

1
0
0 / 0

[Design of POJO Server] - Re: Various performance issues in core projects

by adrian＠jboss.org

3) Using ObjectName.quote() is probably not the same thing. It would lead to a mangled and probably unreadable ObjectName. 4) The correct way to not register (sub-)deployment/components in JMX is to remove the @JMX annotation from the DeployersImpl bean in conf/bootstrap/deployers.xml If the DeployersImpl is not registered in JMX then neither will be the deployments. This has nothing directly to do with the bean. It is letting you look (using JMX) at what deployers the deployment/component went through, the attachments (deployment descriptors) associated with the deployment/component and maybe how long the processing took for each deployer if you enable the stats. It's just debug information so it is optional. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230450#4230450 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230450

16 years, 11 months

1
0
0 / 0

[Design of JBoss Portal] - Tomahawk jscookMenu is not rendered

by brondumm

Hi there, I'm having problems rendering a jscookMenu in a portlet deployment. I'm using Apache Tomahawk v. 1.1.8 on a JBoss Portal Server v. 2.6. Some of the JavaScript is actually embeded in the resulting HTML, but not all of it! Is this a known Tomahawk/portlet bug, or am I missing something? No exceptions are thrown... Cheers, Brondumm View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230445#4230445 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230445

16 years, 11 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: JSR 250 injection on VDF

by wolfc

As an example of servlets not waiting for their dependencies: https://jira.jboss.org/jira/browse/JBAS-6795 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230437#4230437 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230437

16 years, 11 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 May 2009