User: cgjung Date: 02/03/12 03:04:45 Modified: jboss.net/docs README.html TODO Log: Axis Beta RC1 is here. Needs no more to be patched for integrating with the jboss classloading architecture. Lots of interna have changed, though. Adapted the deployment descriptors to support WSDD now. Revision Changes Path 1.7 +40 -18 contrib/jboss.net/docs/README.html Index: README.html =================================================================== RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -r1.6 -r1.7 --- README.html 28 Feb 2002 08:01:25 -0000 1.6 +++ README.html 12 Mar 2002 11:04:45 -0000 1.7 @@ -55,7 +55,7 @@ <img SRC="pictures/axis.jpg" align=right> 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 +distribution (current release is beta-ec1, installed under <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/thirdparty/apache/axis/";>thirdParty/apache/axis</a>). 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 @@ -86,7 +86,7 @@ <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";>Axis deployment descriptor</a> +slightly extended <a ref="http://cvs.apache.org/viewcvs.cgi/~checkout~/xml-axis/java/docs/user-guide.html";>Web Service Deployment Descriptor (WSDD)</a> in their "META-INF/web-service.xml" entry. </li> @@ -176,11 +176,12 @@ are installed as a part of the above BUILD step. <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 +<code>org.jboss.system.MainDeployer</code>, 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: +code and deployment descriptors are bundled is likely and hopefully to change in RH!) +by your favorite servlet-runner: <pre> @@ -207,31 +208,53 @@ (or an equivalent address depending on the configuration of your WebContainer and the RootContext) should return the default "hello" response page of the AxisServlet. -<p class="text">A <a href="http://localhost:8080/axis/services?list";>http://localhost:8080/axis/services?list</a> +<p class="text">When you start JBoss with the -Daxis.enableListQuery=true option, a <a href="http://localhost:8080/axis/services?list";>http://localhost:8080/axis/services?list</a> request should return an xml document describing the current configuration of the AxisEngine including the deployed services. The services section should look like: <pre> - <services> - <service pivot="JMXHandler" name="RemoteAdaptor"> - <option name="ObjectName" value="Web:service=Adaptor" /> + <?xml version="1.0" encoding="UTF-8" ?> + <deployment xmlns="http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java"> + <service name="RemoteAdaptor" provider="Handler"> + <parameter name="handlerClass" value="org.jboss.net.jmx.server.MBeanProvider" /> + <parameter name="ObjectName" value="jboss.net:service=Adaptor" /> </service> - </services> -</pre> - -<p class="text">This is the already mentioned end-point of the RemoteAdaptor web service that -is mapped to a dedicated MBean. Indeed, if you have a look at your <a ref="http://localhost:8082/";>current JMX state</a> there + <service name="Administration" provider="java:MSG"> + <parameter name="allowedMethods" value="AdminService" /> + <parameter name="isStatic" value="true" /> + <parameter name="methodName" value="AdminService" /> + <parameter name="enableRemoteAdmin" value="false" /> + <parameter name="className" value="org.apache.axis.utils.Admin" /> + </service> + <transport name="http"> + <requestFlow> + <handler type="java:org.apache.axis.handlers.http.HTTPActionHandler" /> + <handler type="java:org.apache.axis.handlers.http.URLMapper" /> + <handler type="java:org.apache.axis.handlers.http.HTTPAuthHandler" /> + <handler type="java:org.jboss.net.axis.SetClassLoaderHandler" /> + </requestFlow> + <responseFlow> + <handler type="java:org.jboss.net.axis.ResetClassLoaderHandler" /> + </responseFlow> + </transport> + <typeMapping encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"; serializer="org.jboss.net.jmx.adaptor.ObjectNameSerializerFactory" deserializer="org.jboss.net.jmx.adaptor.ObjectNameDeserializerFactory" type="java:javax.management.ObjectName" qname="ns1:ObjectNameType" xmlns:ns1="http://net.jboss.org/jmx"; /> + </deployment> +</pre> + +<p class="text">We recognize inter alia the already mentioned end-point of the RemoteAdaptor web service that +is mapped (via the <code>org.jboss.net.jmx.server.MBeanProvider</code>) to a dedicated MBean with JMX-ObjectName "jboss.net:service=Adaptor". +Indeed, if you have a look at your <a ref="http://localhost:8082/";>current JMX state</a> there should be the corresponding service up and running, ready to take your Web Invocations through the JMX bus. <p class="text">In the <a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/contrib/jboss.net/testsuite/";>JBoss.net testsuite</a>, we have assembled some samples and tests that can serve as an inspiration and source of insight. -You can build/run the testsuite as follows +You can build and run the testsuite against a runnign jboss server as follows <code> <pre> -cd build -build -Dmodules=jboss.net/testsuite tests +cd jboss.net/testsuite +build tests-standard-unit </pre> </code> @@ -239,8 +262,7 @@ (output/lib/addr.wsr is the JBoss-compatible package containing the Axis Address example, output/lib/hello.ear is a J2EE application consisting of the hello ejb module from the JBoss main testsuite and an additional web service layer on top of the HelloBean). In output/bin we also have put -some (non-functional, arrgh) batch files to run the individual tests. As soon as the testsuite -runs through - I still have some configuration problems - there will be more on that topic. +some (non-functional, arrgh) batch files to run the individual tests. <p class="head">DISTRIBUTION AND CVS 1.5 +14 -17 contrib/jboss.net/docs/TODO Index: TODO =================================================================== RCS file: /cvsroot/jboss/contrib/jboss.net/docs/TODO,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- TODO 4 Feb 2002 09:38:58 -0000 1.4 +++ TODO 12 Mar 2002 11:04:45 -0000 1.5 @@ -1,32 +1,29 @@ DONE -- AxisService installation, WebContainer invocation -- Axis logging configuration disabled -- Axis extension to remember service classloader correctly -- WSR-file structure and deployment -- MBeanProvider for Axis -- JMXConnector basic layout -- javax.management.ObjectName support -- Inclusion of .wsr as java-client into .ear, AxisService as java-client deployer in J2eeDeployer +- AxisService installation, WebContainer invocation. +- Axis logging configuration disabled. +- Axis extension to remember service classloader correctly. +- WSR-file structure and deployment. +- MBeanProvider for Axis. +- JMXConnector basic layout. +- javax.management.ObjectName support. +- Inclusion of .wsr as java-client into .ear, AxisService as java-client deployer in J2eeDeployer. - Naming Environment correctly set. - Stateless EJBProvider functionality -- Authentication propagation and security constraints for AxisServlet +- Authentication propagation and security constraints for AxisServlet. +- Integration of Axis-Beta-rc1 and the new WSDD format. TODO: -- Use the * role in order to authenticate users with a non-null credential, pass-through unassociated the others -- Home methods should be also callable (stateless case) -- Current Axis Beta (4?) +- Home methods should be also callable (stateless case). +- SecurityHandler that connects to JBoss Realm. +- MBeanProvider wsdl generation. - JMX mappings for other complex types, e.g., javax.management.Attribute - StatefulEJBProvider - EntityEJBProvider (do we need that anyway?) - Remote References via Axis/SOAP -- MBeanProvider wsdl generation. - AxisClient deployment - exception (de-)serialisation - JMSTransportProvider? Bugs: -- (5th October 2000) An IllegalStateException is produced when you try to access the AxisServlet?list command in a JBoss-Jetty -installation. Seems to be some misunderstanding between Axis and Jetty about what HTTP1.1 is. The HTTP-response -is nevertheless returned seemingly correctly. But that is IMHO already reported and patched in the Axis cvs. - + none currently known.
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
