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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Noise at undeployment

by clebert.suconic＠jboss.com

anonymous wrote : Yes please. It took me two hours including disassembling the jar in my local | repository before I figured this out. | | If we are going to use version control then let's do it properly otherwise it is pointless. Sorry again... It was my understanding that if I retaged, the maven repo would pick this up, and as we hadn't officially released CR1 I thought the re-upload would be appropriate. anonymous wrote : P.S. Why isn't this default config visible in the -persistence-service.xml for easy override? | It was while I was researching how to do this (by reading the source), that | I realised the source didn't match the object. We do this for all the databases but HSQLDB. On HSQLDB we just pick the default config specified on the source code. But we can consider also exposing the SQL Statement on next release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144484#4144484 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144484

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Programmatic policy for jar handling

by adrian＠jboss.org

"alesj" wrote : When I'm swapping the root with unpacked on top level, must I also change the root in VFSDeployment? No the deployment represents the client side view over the original artifact. i.e. it is the request not the response. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144474#4144474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144474

16 years, 7 months

1
0
0 / 0

[Design of JBoss Portal] - Re: JBoss Portlet Container integration into 2.7

by thomas.heute＠jboss.com

The bugs are now fixed in SVN. Still, as you said: anonymous wrote : | What is remaining to be done in that area is : | | 1/ update of the faces portlet component to handle a portlet generated event as a JSF event | | 2/ implement a special event that signals the end of the configuration activity during content edition using the same "urn:jboss:portal:content" namespace with an appropriate name. When this event is received it should tells the JSF admin portlet that content is configured. Today that already exists but relies on a special action parameter which is the previous way to communicate. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144473#4144473 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144473

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Noise at undeployment

by adrian＠jboss.org

"clebert.suconic(a)jboss.com" wrote : In the future I won't retag it any more (I would just create another CR2). Yes please. It took me two hours including disassembling the jar in my local repository before I figured this out. If we are going to use version control then let's do it properly otherwise it is pointless. I can confirm when I exchange CR1v1 for CR1v2 the noise is gone. ;-) P.S. Why isn't this default config visible in the -persistence-service.xml for easy override? It was while I was researching how to do this (by reading the source), that I realised the source didn't match the object. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144470#4144470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144470

16 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Programmatic policy for jar handling

by alesj

When I'm swapping the root with unpacked on top level, must I also change the root in VFSDeployment? AbstractStructureBuilder.class | public DeploymentContext populateContext(Deployment deployment, StructureMetaData metaData) throws DeploymentException | { | if (deployment == null) | throw new IllegalArgumentException("Null deployment"); | if (metaData == null) | throw new IllegalArgumentException("Null metaData"); | | boolean trace = log.isTraceEnabled(); | if (trace) | log.trace("Populating deployment " + deployment.getName() + " metaData=" + metaData); | | DeploymentContext result; | try | { | result = createRootDeploymentContext(deployment); | if (result == null) | throw new IllegalStateException("Root deployment context is null"); | result.setDeployment(deployment); | | ContextInfo contextInfo = metaData.getContext(""); | if (contextInfo == null) | contextInfo = StructureMetaDataFactory.createContextInfo("", null); | | // APPLY THE ContextInfo.isUnpack() check here | // implementing it in VSFStructureBuilder | | contextInfo.setPredeterminedManagedObjects(deployment.getPredeterminedManagedObjects()); | applyContextInfo(result, contextInfo); | } | catch (Throwable t) | { | throw DeploymentException.rethrowAsDeploymentException("Error populating deployment " + deployment.getName(), t); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144469#4144469 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144469

16 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Remapping transitive dependencies

by dimitris＠jboss.org

Just exclude jboss:jboss-common-core when importing jnpserver for now AND correct the dependency on the jnpserver project for the next release. I don't know of a mapping mechanism in maven. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144467#4144467 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144467

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Noise at undeployment

by clebert.suconic＠jboss.com

(I have tried this myself with an empty repo, and fresh SVN copy) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144464#4144464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144464

16 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Noise at undeployment

by clebert.suconic＠jboss.com

I have retaged CR1 with a small fix on the SQLs, that would cause that. I understood from Paul Gier that the Maven repo would verify for updates daily, and the retag was done two days ago. I'm pretty sure you would be able to fix it by updating your maven repo. You could remove /home/.me/repository, your thirdparty and build it again. In the future I won't retag it any more (I would just create another CR2). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144463#4144463 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144463

16 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Re: Remapping transitive dependencies

by scott.stark＠jboss.org

We can just update the dependency to org.jboss:jboss-common-core version=2.2.5.GA and release it as 5.0.0.Beta5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144454#4144454 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144454

16 years, 7 months

1
0
0 / 0

[Design of JBoss Build System] - Remapping transitive dependencies

by wolfc

jnpserver has a dependency on jboss:jboss-common-core, while others have a dependency on org.jboss:jboss-common-core. Is there a way to remap this? [INFO] [dependency:tree] | [INFO] org.jboss.ejb3:jboss-ejb3-transactions:jar:0.13.0-SNAPSHOT | [INFO] +- junit:junit:jar:4.4:test | [INFO] +- jboss.aop:jboss-aop-deployer-jdk50:jar:2.0.0.CR8:test | [INFO] +- org.jboss:jnpserver:jar:5.0.0.Beta4:test | [INFO] | +- apache-log4j:log4j:jar:1.2.14:test | [INFO] | +- jboss:jboss-common-core:jar:2.0.2.GA:test | ... | [INFO] +- org.jboss:jboss-transaction-spi:jar:5.0.0.Beta4:compile | [INFO] | +- jboss:jboss-common-logging-spi:jar:2.0.4.GA:compile | [INFO] | +- org.jboss.javaee:jboss-jca-api:jar:1.5.0.Beta3Update1:compile (version managed from 1.5.0.20070913080910) | [INFO] | | \- (org.jboss:jboss-common-core:jar:2.2.5.GA:compile - version managed from 2.2.2.GA; omitted for duplicate) | ... So I would like to specify that jboss:jboss-common-core is interpreted as org.jboss:jboss-common-core. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144451#4144451 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144451

16 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2008