I always thought Service-Oriented-Architecture was a a devteam take-a- break bullshit word.
You know, something you tell the brass so they get off your back for a month or two, giving the team time to spend some much needed time in feature-freeze, cleaning up stuff, refactoring code to be more maintainable for the future, and turning hacked together workarounds into proper fixes. Once you're done, you tell management you have the exact same thing you had before, except it's now all smoother and more maintainable (true), and that it is because "it now has more SOA" (which is false, as SOA is meaningless blather). I guess I'm wrong. On a total sidenote, Oracle has not acquired sun yet. The notion that netbeans is out to get you to move towards for-pay oracle products now, well short than a year after a sale to oracle was likely, strikes me as extremely paranoid behaviour that is obviously not true. The fact that some (ex-)netbeans developers and many sun engineers read these forums only adds to the extreme rudeness of this kind of paranoid rambling. Please consider that when you next post your delusions. On Dec 11, 3:55 am, kibitzer <[email protected]> wrote: > This post is extremely disheartening -- basically, it looks like the > NetBeans team will no longer develop the SOA > features:http://forums.netbeans.org/post-56916.html. > > I can only see this as the beginning of Oracle pushing people towards > jDeveloper and the Oracle suite. Not surprising but extremely > disappointing. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
