User: cgjung Date: 02/02/18 01:14:32 Modified: jboss.net/docs README.html Log: updated jboss.net doco (finally!) Revision Changes Path 1.5 +29 -59 contrib/jboss.net/docs/README.html Index: README.html =================================================================== RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- README.html 4 Feb 2002 09:38:58 -0000 1.4 +++ README.html 18 Feb 2002 09:14:32 -0000 1.5 @@ -23,12 +23,11 @@ and the Web ... </cite> -<p class="text"> We think (and also <a ref="http://www.sun.com"/>SUN</a> -and its licensees have recently began to sloooowly recognize) that Web Services -and the <a href="http://j2ee.sun.com";>J2EE</a> platform are an ideal match. J2EE is a mature and +<p class="text"> As emphasised in the <a href="http://www.sun.com/sunone";>Sun Open Network Environment</a> vision, +Web Services and the <a href="http://j2ee.sun.com";>J2EE</a> platform are an ideal match. J2EE is a mature and productive environment for developing and deploying application logic. Web Services provide a new degree of cross-platform interoperability especially -wrt. the <a href="http://www.microsoft.com/net/";>Microsoft .NET</a> cosmos +wrt the (surely upcoming) <a href="http://www.microsoft.com/net/";>Microsoft .NET</a> cosmos that <a href="http://www.omg.org/corba";>CORBA and IIOP</a> are not able to provide. <p class="text"> @@ -45,7 +44,10 @@ </li> </ul> while keeping track with respective standardisation efforts in the Java Community, -the W3C consortium, and the Microsoft development department. +the W3C consortium, and the Microsoft development department. It is - for the time being - <br>NOT</br> an attempt +to build a platform-independent .NET implementation! For that purpose, please have a look at +the commercial <a href="http://halcyonsoft.com/products/iNET.asp";>Halycon iNet (Beta)</a> +or the <a href="http://www.go-mono.com/";>Mono</a> Open Source project. <p class="head">Features and release plan @@ -55,7 +57,7 @@ In a first phase, JBoss.net is adapting the <a href="http://xml.apache.org/axis";>Apache Axis</a> distribution (current release is alpha 2, installed under <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/thirdparty/apache/axis/";>thirdParty/apache/axis</a>). -Axis is a successor to the <a href="http://xml.apache.org/soap/";>Apache-SOAP 2.0</a> effort +Axis is a clean-room successor to the <a href="http://xml.apache.org/soap/";>Apache-SOAP 2.0</a> effort and comes with a well-configurable processing architecture that is quite similar to the JBoss container concept. @@ -67,25 +69,24 @@ like security, specialised typemappings, .NET interoperability, and keeping track with the XML-related JSR�s. -<p class="text"> JBoss.net is currently a pre-alpha and prototypes some basic concepts -of J2EE-based Web Service integration: +<p class="text"> JBoss.net is currently an alpha version and prototypes some basic concepts +of J2EE-based Web Service integration: <ul> <li class="text"> The <code>org.jboss.net.axis.server.AxisService</code> MBean installs the basic Axis invocation engine and an adapted transport servlet in the associated -WebContainer (<a ref="jboss-jetty.jsp">Jetty</a> or <a ref="jboss-tomcat.jsp">Tomcat</a>). A configurable -<code>org.jboss.net.axis.AxisInvocationHandler</code> eases the construction of detached +WebContainer (tested with <a ref="jboss-jetty.jsp">Jetty</a>, afterwards also <a ref="jboss-tomcat.jsp">Tomcat</a>). +A configurable <code>org.jboss.net.axis.AxisInvocationHandler</code> eases the construction of detached (dynamic) client proxies that transparently access remote Web Services, such as published by the AxisService. </li> <li class="text"> -The AxisService MBean functions as a (hot-)deployer -for so-called <em>Web Service aRchive</em> (WSR- or .wsr-) files. These are ordinary .jar files -that contain, besides necessary byte code for plugging into the Axis machinery, a slightly extended -<a ref="http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/user-guide.html";>deployment descriptor</a> +The AxisService MBean functions as a (hot-)deployer for so-called <em>Web Service aRchive</em> (WSR- or .wsr-) files. +These are ordinary .jar files that contain, besides necessary byte code for plugging into the Axis machinery, a +slightly extended <a ref="http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/user-guide.html";>Axis deployment descriptor</a> in their "META-INF/web-service.xml" entry. </li> @@ -110,12 +111,12 @@ <li class="text"> A specialised <code>org.jboss.net.axis.server.EJBProvider</code> allows to interface/map Web Service invocations immediately to session beans. For that purpose, .wsr files can -be deployed as "client applications" within .ear files (<java/> modules). We allow -"<ejb-ref\>" entries in the Web Service descriptor to link the +be deployed as "client applications" within .ear files (<java/> modules). We allow +"<ejb-ref\>" entries in the Axis deployment descriptor to link the naming environments of the Web Service to the corresponding EJB�s. This is quite similar to the way that Web Applications/servlets in .war files are linked to EJB�s -in the Virtual Machine. Support for session-based entity bean access and suitable security -models is envisaged. +in the Virtual Machine (see the Web Container Howto for that purpose). +Support for session-based entity bean access and suitable security models is envisaged. </li> </ul> @@ -123,15 +124,14 @@ JBoss.net is strongly connected to features of Jboss 3.0 (Rabbit Hole) and hence, we try to synchronize with its release plan. We are seeking any available help for testing the existing code, constructing a detailed requirement list, and -implementing features! See the -<a ref="http://sourceforge.net/pm/task.php?group_project_id=13975&group_id=22866&func=browse";>Todo&Assignment List</a> +implementing features! See the <a ref="http://sourceforge.net/pm/task.php?group_project_id=13975&group_id=22866&func=browse";>Todo&Assignment List</a> and make your development skills immortal! <p class="head">How to build, install and use Jboss.net <p class="text"> Before you go on writing your first Web Service in Java, we recommend -that you have a look at code and meta-data samples -at <link href="http://xml.apache.org/axis/";>the axis site</a>. +that you have a look at code and meta-data samples at +<link href="http://xml.apache.org/axis/";>the axis site</a>. <p class="text"> <em>To build</em>, you can run either @@ -174,57 +174,27 @@ the http transport facility. The necessary runtime libraries (lib/ext/axis.jar, deploy/lib/jboss-net.sar and client/jboss-net-client.jar) and configuration files (conf/default/axis-config.xml and client/client-config.xml) are installed as a part of the above BUILD step. - -<p class="text">If you would like to enable the AutoDeployer to delegate deploying of WSR-files, -you have to give it a reference to JBoss.net�s Axis service (in conf/default/jboss-service.xml) - -<pre> - <mbean code="org.jboss.deployment.AutoDeployer" name="jboss:service=AutoDeployer"> - <attribute name="Deployers"> - jboss.system:service=ServiceDeployer; - jboss.jca:service=RARDeployer; - jboss.j2ee:service=J2eeDeployer; - jboss:service=Axis - </attribute> - ... - </mbean> -</pre> -<p class="text">If you would like to configure JBoss.net with a different WebContainer, please replace the -dependency and WarDeployer references in deploy/lib/jboss-net.sar!META_INF/jboss-service.xml (the way that +<p class="text">Since January 2002, the AxisService is able to register itself as a .wsr deployer at the +org.jboss.system.MainDeployer, hence simply putting a .wsr file (or a .wsr file embedded into some other +hierarchically structured deployment package, such as an .ear) into your deploy directory is enough. +If you would like to configure JBoss.net with a different WebContainer, please replace the dependency and +WarDeployer references in deploy/lib/jboss-net.sar!META_INF/jboss-service.xml (the way that code and deployment descriptors are bundled will change in RH!) by your favorite servlet-runner: <pre> <server> - <depends>jboss.web:service=Jetty</depends> - <mbean code="org.jboss.net.axis.server.AxisService" - name="jboss:service=Axis"> + name="jboss.net:service=Axis"> + <depends>jboss.web:service=Jetty</depends> <attribute name="WarDeployerName">jboss.web:service=Jetty</attribute> <attribute name="RootContext">axis/</attribute> <attribute name="SecurityDomain">java:/jaas/other</attribute> </mbean> </server> -</pre> - -<p class="text">If you would like to enable the AxisService to deploy -the java-client modules of your .ear files (I pledge for having a </code>org.jboss.system.UniversalDeployer</code> underlying -the Autodeployer for that purpose!), please add the following line to the configuration of -your J2eeDeployer in the deploy/j2eedeployment-service.xml. - -<pre> - - <mbean code="org.jboss.deployment.J2eeDeployer" - name="jboss.j2ee:service=J2eeDeployer"> - <attribute name="DeployerName">Default</attribute> - <attribute name="JarDeployerName">:service=ContainerFactory</attribute> - <attribute name="WarDeployerName">jboss.web:service=Jetty</attribute> - <attribute name="JavaDeployerName">jboss:service=Axis</attribute> - </mbean> - </pre> <p class="text"><em>To test</em>: The successfull installation of JBoss.net will be reported
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
