Slashdot Mirror


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."

18 comments

  1. Some java way to do Ajax easily ?. by Gopal.V · · Score: 1

    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

    1. Re:Some java way to do Ajax easily ?. by Gopal.V · · Score: 1

      Also not to mention that BeeHive @attributes looks a hell of a lot like .NET's [WebMethod]...

      Sad to see Sun copying MS (JVM had custom attributes since '97, but Java never had - till now).

    2. Re:Some java way to do Ajax easily ?. by MikkoApo · · Score: 2, Informative

      I think JSON-RPC-Java existed before the term Ajax had surfaced to /. or anywhere else.

    3. Re:Some java way to do Ajax easily ?. by Anonymous Coward · · Score: 0

      DWR does just that.

  2. Another layer. . . . by untouchable · · Score: 2

    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!!!
    1. Re:Another layer. . . . by hey! · · Score: 4, Insightful

      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.

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  3. Has the Apache Foundation ever considered ... by BigLinuxGuy · · Score: 3, Funny

    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.......

    1. Re:Has the Apache Foundation ever considered ... by Michael+Pigott · · Score: 2, Informative
    2. Re:Has the Apache Foundation ever considered ... by BigLinuxGuy · · Score: 3, Insightful

      Ah, I see the subtlety of the humor was lost....

      With that in mind (from the front page of Apache.org):

      # HTTP Server (C)
      # Ant (Java)
      # APR (C)
      # Cocoon (Java)
      # DB
      # Torque (Java)
      # ObjectrRelationalBridge (Java)
      # DB Commons (Nothing published, but has phrase "including but not limited to Java"
      # Directory
      # Apache Directory Server (Java)
      # LDAP (nothing published)
      # Naming (Java)
      # AuthX (nothing published)
      # ASN.1 (Java)
      # Kerberos (Java)
      # MINA (Multipurpose Infrastructure for Network Applications) (Java)
      # Excalibur (Java)
      # Forrest (Java)
      # Geronimo (Java)
      # Gump (Java, supports multiple language builds)
      # Jakarta (Java)
      # James (Java)
      # Lenya (Java)
      # Logging (Multiple languages)
      # Lucene (Java)
      # Maven (Java)
      # MyFaces (Java)
      # Perl (C)
      # Portals (Java)
      # SpamAssassin (Perl)
      # Struts (Java)
      # TCL (C)
      # Web Services
      # Axis (C++, Java)
      # WS-FX (C++, Java)
      # JaxMe (Java)
      # jUDDI (Java)
      # SOAP (Java)
      # WSIF (Java)
      # WSIL (Java)
      # WSRP4J (Java)
      # XML-RPC (Java)
      # EWS (Java)
      # Mirae (Java)
      # Muse (Java)
      # Scout (Java)
      # Addressing (WS-FX subproject) (Java)
      # Sandesha (WS-FX subproject) (Java)
      # WSS4J (WS-FX subproject) (Java)
      # Apollo (WS-FX subproject) (Java)
      # Hermes (WS-FX subproject) (Java)
      # XML
      # Xerces (Java, C++, Perl, COM)
      # Xalan (Java, C++)
      # AxKit (C)
      # Batik (Java)
      # FOP (Java)
      # Xang (JavaScript)
      # SOAP (Java)
      # Crimson (Java)
      # XML-Security (Java, C++)
      # Xindice (Java)
      # XML Commons (Java)
      # XMLBeans (Java)

      Now I may have missed a few, but it looks like the majority of the Apache projects are developed in and for Java. :-)

      That doesn't bother me, but I wanted to ensure that the source of *my* amusement was obvious.

    3. Re:Has the Apache Foundation ever considered ... by rleibman · · Score: 1

      Well, Java's just ziz langvage, you know?

  4. Web services? by Anonymous Coward · · Score: 0

    "Web services programming."

    Obviously the latest buzzword. So what is a good book on web services, and not just the programming aspect?

  5. Beehive vs struts? I don't see improvement by Minute+Work · · Score: 4, Insightful

    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.

  6. Rails for Java? by jdclucidly · · Score: 3, Informative

    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!

  7. Re:Beehive vs struts? I don't see improvement by Anonymous Coward · · Score: 0

    _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!

  8. Re:Beehive vs struts? I don't see improvement by Anonymous Coward · · Score: 0

    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).