November 2006 - jboss-dev-forums - Jboss List Archives

[Design of EJB 3.0] - Re: Need to deploy based on a metamodel

by bill.burke＠jboss.com

I thought Adrian was rewriting the ejb3/javaee metamodel? What happened with this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982833#3982833 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982833

18 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Clustering tests and hsqldb

by scott.stark＠jboss.org

What about just switching to another embedded database such as derby or javadb? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982829#3982829 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982829

18 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to deploy based on a metamodel

by scott.stark＠jboss.org

I did merge the org.jboss.metamodel used by the ejb3 web tier components into the org.jboss.metadata model. This certainly could be done elsewhere. The concern is how to reuse the ejb3 deployer when it needs to be integrated with legacy jboss-4.0.x servers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982825#3982825 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982825

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Relative order of deployers to other deployers

by scott.stark＠jboss.org

"kabir.khan(a)jboss.com" wrote : How about a precedence bean that is injected into the main deployer, and defines relative ordering between all the deployers that would otherwise be at the same level. Isn't the main deployer what maintains the order of all the deployers? Yes, its the MainDeployerImpl that uses standard collections and the Deployer.COMPARATOR to order deployers based on the relativeOrder value currently. Allowing for the injection of the comparator would allow for alternate ordering mechanisms. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982824#3982824 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982824

18 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: Relative order of deployers to other deployers

by kabir.khan＠jboss.com

How about a precedence bean that is injected into the main deployer, and defines relative ordering between all the deployers that would otherwise be at the same level. Isn't the main deployer what maintains the order of all the deployers? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982821#3982821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982821

18 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LDAP Support expectations

by bdaw

"bdaw" wrote : | Any contribution is kindly welcome. If you are willing to help you need to | 1) sign contributiors agreement: http://labs.jboss.com/portal/con?noproject=true | 2) then you can add your code as a patch in jira and I'll integrate it | 3) code must be tested | 4) And if you contribute more often and gain trust of the team you can get svn access in the future ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982816#3982816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982816

18 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LDAP Support expectations

by bdaw

"bvogt" wrote : | Is the db part assigned to one already? If not, I can do it (because I need it ;-) ). | It's assigned to me ;) Any contribution is kindly welcome. If you are willing to help you need to 1) sign contributiors agreement: http://labs.jboss.com/portal/con?noproject=true 2) then you can add your code as a patch in jira and I'll integrate it 3) code need to have test cases otherwise it'll be rejected For the implementation: The DB part you mention is not a big deal as for the base functionality its mostly about refactoring current hibernate stuff from 2.4 to comply with new interfaces in 2.6 (UserModule, RoleModule, MembershipModule and UserProfileModule) There is org.jboss.portal.identity2 package in portal trunk in which new stuff is being done. After it's completed it'll replace the old implementation. What is currently in svn looks more like draft at the moment. I'm going to give it more definite shape in around 2 weeks. So there may be future changes in the design but big. So for the hibernate implementation what differes is UserProfileModule. I was thinking about two implementations 1) current behaviour - we have a DBUserImpl object which fields are mapped to a table columns. so UserProfile is simply a fasade to get calles on DBUserImpl object 2) dynamic mapping - we define hibernate mappings for a user object in separate file and than construct SessionFactory based on them. The benefit is that we can mapp those atrributes in any way we want. This can be widen of course. >From my point of view is that whatever you implement as long it implements the right interfaces its ok. If you want to propose something different we can always bundle it as optional implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982808#3982808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982808

18 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LDAP break the testsuite

by bdaw

sounds ok. I'll do it in this way then View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982801#3982801 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982801

18 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - LDAP break the testsuite

by julien＠jboss.com

When I run the testsuite I have the ldap service breaking because it cannot deploy portal-test.sar : | 2006-11-02 23:35:19,039 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/Users/julien/java/jboss-portal-2.6/test/output/lib/portal-test.sar | org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.portal.test.framework.embedded.opends.OpenDSService; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoader | s found for: org.jboss.portal.test.framework.embedded.opends.OpenDSService) | at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) | at org.jboss.system.ServiceController.install(ServiceController.java:226) | I have to disable it for now. Also the testsuite must be able to run on JDK 1.4 and not require Java 5. If JDK 1.4 is selected then we need to find a way to run only JDK 1.4 stuff. Also I think that portal-test.sar (test agent) is not the right place for the OpenDSService deployment. You need to make it in a separate sar file living in the identity module, so I am going to remove it from the portal-test.sar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982799#3982799 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982799

18 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Need to deploy based on a metamodel

by anil.saldhana＠jboss.com

I have an immediate need in that if the user has configured specific rolename-principals mapping in jboss-app.xml, then those need to be picked up by ejb3 metamodel. These security role mappings get merged in the ejb21 and web meta data world. But the ejb3 meta model (based on independent JBossXB) is not doing the merge. The metadata parsed for the ear (J2EEApplicationMetaData) is available to the EJB3 deployment, but it is not using it. A concern I have is that due to this merge (J2EEApplicationMetaData->security Roles) into the ejb3 AssemblyDescriptor ->security roles, there will be a link between ejb3 metamodel and the old org.jboss.metadata due to the use of J2EEApplicationMetaData/SecurityRoleMetaData. I know the original intent of ejb3 metamodel was not to use the old metadata infrastructure for ejb21/web. I guess since this is all temporary and there will be an effort for an unified metadata from either Adrian or Bill, I am adding this change. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982798#3982798 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982798

18 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 November 2006