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

[Design of JBoss Web Services] - Re: container integration naming issue

by thomas.diesler＠jboss.com

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBMETA-44, ws annotation processing for references

by alessio.soldano＠jboss.com

Hi, I'm looking at the JBWS-2171 failure too (and the related issue). Still have to figure out what changed from AS500Beta4 in the behavior we had about service-interface null or not null. In the mean time, just two considerations regarding JBWS-2171: - it seems to me the @WebServiceRef / @WebServiceRefs annotations on class (type target) are not processed since the WebServiceRef processor is called on field annotations only - having the serviceRef.getAnnotatedElement() != null prevents the code throwing the "<service-interface> cannot be null" exception from being executed, since the check that lead to that exception is performed when looking for the type of service ref (JAXWS or JAXRPC) and of course having an annotated element implies JAXWS. This just to say that error might also be misleading. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157964#4157964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157964

16 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by bstansberry＠jboss.com

Re: create, start, stop, destroy, yeah, looking into simplifying that makes sense. The 4 step lifecycle is kind of a legacy artifact of the way the old JBoss AS JMX microkernel worked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157962#4157962 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157962

16 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by bstansberry＠jboss.com

anonymous wrote : Another method I don't find appropriate for public API is evict. I do not see an y reason for it to be publicly available, as it is rather internally used by eviction thread. No! It makes total sense for a cache-based application to want to control memory management itself. The application often knows more about the overall state of the system than the cache does. The fact that JBC provides a feature whereby it can help the application control memory doesn't mean that users should be forced to use that mechanism. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157961#4157961 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157961

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: @RemoteBinding/@LocalBinding in jboss-metadata

by ALRubinger

Well, whether this makes CR1 will depend on the regressions this introduces. :) For now my little hack is limited only to @RemoteBindings / @RemoteBinding / @RemoteHomeBinding / @LocalHomeBinding /@JndiBindingPolicy and lives in EJB3 Core (locally on my machine). S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157958#4157958 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157958

16 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by mircea.markus

move throws an exception if either source or destination does not exist. This is inconsistent with the rest of the API, as it is the only method that trows an exception if nodes(s) are inexistent. E.g. removeNode(fqn) will return a false if the node to be added was not found. Here are some suggestions for changing this: 1) return a false if either source or destination does not exist (no-op) 2) treat it as a remove followed by an put: remove the node (return false if does not exist) and if destination does not exist create it (put semantics). I vote for 1, mainly because 2 is hard to explain to the user View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157954#4157954 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157954

16 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by mircea.markus

curently there are 4 life cycle methods on the cache: create, start, stop, destroy. Although these methods have a different semantics, merging them in two (start and stop) is simpler for the user to understand and use. Also the performance gain we bring by allowing one to reuse (re-start) a cache is not that big, start is doing all the hard word compared with create (object creation). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157951#4157951 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157951

16 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by mircea.markus

Another method I don't find appropriate for public API is evict. I do not see an y reason for it to be publicly available, as it is rather internally used by eviction thread. The only other possible usage I am aware of is in the case of eviction, when you want to use your own "eviction timer" - starting with 3.0 this will be handled through a plugable eviction timer (JBCACHE-1268). So if no other use cases for using Cache.evict, I suggest deprecating it from the public API. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157946#4157946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157946

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: @RemoteBinding/@LocalBinding in jboss-metadata

by alex.loubyansky＠jboss.com

Are you fixing this for CR1? If not then I wouldn't suggest to hack stuff. I just got the tests for EjbJar30Creator pass for JBoss50Creator. So, most of the stuff should be covered. I am not sure at the moment whether we can use JBoss50Creator in CR1. I'll try it locally to see what the effects are. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157939#4157939 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157939

16 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: jBPM integration with ESB

by kukeltje

You kind of live on a razors edge right? But yes... you have some credits in this forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4157936#4157936 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4157936

16 years, 3 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 June 2008