-
1. Re: Is WebBeans and JBAS 5.1 Production Ready?
gavin.king Jun 18, 2009 5:12 AM (in response to meetoblivion)I would say you are pretty safe, assuming that:
- you've done some prototyping and verified that the Web Beans preview has all the features you need, and
- you are going to write good tests for your own application.
The nature of this kind of software is that if it's going to break, it breaks well before you go into production. So as long us you don't deploy untested code, you're safe.
However, there are definitely bugs in the Web Beans preview, and the spec has definitely changed since it was released. So you should go in expecting to run into things that aren't perfect.
Therefore, if you want to be absolutely sure, you should wait for JBoss 5.2, which will feature a totally production ready implementation of 299.
Currently we target 5.2 for September, but I imagine that it could be a month or so late.
-
2. Re: Is WebBeans and JBAS 5.1 Production Ready?
meetoblivion Jun 19, 2009 2:43 AM (in response to meetoblivion)my main production-type issue is probably performance. i figure since most things are going to be bound in JNDI there's not much of a bottleneck in a map. we're expecting it to hit QA early next week and spend about 4 days there.
should i be concerned much about my JBAS issue?
-
3. Re: Is WebBeans and JBAS 5.1 Production Ready?
gavin.king Jun 19, 2009 3:11 AM (in response to meetoblivion)
John Ament wrote on Jun 19, 2009 02:43:
my main production-type issue is probably performance.
we're expecting it to hit QA early next week and spend about 4 days there.Then you will soon know if you have an issue. Seriously, the likelihood that Web Beans would be your performance bottleneck seems incredibly remote.
should i be concerned much about my JBAS issue?Um only you can tell us that. Does your app work?
-
4. Re: Is WebBeans and JBAS 5.1 Production Ready?
asookazian Jul 8, 2009 1:10 AM (in response to meetoblivion)
Gavin King wrote on Jun 19, 2009 03:11:
Seriously, the likelihood that Web Beans would be your performance bottleneck seems incredibly remote.Typically the db/data tier is the performance bottleneck in most CRUD apps.
But has the significant overhead involved with Seam's injection/interceptors been optimized in Web Beans' DI?
Why inject all context variables for every business method in a component if you really only need one of them injected for a particular public method, for instance? This should be configurable...
-
5. Re: Is WebBeans and JBAS 5.1 Production Ready?
pmuir Jul 8, 2009 11:59 AM (in response to meetoblivion)
John Jameson wrote on Jul 08, 2009 01:10:
Gavin King wrote on Jun 19, 2009 03:11:
Seriously, the likelihood that Web Beans would be your performance bottleneck seems incredibly remote.
But has the significant overhead involved with Seam's injection/interceptors been optimized in Web Beans' DI?Yes it has, injection occurs at object instantiation only.