Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Java Programming Software Apache

Apache Beehive Buzz and Pollinate eclipse plug-in 18

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."
This discussion has been archived. No new comments can be posted.

Apache Beehive Buzz and Pollinate eclipse plug-in

Comments Filter:
  • 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.

    Ideally it would be just an <script src="http://server/myclass.jws?client=javascript"> </script> . I don't give a damn whether it generates full SOAP stubs or anything - I want it to "Just Work".

    Php's type-less stuff doesn't really help me too much
  • 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. . . .
    • by hey! ( 33014 ) on Monday April 25, 2005 @10:00AM (#12336550) Homepage Journal
      Hello World is a good example for getting someone up to speed on a language, because it takes him through the most basic stuff -- creating a program, compiling and linking it, then invoking it -- without any unnecessary complexities.

      It makes no sense to use Hello World as an example for a MVC framework, because in that case the complexities are necessary. The point of the system is to organize the complexity in a well factored design; sincer in HW there is nothing to factor, the reader is left wondering what the point of all the machinery is.

      That said, this reminds me a lot of the approach Microsoft took to make MFC bearable -- which is to try to put a facade on the whole thing using an IDE.
  • by BigLinuxGuy ( 241110 ) on Monday April 25, 2005 @09:59AM (#12336542)
    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.......
  • by Minute Work ( 749085 ) <ipirateNO@SPAMyahoo.com> on Monday April 25, 2005 @10:54AM (#12337201)
    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.
  • Rails for Java? (Score:4, Informative)

    by jdclucidly ( 520630 ) on Monday April 25, 2005 @02:45PM (#12339835) Homepage
    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!

We are each entitled to our own opinion, but no one is entitled to his own facts. -- Patrick Moynihan

Working...