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

[Design of JBossCache] - Re: Classloader leak via CacheImpl.invocationContextContaine

by manik.surtani＠jboss.com

Hmm, so should we re-introduce option-overloaded methods? We're looking at about 10 methods in Cache, 20 in Node and about another 20 in NodeSPI. We'd be doubling these to 20, 40 and 40. If this is what needs to happen then ok, but as far as possible I'd like the interfaces to be kept lean and simple. OTOH, I do agree with the ugliness and potential brittleness of setting an option before an invocation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053634#4053634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053634

19 years

1
0
0 / 0

[Design of JBossCache] - Re: CacheListener callbacks for block/unblock

by manik.surtani＠jboss.com

The problem with adding block calls to the listener are that it is a specialised callback that serves little general purpose use. The problem with a sub-interface is that it adds complexity and a performance bottleneck to the notifier (the need to test each listener if it is a subclass instance, etc). If at all I'd prefer the 2nd approach, so we could even move viewChanged() to the 2nd interface - perhaps ReplicatedCacheListener with viewChange() and block/unblock events. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053631#4053631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053631

19 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: building and testing sources

by msandoz

i think im almost there...i am however getting this error and not sure how to fix it. C:\temp\jbpm.3\build\build.xml:33: The following error occurred while executing this line: | C:\temp\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\build.xml:62: The following error occurred while executing this line | : | C:\temp\jbpm.3\designer\jpdl\org.jbpm.gd.jpdl.build\build.xml:218: Warning: Could not find file C:\temp\jbpm.3\designer\ | jpdl\org.jbpm.gd.jpdl.build\target\workspace\N.3.0.13.1\org.jbpm.gd.jpdl.feature-3.0.13.1.zip to copy. i have the .../workspace directory but it doesnt appear to have the N.3.0.13.1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053628#4053628 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053628

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remote replyto functionality - Bridge configuration in p

by timfox

Did you add the active mq jar file in jboss? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053626#4053626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053626

19 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Remote replyto functionality - Bridge configuration in p

by thomasra

Yes, that was my first attempt, too. But the problem was that using the plain jndi lookup caused classcasts between jboss and activemq. I don't have the actual stacktrace before me, but I can get back to you on that. BTW, ActiveMQ standalone does not include a fully functional jndi server, that may be what caused the problem in the first place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053625#4053625 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053625

19 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Retrowoven container project

by pgier

Ok, I should be able to add the GenericDeclaration stuff today. And then I will release retro 1.1.0 at the end of today or tomorrow. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053600#4053600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053600

19 years

1
0
0 / 0

[Deployers on JBoss (Deployers/JBoss)] - Re: Error while deploying jar file

by PeterJ

Shoot, I didn't look at the forum you used, this is a developer's forum, let's continue this discussion on your other post http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053422#4053422 And by the way, do NOT post the same question in multiple forums! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053599#4053599 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053599

19 years

1
0
0 / 0

[Design of JBoss Build System] - Release of jboss-retro

by pgier

I'd like to do a release of jboss retro as soon as we finish up this issue: http://jira.jboss.com/jira/browse/JBBUILD-333 So the release will probably happen at the end of the day today, or sometime tomorrow. I change the version to 1.1.0 since there are a few new features in addition to bug fixes. The completion of the maven build is pending an update that I submitted for the maven surefire plugin. So for now, the ant scripts will remain, but the maven build works, it just can't run the 1.4 tests until the updated surefire plugin is released. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053596#4053596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053596

19 years

1
0
0 / 0

[Design of JBoss jBPM] - Re: process patch files

by brittm

Bernd, deploying a new process and migrating is not a feasible option for large, complicated, long running process. When we take a new order, we don't have one process. Under one new order we spawn an order validation process, a credit check process, multiple service processes for each type of service on the order, each service process can spawn various vendor service order processes, etc., etc. Each new order can easily represent 15 processes of various types that are all interwoven together at some level. There is nothing unusual about our business; its typical telecom. In this environment, it is rare that migration is an option. While late binding of subprocesses helps a lot, there are simply times when we must update processes in place. What Tom was proposing greatly helps us do that (what we're going to do anyway) in as safe a way as possible. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053594#4053594 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053594

19 years

1
0
0 / 0

[Design of JBoss Build System] - Re: What is this circular dependency issue in common-core?

by pgier

"scott.stark(a)jboss.org" wrote : It still was not building for me: | | | | [starksm@succubus common-core]$ mvn release:prepare -DdryRun=true | | etc... | | | | until I updated my local repository maven2/jboss/jboss-common location to pull in the new parent pom. | Sorry about that, I guess when it looked in the relative path, it only found the new snapshot version. And the common-core pom didn't have the jboss repository listed, so it didn't know to get it from there. I changed the common projects so that they now extend directly from the jboss-parent. And they now have the appropriate repository configuration so that they can find the parent. The common projects will also be getting a group ID of "org.jboss" now instead of just "jboss". This will follow the maven conventions a little better, and allow us to differentiate open source projects vs. commercial projects (com.jboss) in the future if we want to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053581#4053581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053581

19 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 June 2007