January 2009 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: A taster - jboss reflect docs

by alesj

Some better (more than just saying 'Nice') feedback: * Initial diagram should show TypeInfo/ClassInfo as well * TypeInfo's / ClassInfo's weak cache could be mentioned (TypeInfoFactory as a singleton) * Joinpoint spi/api is deprecated? Adrian? * Is Classadapter still good usage? It should be either enhanced or removed? * Explain BeanAccessMode View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203163#4203163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203163

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Versioning

by wolfc

For Jira we need a single version which signifies the release we do towards AS and Embeddable. So let's add a 'Fix Component Version(s)' and see how that goes. It also will make sure that the roadmap as shown in Jira won't get messy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203161#4203161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203161

17 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: A taster - jboss reflect docs

by richard.opalka＠jboss.com

"alesj" wrote : What's "ClassLoading SPI" doing there at the end? It's in the jboss-reflect/trunk SVN repo. The TODO at the end of document needs to be evaluated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203158#4203158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203158

17 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: A taster - jboss reflect docs

by richard.opalka＠jboss.com

Feel free to modify the document where necessary. It's just first draft ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203156#4203156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203156

17 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: A taster - jboss reflect docs

by alesj

Nice. :-) What's "ClassLoading SPI" doing there at the end? ps: I'll read in more details asap ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203154#4203154 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203154

17 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failures on testPagedMessageDeliveredMultipleConsumersAf

by ataylor

I'll take a look View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203149#4203149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203149

17 years, 2 months

1
0
0 / 0

[Design of POJO Server] - A taster - jboss reflect docs

by richard.opalka＠jboss.com

Adrian, Ales, could you put some feedback/comments to JBoss Reflect Introduction document? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203148#4203148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203148

17 years, 2 months

1
0
0 / 0

[Design of JBoss Tools (dev)] - Re: Incorporate Hibernate Search into Hibernate Tools idea

by sannegrinovero

cool! I would like to use a tool like that. anonymous wrote : 2) automatic annotation creation for some entity/entities - at least in the simplest case - @Indexed & @Field What do you mean by "automatic"? I don't think it's possible to find a way to guess the correct positions and options for a Field annotation; maybe from the queries but it seems to me quite hard. anonymous wrote : 4) as one more idea - it would useful if all of these has some common switch in interface which is not very bind to Lucene; you refer to an interface update to the luke tools? what's wrong with being tightly coupled to Lucene for a tool like this? anonymous wrote : b) possible to view list of entities for the index (@Indexed), possible to view hierarchy of index entities relation (@ContainedIn and @IndexedEmbedded) I would highly appreciate a view like the Hibernate Tools mapping diagram, showing the resulting index fields and how they are mapped to the entities. anonymous wrote : 5) may be some functions which will help adjust index for better search result and performance - it is similar for clause 3 but not exactly the same; A practical use case? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203138#4203138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203138

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Versioning

by ALRubinger

"wolfc" wrote : Since everything we build is consumed by some other project/component, the proposal is moot. ;-) Aha, I said "directly consumed". :) I stand by the proposal because 1) The JIRA process will closer reflect what we're actually doing 2) Not upgrading stuff for name's sake both saves time and makes for less errors. "wolfc" wrote : Components need a qualifier to make sure that nothing unstable ends up in the supported chain. I want to get to a point were we can say use a version range [1.0,1.1) and not worry about it any more. Qualifiers are doing nothing for us in practice. In actuality, we have the following criteria for any release: * Passes EJB3 Integration TestSuite 100%, except for known issues and transient failures * Passes TCK 100% * No regression in AS TestSuite * Passes module Unit Tests 100% Nowhere along there am I checking that all dependencies are of some particular qualifier. "wolfc" wrote : As for the versioning I agree we need some more transparency there, but we can't create a scheme that's too complicated for users to follow. Since an user doesn't have to find out which component is failing, it'll be reported against our 'global' affected version. Likewise the 'global' fixed version should report the released version. So version per component doesn't sound like a solution to me. Users won't even go that far; they'll report EJB3 problems against their AS version. Or get the version wrong. Either way we'll typically correct "Affects Version" in the JIRA most of the time, same with "component". Regardless of what users are reporting, the problem remains that we currently don't have a scheme in JIRA which correctly models what we're doing. We *do* have version-per-component. To pretend we don't in JIRA is incongruent. One fundamental disagreement we have is that I *do not* believe: anonymous wrote : For any GA release, all dependencies must also be a least GA level I stated our release criteria for ejb3-as-int above. However, a particular component may be implementing some new feature that isn't mature enough to be GA. Take for example: * I start building ejb3-async to fulfill EJB 3.1 requirements of @Asynchronous invocations * At release time, ejb3-async is 1/2 completed. * All the requirements for ejb3-as-int to be released are fulfilled, and we can even preview 1/2 the support of the new ejb3-async module. ejb3-async isn't even complete, so it's not a GA. Does that mean that ejb3-as-int is also not a GA? Why not; it's both more stable and more feature-rich than the previous release. Hmm, so I should promote ejb3-async to GA? But it's not complete. (Start cycle again) That's the philosophical argument. Here's the practical one: I don't want to re-release perfectly good binaries, and update the entire dependency chain, just to get a qualifier promotion that we ignore anyway. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203137#4203137 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203137

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: Using generics info in CollectionPropertyHandler

by alesj

"alex.loubyansky(a)jboss.com" wrote : | So, you can open Jira issues to enhance support in this area. | Not really. :-) As all this Map stuff was a mystery for me from the beginning - see my MC attempts at AbstractMapMetaData. ;-) "alex.loubyansky(a)jboss.com" wrote : | If you do, please, specify how critical this is. So I can prioritize. Thanks. Not really critical, it's just an enhancement (hence feature), to prevent future metadata developers from wildcard-ing wrong types. e.g. throwing exception at parse time, rather than at usage time View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203129#4203129 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203129

17 years, 2 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 January 2009