Apache Beehive Buzz and Pollinate eclipse plug-in
John writes "Beehive is a new Apache project that simplifies Java 2 Platform, Enterprise Edition (J2EE) and Web services programming. This article shows how to get started with Beehive and offers a sneak preview of Pollinate, an Eclipse plug-in that creates Beehive applications."
I've been digging with XmlHttpRequest for over a month now - what I'd really love would be a way to automatically expose Java methods to Javascript.
> </script> . I don't give a damn whether it generates full SOAP stubs or anything - I want it to "Just Work".
Ideally it would be just an <script src="http://server/myclass.jws?client=javascript"
Php's type-less stuff doesn't really help me too much
Quidquid latine dictum sit, altum videtur
Is it just me, or does the example shown not seem very simplified? Granted, I didn't throughly read through the example, but it just seemed to me like another custom tag library on top of struts. And with that, all the complexity that comes with it. I just don't know about it. . . .
As Seen On TV's? Come back!!!
changing its name to the Apache Java Foundation and oh yes, we also do a non-Java web server? :-)
Oddly enough, there *are* other people working in other languages.......
"Web services programming."
Obviously the latest buzzword. So what is a good book on web services, and not just the programming aspect?
The article talks about how beehive sits on top of struts and makes a long and complex struts-config file a thing of the past.
That would be well and good, but it looks like in their example they are putting the same type of configuration information including flow control into hard coded controller classes instead. How is this any different? Let alone better that using an XML file? One of the main points of the struts-config is to allow the user to change page flow, permissions, navigation, validation options, using XML files that get interperted upon server startup so that these types of changes wouldn't require a new code deployment (and thus a long and arduous testing cycle).
Technology should innovate or at least attempt to build a better mouse-trap. I don't see how Beehive does either of the two. Perhaps there is a better explanation somewhere.
It seems very clear to me that this is an effort to bring Ruby on Rails to Java -- even the names of the classes are the same!
_anything_ is better than an xml config file, especially when one must document configuration and maintenance of some configured system to others who don't have the time to understand the intricacies of some plate-of-dried-spaghetty xml configuration system. Why are .properties files not used. Oh, because they're simple. And, god forbid having a system that is simple to manage/configure. I love java, but I tell ya, this whole "I can parse XML!" masturbatory party must end, and soon!
You are correct. It basically moves complexity from the XML config file into java code. Not sure which is better or worse.
If I were you, I'd look into Spring+WebFlow. It's not written by a bunch of people who don't know what they are doing (i.e. BEA).