BEA & Oracle product lines

Oracle came back with another offer to BEA last week and made a deal. I don't want to meditate on pros-and-cons of this acquisition, just to make my personal prediction about future of middleware product line of this joint enterprise (don't read further if you don't like this kind of forecasting ;)
I'm positive regarding WebLogic Server as there is a broad acceptance of this application server contrary to the Oracle one. Not so sure with WebLogic Integration because of Oracle BPEL Process Manager (former Collaxa BPEL Server) and its standards-based approach. On the other hand, WLI has a broader feature set, but honestly, do we need it? In area of ESB, AquaLogic Service Bus is a clear winner for me, with an extensive support of different types of services. BPM is much more fuzzy to me because BEA ALBPM (even it's a great product) might not fit well into Oracle BPA Suite, an analytical and modelling platform. And finally area of SOA registries/repositories: both Oracle Registry and BEA ALSR are OEM versions of HP Systinet Registry so there is no clash. There is no real Oracle repository, thus BEA ALER is a winner.
In summary, I don't think WebLogic and AquaLogic platforms are intended just for maintanence, but will replace (or coexist with) some of the Oracle's actual products.
Update: After reading several "Oracle&BEA" posts saying nothing, I've found a nice summary of opinions about middleware future under flag of Oracle.

Time to shut up and code

If you like REST, you have definitely heard about Pete Lacey. He is a big protagonist of this architecture style and it is always a pleasure to read his blog. His last post is somehow special, because he is leaving Burton Group, where he worked for couple of years as a consultant, now joining Collaborative Software Initiative (CSI) as an open source developer. I recommend you to read his reasons, but a short explanation is:

It’s time to shut up and code.

IMHO, this shows his soul of a core developer, his enthusiasm to create something what you can "touch", what works and what can be used also by others (CSI has a specific business model by using and producing purely open source software). Last but not least, he believes sharing practical knowledge and experiences (via Web) is much more effective than writing a research paper targeted to just a limited number of your customers.

I would go so far as to say that Sam Ruby’s blog, for instance, has done more to change the world than the millions of pages minted by R&A firms that only a select few get to read.

I wish Pete a lot of luck and satisfaction in his new job!