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

[Design of JBoss Build System] - Re: Dependency conflicts lost during AS mavenization

by pgier

"heiko.braun(a)jboss.com" wrote : I'd like to remove all legacy artifacts (wrong group-id) from the repo. This would force anyone to update (because the build breaks). But I am not sure about the implications. | | Does this require any dependent project to republish it's artifacts and pom or can an existing repo artifacts simply be updated? The risk of doing this is that it can break old builds that depend on the old groupId. The official maven way to move artifacts around in a repository is to add a relocation configuration to the pom (http://maven.apache.org/ref/2.0.4/maven-model/maven.html#class_relocation). What would you think if we create a new location in the repository for stuff that is in the repository but should have been in a different place? So maybe something like http://repository.jboss.org/maven2_legacy. This way we can remove stuff from the main repository to make it cleaner, and if we want to build older releases that depend on some of these things, this legacy repo location just needs to be added to settings.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140978#4140978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140978

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Circular dependency error msg problem

by alesj

"scott.stark(a)jboss.org" wrote : If all resolvable dependencies were processed and then resolveDependencies returned false, only the two cyclic dependencies would remain for the error processing. | Yup, that's right. Should we change AbstractDependencyInfo::resolveDependencies to work this way? Or some additional (quick) isResolved on DependencyItem? Which would only do some check, not changing the state inside the instance. e.g. | public boolean isResolved(Controller controller) | { | return isResolved() || controller.getInstalledContext(iDependOn) != null; | | } | which we would then use in DeployersImpl::checkControllerContext | for (DependencyItem item : dependsInfo.getIDependOn(null)) | { | if (item.isResolved(controller) == false) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140973#4140973 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140973

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBM 2.0 new Security Manager

by ataylor

Ive created a new Security manager for JBM 2.0. Instead of the security store talking direct to the Jboss AuthenticationManager it uses a new interface JBMSecurityManager. There are 2 implementations of this interface, JAASSecuritymanager, which basically does what the old security store does and delegates to the JAAS AuthenticationManager and a simple implementation that can be used for standalone or embedded purposes, or even with the App server if the user so wishes. Ive also added a SecurityManager Deployer that will load users and roles from an xml file (jbm-security.xml) into the Simple SecurityManager. The old tests still use a JAAS based Authentication, however any new style tests that create a MessagingServer dynamically will use the Simple one, because of this the simple SecurityManager automatically adds a guest user so the tests still pass. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140970#4140970 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140970

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Root cause with iDependOn equal null

by alesj

A bit related to this: - http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4140958#4140958 In the case where iDependOn == null this is then used | Object iDependOn = item.getIDependOn(); | if (iDependOn == null) | { | dependency = "<UNKNOWN>"; | actualStateString = "** UNRESOLVED " + item.toHumanReadableString() + " **"; | } | Meaning (UNKNOWN) name is used for all dependencies that don't have iDependOn set. But when we look for root cause (see IncompleteDeployments::calculateContextsError) | Map<String, Set<MissingDependency>> contextsMissingDependencies = getContextsMissingDependencies(); | if (contextsMissingDependencies.isEmpty() == false) | { | for (Map.Entry<String, Set<MissingDependency>> entry : contextsMissingDependencies.entrySet()) | { | for (MissingDependency dependency : entry.getValue()) | rootCauses.put(dependency.getDependency(), dependency.getActualState()); | } | } | we use the name as key. So all (UNKNOWN) would be flattened into single entry. Should I add something like | dependency = "<UNKNOWN " + GUID.asString() + ">"; | ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140967#4140967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140967

18 years

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb 1.0.0.SP2

by alex.loubyansky＠jboss.com

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - DemandDependencyItem and iDependOn in constructor

by alesj

Is there a reason why DemandDependencyItem doesn't set demand as iDependOn in its constructor? | public DemandDependencyItem(Object name) | { | super(name, null, whenRequired, null); | Since then we get a lot of these | Object iDependOn = item.getIDependOn(); | if (iDependOn == null) | { | dependency = "<UNKNOWN>"; | actualStateString = "** UNRESOLVED " + item.toHumanReadableString() + " **"; | } | in DeployersImpl:checkControllerContext View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140958#4140958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140958

18 years

1
0
0 / 0

[Design of JBoss ESB] - Re: About authentication / authorization on ESB services?

by mark.little＠jboss.com

Yes, it does at this time. However, we are actively working on adding such support for the next major release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140942#4140942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140942

18 years

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb 1.0.0.SP2

by dimitris＠jboss.org

In the old jboss common, all those libraries (core, logging-spi + impls) are combined together. Since this is to be used in Branch_4_2, I am not sure if producing maven artifacts is necessary. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140927#4140927 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140927

18 years

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb 1.0.0.SP2

by alex.loubyansky＠jboss.com

What about logging-spi? logging-log4j? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140913#4140913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140913

18 years

1
0
0 / 0

[Design of JCA on JBoss] - JBAS-5278 Errors .

by vickyk

I have been seeing the following error in org.jboss.test.jca.test.ExecuteJMSDuringRollbackStressTestCase testcase . 2008-04-01 17:58:53,658 TRACE [org.jboss.resource.connectionmanager.TxConnectionManager] (WorkerThread#0[127.0.0.1:59944]) commit problem: | org.jboss.resource.JBossResourceException: Could not commit LocalTransaction; - nested throwable: (javax.jms.TransactionInProgressException: Cannot call commit on an XA session) | at org.jboss.resource.adapter.jms.JmsLocalTransaction.commit(JmsLocalTransaction.java:60) | at org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource.commit(TxConnectionManager.java:990) | at com.arjuna.ats.internal.jta.resources.arjunacore.XAOnePhaseResource.commit(XAOnePhaseResource.java:110) | at com.arjuna.ats.arjuna.LastResourceRecord.topLevelPrepare(LastResourceRecord.java:170) | at com.arjuna.ats.arjuna.coordinator.AbstractRecord.topLevelOnePhaseCommit(AbstractRecord.java:441) | at com.arjuna.ats.arjuna.coordinator.BasicAction.onePhaseCommit(BasicAction.java:2639) | at com.arjuna.ats.arjuna.coordinator.BasicAction.End(BasicAction.java:1784) | at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:88) | at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:177) | at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1390) | at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) | at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75) | at org.jboss.test.jca.test.ExecuteJMSDuringRollbackStressTestCase.setupQueue(ExecuteJMSDuringRollbackStressTestCase.java:262) | at org.jboss.test.jca.test.ExecuteJMSDuringRollbackStressTestCase.testExecuteJMSDuringRollback(ExecuteJMSDuringRollbackStressTestCase.java:72) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) These details I have found from the server log . I am not sure why this is failing here . What could be the problem ? I made changes in the test-jms-local-ds.xml at tx-connection-factory <xa-transaction/> This got me the rid of the above exception but the test failed with this error details Expected one text message: null | java.lang.RuntimeException: Expected one text message: null | at org.jboss.test.jca.test.ExecuteJMSDuringRollbackStressTestCase.checkQueue(ExecuteJMSDuringRollbackStressTestCase.java:280) | at org.jboss.test.jca.test.ExecuteJMSDuringRollbackStressTestCase.testExecuteJMSDuringRollback(ExecuteJMSDuringRollbackStressTestCase.java:99) Any inputs here ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140910#4140910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140910

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