News: ServiceLayer Beta Release: Instant Web Services for Java Apps

  1. AgileIT (http://agileitinc.com) announces a beta test program for ServiceLayer(TM). Apply for the beta program by filling out this form: http://agileitinc.com/ApplyToBeta.html The beta release software works with Windows and Tomcat. Linux and other Java EE containers to be supported soon. ServiceLayer(TM) is a run-time Java framework that enables you to dynamically add web services to an existing Java application using a point-and-click interface. To use ServiceLayer(TM) for web service enabling a Java executable, you simply start the program using a script - 'sl' - instead of 'java'. If the Java app runs inside a container (e.g., Tomcat, WebSphere, JBoss, etc.) you simply deploy ServiceLayer(TM) into that container. ServiceLayer(TM) scans the program bytecode and provides a graphical user interface showing all the program's classes and methods that can be exposed as web services. You simply point-and-click to select the web services you want to expose. No coding is required to web service enable a Java application with ServiceLayer(TM). No migration, recompilation, or repackaging is needed either. ServiceLayer(TM) is completely non-intrusive and it does not modify your program's bytecode or source code. ServiceLayer(TM) works by mirroring the bytecode of the Java program that it web service enables. Only the bytecode related to those methods exposed as web services gets mirrored. Within its mirroring system, ServiceLayer(TM) "enhances" its copies of the program's .class files by injecting bytecode to add the JAX-WS and JAXB annotations necessary for web services support. These enhanced copies of the original classes are used to translate web service request/response messages (e.g., SOAP, REST) to method invocations that are processed by the program being mirrored. No changes are made to the original program and its bytecode continues to run in the JVM without any modifications. AgileIT invented its (patent pending) dynamic bytecode mirroring system after more than three years of research and development aimed at making Java web services easier to use. No product we are aware of offers similar capabilities. Although powered by sophisticated technology, ServiceLayer(TM) is easy to use. Just point-and-click to configure an existing Java program to run as a web service enabled application.
  2. It sound like a new Web Service framework which does Web service creation on the fly. I mean just search the classes and from the reflection you find the classes and list them out. I have two questions -1. Does this only work on JDK 1.5 or above ? -2. How about the QoS support, like security, reliability etc ? Thank you Deepal
  3. Yes, that is exactly right. This is a new framework that creates services dynamically - i.e., "on the fly". As far as I know, there is nothing else like it. The simplest mode of operation is to run JDK 1.6. However, you can run ServiceLayer(TM) to enable web services on any Java application running under JDK 1.4.2 or higher. For example, if you have an application - say MyWebApp - deployed in Tomcat running under JDK 1.4.2, you can use ServiceLayer(TM) to web service enable MyWebApp as long as you have a JDK 1.6 installed on the same machine. ServiceLayer will launch a separate "serialization process" JVM using JDK 1.6. ServiceLayer(TM) then offloads all its web services processing (e.g., converting from XML to Java) to the "serialization process" running under JDK 1.6. QOS features are in the works, but not included in the current beta. The primary purpose of this beta release is to show that the product works. It is quite amazing actually. Without any coding, you can invoke any Java application via web services with ServiceLayer(TM). We are hoping to get feedback from beta users regarding QOS and other features (e.g., user interface, audit, etc.) they would like to see in the product. Mark Hansen Founder and President AgileIT LLC White Plains, NY
  4. On the other hand, since your juvenile "class copy" code is obfuscated by bytecode, that DOES seem smart. PATENT GRANTED! Also, while your at it why dont you try and patent ORM? See cocobase. ooops.
  5. No Obfuscation[ Go to top ]

    There is no obfuscation. The product works directly at the bytecode level so that you can web service enable Java applications without needing access to the source code.
  6. You can send the USPTO a blank sheet of paper and get patent pending. And the fact thats its patented, means my organization would never use it. Thanks A-Holes