will those contextual annotations in 299 replace @Scope in Seam 3?
Yes of course. Obviously.
299/Weld is supposed to replace the core of Seam. so that's: %SEAM_HOME%\src\main\org\jboss\seam\core package, correct? does the Weld core injection affect annotations package as well in Seam 2.x?
It means the whole Seam core. Not the package named
core. It means jboss-seam.jar.
ok cool. so I imagine Seam 3 will be backwards-compatible with Seam 2.x apps? So that means in Seam 3 I can still use @In instead of @Inject?
We will provide interoperability between Seam2 style beans and JSR-299 beans. Of course, we don't recommend that you use @In in new code.
I'm 99% certain that you've asked this question before.
Soon he'll ask if Seam 3 is ready yet ;-) Sorry, couldn't help myself...
LOL. Do you think we could implement an ArbiQuestionGeneratorBean in CDI?
Actually, come to think of it, how sure are we that Arbi isn't a bean?
Well, we could always try specializing him...
Keep asking questions Arbi, I for one enjoy reading them :)
Haven't started looking at CDI yet and I'll no doubt have learned lots useful bits and bobs by quickly checking the forum now and then.
yeah, sorry. not only do i ask a lot of questions, i don't check for duplication prior to posting, don't always read the specs and i have a bad memory.
anyways, at least you guys have some fun about it.
But if you specialized (a clone of) me, that would really make me and the rest of the forumites feel extra special. lol.
I have myself deployed as a singleton bean using @Factory method in an infinite loop, generating lots of questions for your (dis)enjoyment. lol.
Arbi, we're just teasing.
Ok, cool, it's hard to tell in these forums. The concepts in 299 are difficult to grasp so I know I'm asking some basic/stupid questions. But as long as I learn that's fine.
anyways, I have a
meetingwith an acquired company tomorrow in SoCal for a possible new
function. I may be doing professional Seam 2.x development again very soon (crossing my fingers). Unfortunately, the larger parent company may presumably in the future be
enforcingthe current Java enterprise platform standard (you guessed it, Spring) for new app development upon this smaller, purchased division. I don't want that to happen.
Can't you guys get me a job with Redhat or an affiliate to help make CDI (EE 6) and/or Seam 3 more common as the
corporate Java development platform/standard? Is that a marketing function or a product manager function or what?
Perhaps they will consider if you manager to get VMWare to adopt Seam 3 as their framework of choise ;-)
By the time that happens, Oracle will have bought VMWare. Seems like the only company Oracle won't buy is Microsoft. btw, I installed Windows 7 Ultimate on my pc and it's very good so far...