October 2007 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: 2.0.0.Beta5 released

by scott.stark＠jboss.org

These versions referrenced by the build/pom-jdk14.xml don't make sense for a retrod jar though, so what was the last version of the mc that was retrod? | <properties> | <version.jboss.common.core>2.2.1-SNAPSHOT</version.jboss.common.core> | <version.jbossxb>2.0.0.CR3</version.jbossxb> | <version.osgi.r4.core>1.0</version.osgi.r4.core> | <version.jboss.vfs>2.0.4.snapshot</version.jboss.vfs> | <version.javassist>3.6-beta</version.javassist> | <version.jaxb.api>2.0</version.jaxb.api> | <version.jboss.aop>2.0.0-SNAPSHOT</version.jboss.aop> | <version.jboss.common.logging.spi>2.0.5-SNAPSHOT</version.jboss.common.logging.spi> | <version.jboss.classloading.spi>5.0.0-SNAPSHOT</version.jboss.classloading.spi> | <version.org.jboss.test>1.0.4-SNAPSHOT</version.org.jboss.test> | <version.junit>3.8.1</version.junit> | <version.jboss.profiler.jvmti>1.0.0.CR5</version.jboss.profiler.jvmti> | <version.ant.junit>1.7.0</version.ant.junit> | <version.backport.concurrent>2.1.0.GA</version.backport.concurrent> | <version.javax.management.jmxri>1.2.1</version.javax.management.jmxri> | <version.org.jbossretro.rt>1.1.2</version.org.jbossretro.rt> | </properties> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097196#4097196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097196

18 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: 2.0.0.Beta5 released

by kabir.khan＠jboss.com

"scott.stark(a)jboss.org" wrote : You mean from the 2.0.0.Beta5 tag? | https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/2.0.0.Be... | | I did not update the pom-jdk14.xml so that will be one problem. What jars are we retroing when we do a release? | I only need the jar from the container/ project View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097195#4097195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097195

18 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: 2.0.0.Beta5 released

by scott.stark＠jboss.org

I updated the version in the poms and the build is failing due to out of date commons version being used. This is referring to the 2.2.1-SNAPSHOT which itself is a jdk5 artifact. | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD FAILURE | [INFO] ------------------------------------------------------------------------ | [INFO] Compilation failure | | C:\home\svn\JBossMC\tags\2.0.0.Beta5\container\src\main\org\jboss\reflect\plugin | s\introspection\IntrospectionTypeInfoFactoryImpl.java:[59,33] cannot find symbol | | symbol : class WeakTypeCache | location: package org.jboss.util.collection | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097194#4097194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097194

18 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: 2.0.0.Beta5 released

by scott.stark＠jboss.org

You mean from the 2.0.0.Beta5 tag? https://svn.jboss.org/repos/jbossas/projects/microcontainer/tags/2.0.0.Be... I did not update the pom-jdk14.xml so that will be one problem. What jars are we retroing when we do a release? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097193#4097193 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097193

18 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Default window state

by julien＠jboss.com

Otoh we support it for the life time of 2.6 and having a dedicated tag would be better for end users as it is more explicit and less error prone. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097187#4097187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097187

18 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Node removal not working with Invalidation?

by bstansberry＠jboss.com

Agreed; if leaving tombstones around on remote nodes makes sense, it makes sense to do it locally as well. I was trying to think how this could break things; e.g. app removes some data and then tries to recreate it. Say an admin creates a "user" account entity; realizes he's mucked it up, deletes it and starts over with the same id. He could get version conflicts when he starts over. But: 1) With the present approach of tombstones on remote nodes, that problem already exists, if the admin happens to work on a different node when he starts over. 2) If implicit data versioning is used, it wouldn't be a problem. 3) If explicit data versioning is used, it could be a problem. But perhaps that can be handled in the Hibernate/JBC integration, which separately handles cache insertions of newly created entities. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097186#4097186 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097186

18 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Default window state

by chris.laprun＠jboss.com

I don't think that it should matter too much since we should move away from the XML descriptors anyway... This is why I would vote for proposal #1 as it doesn't imply a new tag, hence minimal modification to the current format. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097185#4097185 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097185

18 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-1153 - structural nodes

by manik.surtani＠jboss.com

Thinking a bit more about this since we spoke yesterday; I think this can become a problem since even a node with no data still has an overhead and an impact on memory. I think they should still be considered for eviction. The whole purpose behind JBCACHE-1153 is so that certain nodes can be considered structural and not considered for eviction since they are just "path builders" rather than data buckets. Can't we just use the resident flag for this purpose instead? See my comment on http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097183#4097183 about tombstones and invalid nodes. It shows how you could have empty nodes with no data, that *should* be considered for eviction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097184#4097184 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097184

18 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Node removal not working with Invalidation?

by manik.surtani＠jboss.com

Here's a thought re: nodes being removed locally but still living as tombstones on remote nodes (as a placeholder for the version that last existed). Isn't there enough of an argument that says even the locally removed node should not be removed, but instead just have it's data removed and then marked as invalid? The same argument for the need of the last used version will apply, since the node may be re-added anywhere else in the cluster, potentially with an older version. Agreed that this does become a problem with regards to memory footprint, at least until eviction kicks in ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097183#4097183 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097183

18 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: 2.0.0.Beta5 released

by kabir.khan＠jboss.com

I need a retroed jboss container jar in http://repository.jboss.org/jboss/microcontainer14/2.0.0.Beta4/ But I get problems | Kabir@KabirDell ~/sourcecontrol/microcontainer/container | $ mvn -f pom-jdk14.xml clean install | [INFO] Scanning for projects... | Downloading: http://repo1.maven.org/maven2/org/jboss/microcontainer-jdk14/jboss-microc... | [WARNING] Unable to get resource 'org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5' from repository central (http://repo1.maven.org/maven2) | [INFO] ------------------------------------------------------------------------ | [ERROR] FATAL ERROR | [INFO] ------------------------------------------------------------------------ | [INFO] Failed to resolve artifact. | | GroupId: org.jboss.microcontainer-jdk14 | ArtifactId: jboss-microcontainer-jdk14 | Version: 2.0.0.Beta5 | | Reason: Unable to download the artifact from any repository | | org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5 | | from the specified remote repositories: | central (http://repo1.maven.org/maven2) | | | [INFO] ------------------------------------------------------------------------ | [INFO] Trace | org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14 for project: null:jboss-container-jdk14:jar:null | at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:373) | at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:286) | at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) | at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:324) | at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) | at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) | at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) | at org.codehaus.classworlds.Launcher.main(Launcher.java:375) | Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14 for project: null:jboss-container-jdk14:jar:null | at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1198) | at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:697) | at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:431) | at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:195) | at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:523) | at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:455) | at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:359) | ... 11 more | Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14' not found in repository: Unable to download the artifact from any repository | | org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5 | | from the specified remote repositories: | central (http://repo1.maven.org/maven2) | | at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:528) | at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1194) | ... 17 more | Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository | | org.jboss.microcontainer-jdk14:jboss-microcontainer-jdk14:pom:2.0.0.Beta5 | | from the specified remote repositories: | central (http://repo1.maven.org/maven2) | | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:197) | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) | at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:482) | ... 18 more | Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository | at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:308) | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:185) | ... 20 more | [INFO] ------------------------------------------------------------------------ | [INFO] Total time: < 1 second | [INFO] Finished at: Sat Oct 20 13:29:33 BST 2007 | [INFO] Final Memory: 1M/2M | [INFO] ------------------------------------------------------------------------ | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097178#4097178 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097178

18 years, 5 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 October 2007