March 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Build System] - Re: Notion of 'compatible-version'?

by heiko.braun＠jboss.com

ALR wrote: anonymous wrote : | | Most I've seen from this is a wishlist/informal roadmap of sorts: | | http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+... | | Anyone know about the status of this? | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136202#4136202 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136202

18 years

1
0
0 / 0

[Design of JBoss Build System] - Notion of 'compatible-version'?

by heiko.braun＠jboss.com

Does maven support the notion of 'compatible-version'? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136201#4136201 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136201

18 years

1
0
0 / 0

[Design of JBoss Build System] - Shared Parent POM for dependencyManagement

by ALRubinger

One problem present with EJB3 (and likely other projects in the future) is the lack of a proper dependency matrix. As it currently stands, EJB3 dependencies are defined by the EJB3 Build module, set as the parent POM for the other modules. We are specifying the versions here to match those of AS by hand. If EJB3 is not compiling against the same version that the AS assembly will be placing in the runtime, we're setting ourselves up for disaster with any number of potential version conflicts. There is no contract ensuring that our manual process is valid. All of the proper dependencies are defined in the JBossAS Parent POM. However, EJB3 cannot depend on AS as this introduces a cyclic dependency. Therefore, I'd like to move all of the versioning (dependencyManagement section) of the JBossAS Parent POM to a new project, potentially an AS component. This way, both EJB3 Build and AS Assembly can depend on the same versions/definitions, and we become bound to a shared contract. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136182#4136182 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136182

18 years

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: Question about Remoting, Marshalling, and EJBs

by ron.sigal＠jboss.com

Thanks, everyone, for your rapid replies. 1. I've gone ahead and added this feature, and I don't think it will have any impact on any other projects. 1a) Upon further inspection, I see that org.jboss.invocation.unified.marshall.InvocationMarshaller acts only upon InvocationRequests, so in the server-to-client direction it has no effect. 1b) Just in case, I added the parameter org.jboss.remoting.transport.rmi.RMIServerInvoker.RMI_ONEWAY_MARSHALLING (actual value "rmiOnewayMarshalling"), which, when set to "true", will cause the RMI transport to revert to its current marshalling behavior. 2. Galder, where are those "unified invoker unit tests" tests you mentioned? I'd like to take a look at them. 3. Bill, where is org.jboss.serial.io.MarshalledObjectForLocalCalls? 4. Finally, Galder, note that it's never to early to start agitating for a meeting in Neuchatel next September. :-) -Ron View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136167#4136167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136167

18 years

1
0
0 / 0

[Design of POJO Server] - Re: JBAS-5259, JMS Destination Names is showing as QueueServ

by scott.stark＠jboss.org

The testDLQ is definitely checked in: https://svn.jboss.org/repos/jbossas/trunk/testsuite/src/main/org/jboss/te... but was not in the suite of explicitly declared tests. I have added that. I tried running this on another box: | [starksm@valkyrie testsuite]$ ant tests-profileservice | ... | [junit] Running org.jboss.test.profileservice.test.JmsDestinationUnitTestCase | [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.681 sec | [junit] Running org.jboss.test.profileservice.test.ProfileServiceUnitTestCase | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136165#4136165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136165

18 years

1
0
0 / 0

[Design of POJO Server] - Re: Invalid jboss-deployers-vfs-spi POM

by ALRubinger

"adrian(a)jboss.org" wrote : If you don't want to do the extra work of reading a forum where a project is being developed then don't use a snapshot. :-) That wasn't an option. I've got to use the same versions for EJB3 as the AS assembly will place in the runtime, else I'll have a version conflict. But after the changes to the build system, and the discussion on a forum you weren't monitoring, I'm guessing you now feel my pain. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136164#4136164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136164

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Injection of Security Domain annotation into the contain

by anil.saldhana＠jboss.com

Think I have figured it out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136129#4136129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136129

18 years

1
0
0 / 0

[Design of EJB 3.0] - Re: Injection of Security Domain annotation into the contain

by anil.saldhana＠jboss.com

| public Ejb3Deployer() | { | // TODO: when the annotation scanner deployer comes on, we will always have JBossMetaData | //super(JBossMetaData.class); | //addInput(JBossMetaData.class); | addInput(MergedJBossMetaDataDeployer.EJB_MERGED_ATTACHMENT_NAME); | I tried setting the input in EJB3Deployer to use the mergedmetadata. So in the deploy method of ejb3deployer, I am seeing the merged meta data. But when the SecurityDomainMetaDataBridge is invoked, it is back to square one. Not the merged meta data. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136125#4136125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136125

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by anil.saldhana＠jboss.com

Ok, now I follow you. "jbossmq" is the security domain name or application policy. The DatabaseServerLoginModule is the login module name. I was saying that it should not depend on DSLM. Just terminology difference. I also followed that the security domain name should be more like "jbossmq" and not "java:jaas/jbossmq" which is more like an internal implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136124#4136124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136124

18 years

1
0
0 / 0

[Design of Security on JBoss] - Re: Security Injection in AS5

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | | | <bean name="Whatever" ...> | | <property name="securityDomain"><security-domain-ref xmlns="urn:jboss-security-beans:1.0" name="jbossmq"/></property> | | ... | | | In practice a jboss developer would be more likely to use it programmatically | String securityDomainName = ... | beanMetaDataBuilder = ... | beanMetaDataBuilder.addProperty("securityDomain", new SecurityDomainDependency(securityDomainName); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136111#4136111 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136111

18 years

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 March 2008