User: cgjung Date: 01/10/03 06:20:30 Modified: jboss.net/docs README TODO Log: restructured server/client parts, invocationhandler support. MBeanProvider for exposing MBeans as web-services. JMXConnector. Revision Changes Path 1.2 +21 -30 contrib/jboss.net/docs/README Index: README =================================================================== RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- README 2001/09/29 16:17:07 1.1 +++ README 2001/10/03 13:20:30 1.2 @@ -1,9 +1,10 @@ JBoss.net --------- -This is an optional plugin that enables JBoss to deploy and run Web-Services speaking XML-based -interoperability protocols and packaged in so-called WSR (Web-Service aRchive)-files. JBoss.net -is currently based on a slightly modified Apache Axis 1.0 2nd Alpha Release located under +JBoss.net is an optional plugin that enables JBoss to deploy and run Web-Services speaking XML-based +interoperability protocols. The web services are packaged in so-called WSR (Web-Service aRchive)-files. + +JBoss.net is currently based on a slightly modified Apache Axis 1.0 2nd Alpha Release located under thirdParty/apache/axis. For how to write Java-Code and how to specify deployment meta-data for that purpose, please have a look at http://xml.apache.org/axis/. @@ -34,10 +35,10 @@ To INSTALL: -Currently, JBoss.net relies on a http-based transport layer that requires an installed WebContainer -(Tomcat, Jetty; JBoss.net has currently been tested under Jetty). The necessary runtime libraries (including -the JBossDotnet.sar service archive) and configuration files for a JBoss-Jetty distribution -are installed as a part of the above BUILD step. +JBoss.net relies requires a WebContainer installation (Tomcat, Jetty; JBoss.net has currently +been tested under Jetty) to realize the http transport facility. The necessary runtime +libraries (including the jbossdotnet.sar service archive) and the configuration files for +a JBoss-Jetty distribution are installed as a part of the above BUILD step. If you would like to enable the AutoDeployer functionality for WSR-files, you have to add a reference JBoss.net�s Axis service @@ -61,27 +62,10 @@ <server> <depends>JBOSS-SYSTEM:service=Jetty</depends> - - <classpath archives="axis.jar,javax.servlet.jar"/> - <!-- ==================================================================== --> - <!-- Starts the Axis Deployer --> - <!-- ==================================================================== --> - - <!-- - | Uncomment to enable the Axis service. - | - | Besure to check that the configuration values are valid for your - | environment. - | - | If you want to enable several services, be sure that you choose - | different root contexts - | - --> - <mbean code="org.jboss.net.axis.AxisService" + <mbean code="org.jboss.net.axis.server.AxisService" name="JBOSS-SYSTEM:service=Axis"> <attribute name="WarDeployerName">JBOSS-SYSTEM:service=Jetty</attribute> - <attribute name="RootContext">axis</attribute> </mbean> </server> @@ -94,17 +78,24 @@ ${RootContext} is the URL infix, defaults to "axis" under which the deployed Web-Services can be reached). After that, pointing your browser to http://${machine}:8080/axis/servlet/AxisServlet should return the -default hello message of the servlet. +default hello response page of the servlet. -Under plugins/jboss.net/output/lib/addr.wsr, the BUILD will also have packaged one standard sample of Axis, -the AddressBook example, into a WSR-file. If you put it into the jboss deploy directory, the auto-deployer should -contact the Axis service and tear up the AddressBook Web-Service. +Under deploy/addr.wsr, the BUILD will also have packaged one standard sample of Axis, the AddressBook example, +as a WSR-file. The modified auto-deployer (see above) should contact the Axis service and tear up the AddressBook +Web-Service, automatically. -You can now run the corresponding client application against it +You can now run the standard client application against it cd thirdParty/apache/axis java -classpath ./;lib/axis.jar;../log4j/lib/log4j.jar;../../sun/jaxp/lib/crimson.jar sample.addr.Main +Shipped with the default configuration comes a pre-installed "JMXConnector" WebService that exports +JMX server management to arbitrary SOAP-clients (currently, the datatype mappings are still a bit +restricted). The testAxis.bat will try to run three different types of clients (general invocation, +mbean-specific invocation, typed invocation) agains the server and each should return the default +domain of the JBoss mbean server ("JBOSS-SYSTEM") and the successful deployment of the AxisService MBean +("true"). + PROBLEMS : Axis questions should be directed to [EMAIL PROTECTED] 1.2 +11 -4 contrib/jboss.net/docs/TODO Index: TODO =================================================================== RCS file: /cvsroot/jboss/contrib/jboss.net/docs/TODO,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- TODO 2001/09/29 16:17:07 1.1 +++ TODO 2001/10/03 13:20:30 1.2 @@ -3,15 +3,22 @@ - 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 TODO: -- AxisJMXAdaptor -- ContainerInvoker, InvocationHandler -- Inclusion into .ear and J2eeDeployer, Hitting EJB�s. +- JMX mappings for other complex types, e.g., javax.management.Attribute +- Inclusion of .wsr into .ear and J2eeDeployer +- EJBProvider functionality +- Security models +- MBeanProvider wsdl generation. +- AxisClient deployment +- exception (de-)serialisation - JMSTransportProvider? Bugs: -- An IllegalStateException is produced when you try to access the AxiServlet?list command in a JBoss-Jetty +- 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.
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
