[JBoss-dev] CVS update: contrib/jboss.net/docs README.html TODO

2002-04-09 Thread Dr. Christoph Georg Jung 

  User: cgjung  
  Date: 02/04/09 02:59:40

  Modified:jboss.net/docs README.html TODO
  Log:
  parameterizable typemappings.
  adopted latest subdeployer changes/patches from Mr. Maisey.
  
  Revision  ChangesPath
  1.10  +1 -1  contrib/jboss.net/docs/README.html
  
  Index: README.html
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- README.html   2 Apr 2002 13:48:35 -   1.9
  +++ README.html   9 Apr 2002 09:59:40 -   1.10
  @@ -311,7 +311,7 @@
   
   p class=textIn 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 and run the testsuite against a running jboss server as follows
  +You can build and run the testsuite against a running jboss server as follows 
(after having built the main jboss-all/testsuite!)
   
   code
   pre
  
  
  
  1.8   +1 -1  contrib/jboss.net/docs/TODO
  
  Index: TODO
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/TODO,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- TODO  2 Apr 2002 13:48:35 -   1.7
  +++ TODO  9 Apr 2002 09:59:40 -   1.8
  @@ -19,6 +19,7 @@
   li WSDL-generation for EJBProvider needs classloader adjustment. /li
   li EJBHomeProvider for exposing Home methods. /li
   li Advanced J2EE store example for testing functionality and .Net 
interoperability. /li
  +li TypeMapping parameters have been introduced. /li
   /ul
   
   H3TODO for 1.0 release/h3
  @@ -26,7 +27,6 @@
   li Finish order part of the store example./li 
   li MBeanProvider wsdl generation. /li
   li EJB-Refs should be either outsourced (different namespace, different file) or 
should be removed./li
  -li TypeMapping parameters must be introduced. /li
   li JMX mappings for other complex types, e.g., javax.management.Attribute /li
   li UDDI registry /li
   li call remove method on bean references hashed in the httpsession when session 
goes down. /li
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: contrib/jboss.net/docs README.html TODO

2002-03-15 Thread Dr. Christoph Georg Jung 

  User: cgjung  
  Date: 02/03/15 02:04:24

  Modified:jboss.net/docs README.html TODO
  Log:
  security for jboss.net has finally arrived (although the corresponding testcases 
still need
  to be checked-in).
  
  Revision  ChangesPath
  1.8   +25 -2 contrib/jboss.net/docs/README.html
  
  Index: README.html
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- README.html   12 Mar 2002 11:04:45 -  1.7
  +++ README.html   15 Mar 2002 10:04:24 -  1.8
  @@ -119,6 +119,27 @@
   Support for session-based entity bean access and suitable security models is 
envisaged. 
   /li
   
  +li class=text 
  +For the called web-service to correctly behave in the JBoss container, it is 
required that
  +the calling thread (usually taken from the WebServer´s threadpool) is associated 
with the correct classloader , i.e., 
  +the deployment classloader of the targetted service. For this purpose, we have 
fixedly installed two handlers 
  +codeorg.jboss.net.axis.SetClassLoaderHandler/code and
  +codeorg.jboss.net.axis.ResetClassLoaderHandler/code in the server´s http 
transport chain. The first handler is installed
  +in the requestFlow and 
  +remembers the old classloader in the messagecontext and associated the thread with 
the target service´s deployment classloader. 
  +The latter is installed in the responseFlow and resets the association to the old 
loader after a successful call. Upon failure in each flow, 
  +both handlers are able to reset the association.
  +/li
  +
  +li class=text 
  +Axis and JBoss Security models are connected via the two handlers 
codeorg.jboss.net.axis.server.JBossAuthenticationHandler/code and
  +codeorg.jboss.net.axis.server.JBossAuthorizationHandler/code. The first one is 
installed per-default in the http-transport
  +chain and maps the basic authentication data that has been extracted by a 
preceeding codeorg.apache.axis.transports.http.HTTPAuthHandler/code 
  +to a given JBoss security domain (as specified as a JNDI name in the handlers 
securityDomain parameter). The latter handler can
  +be inserted in the requestFlow of your particular Web-service to mimique a 
unix-style allow/denied roles authorization scheme (parameter
  +securityDomain as before, parameters allowedRoles and deniedRoles for 
controlling access to the 
  +specified web service. See the servers axis-config.xml for that purpose.
  +/li
   /ul
   
   JBoss.net is strongly connected to features of Jboss 3.0 (Rabbit Hole) and hence,  
  @@ -208,7 +229,8 @@
   (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=textWhen 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
  
  +p class=textWhen you start JBoss with the -Daxis.enableListQuery=true option 
(which you usually do not in a security-aware 
  +productive environment), 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:
   
  @@ -232,6 +254,7 @@
 lt;handler type=java:org.apache.axis.handlers.http.URLMapper /gt; 
 lt;handler type=java:org.apache.axis.handlers.http.HTTPAuthHandler /gt; 
 lt;handler type=java:org.jboss.net.axis.SetClassLoaderHandler /gt; 
  +  lt;handler type=java:org.jboss.net.axis.server.JBossAuthenticationHandler 
/gt; 
 lt;/requestFlowgt;
 lt;responseFlowgt;
 lt;handler type=java:org.jboss.net.axis.ResetClassLoaderHandler /gt; 
  @@ -249,7 +272,7 @@
   
   p class=textIn 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 and run the testsuite against a runnign jboss server as follows
  +You can build and run the testsuite against a running jboss server as follows
   
   code
   pre
  
  
  
  1.6   +33 -26contrib/jboss.net/docs/TODO
  
  Index: TODO
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/TODO,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- TODO  12 Mar 2002 11:04:45 -  1.5
  +++ TODO  15 Mar 2002 10:04:24 -  1.6
  @@ -1,29 +1,36 @@
  -DONE
  -- AxisService installation, WebContainer invocation.
  -- Axis logging configuration disabled.
  -- Axis extension to remember service classloader correctly.
  -- WSR-file structure and deployment.
  --

[JBoss-dev] CVS update: contrib/jboss.net/docs README.html TODO

2002-03-12 Thread Dr. Christoph Georg Jung 

  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  ChangesPath
  1.7   +40 -18contrib/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 -  1.6
  +++ README.html   12 Mar 2002 11:04:45 -  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 emWeb 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 quot;META-INF/web-service.xmlquot; entry.
   /li
   
  @@ -176,11 +176,12 @@
   are installed as a part of the above BUILD step.
 
   p class=textSince 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 
  +codeorg.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=textA a 
href=http://localhost:8080/axis/services?list;http://localhost:8080/axis/services?list/a
  
  +p class=textWhen 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
  -  lt;servicesgt;
  -   lt;service pivot=quot;JMXHandlerquot; name=quot;RemoteAdaptorquot;gt;
  -lt;option name=quot;ObjectNamequot; value=quot;Web:service=Adaptorquot; 
/gt; 
  +  lt;?xml version=1.0 encoding=UTF-8 ?gt; 
  +  lt;deployment xmlns=http://xml.apache.org/axis/wsdd/; 
xmlns:java=http://xml.apache.org/axis/wsdd/providers/javagt;
  +  lt;service name=RemoteAdaptor provider=Handlergt;
  +  lt;parameter name=handlerClass value=org.jboss.net.jmx.server.MBeanProvider 
/gt; 
  +  lt;parameter name=ObjectName value=jboss.net:service=Adaptor /gt; 
 lt;/servicegt;
  -  lt;/servicesgt;
  -/pre
  -
  -p class=textThis 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
  +  lt;service name=Administration provider=java:MSGgt;
  +  lt;parameter name=allowedMethods value=AdminService /gt; 
  +  lt;parameter name=isStatic value=true /gt; 
  +  lt;parameter name=methodName value=AdminService /gt; 
  +  lt;parameter name=enableRemoteAdmin value=false /gt; 
  +  lt;parameter name=className value=org.apache.axis.utils.Admin /gt; 
  +  lt;/servicegt;
  +  lt;transport name=httpgt;
  +  lt;requestFlowgt;
  +  lt;handler type=java:org.apache.axis.handlers.http.HTTPActionHandler /gt; 
  +  lt;handler

[JBoss-dev] CVS update: contrib/jboss.net/docs README.html

2002-02-27 Thread Dr. Christoph Georg Jung 

  User: cgjung  
  Date: 02/02/28 00:01:26

  Modified:jboss.net/docs README.html
  Log:
  runtime MBean invocations work again (detyped JMX is a pain!). Security
  tests removed, because hello bean does not support them anymore.
  
  Revision  ChangesPath
  1.6   +2 -2  contrib/jboss.net/docs/README.html
  
  Index: README.html
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- README.html   18 Feb 2002 09:14:32 -  1.5
  +++ README.html   28 Feb 2002 08:01:25 -  1.6
  @@ -138,7 +138,7 @@
   code
   pre
   cd build
  -build -Dmodules=plugins/jboss.net
  +build -Dmodules=jboss.net
   /pre
   /code
   
  @@ -231,7 +231,7 @@
   code
   pre
   cd build
  -build -Dmodules=plugins/jboss.net/testsuite tests
  +build -Dmodules=jboss.net/testsuite tests
   /pre
   /code
   
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: contrib/jboss.net/docs README.html

2002-02-18 Thread Dr. Christoph Georg Jung 

  User: cgjung  
  Date: 02/02/18 01:14:32

  Modified:jboss.net/docs README.html
  Log:
  updated jboss.net doco (finally!)
  
  Revision  ChangesPath
  1.5   +29 -59contrib/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 -   1.4
  +++ README.html   18 Feb 2002 09:14:32 -  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 slwly 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 - brNOT/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=headFeatures 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 codeorg.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.jspJetty/a or a 
ref=jboss-tomcat.jspTomcat/a). A configurable
  -codeorg.jboss.net.axis.AxisInvocationHandler/code eases the construction of 
detached
  +WebContainer (tested with a ref=jboss-jetty.jspJetty/a, afterwards also a 
ref=jboss-tomcat.jspTomcat/a). 
  +A configurable codeorg.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 emWeb 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 emWeb 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 quot;META-INF/web-service.xmlquot; entry.
   /li
   
  @@ -110,12 +111,12 @@
   li class=text 
   A specialised codeorg.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

[JBoss-dev] CVS update: contrib/jboss.net/docs README.html TODO

2002-02-04 Thread Dr. Christoph Georg Jung 

  User: cgjung  
  Date: 02/02/04 01:38:58

  Modified:jboss.net/docs README.html TODO
  Log:
  Adapted to latest deployment changes. Compiles, but does not yet run yet.
  
  Revision  ChangesPath
  1.4   +1 -0  contrib/jboss.net/docs/README.html
  
  Index: README.html
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- README.html   2002/01/03 04:00:54 1.3
  +++ README.html   2002/02/04 09:38:58 1.4
  @@ -204,6 +204,7 @@
 name=quot;jboss:service=Axisquot;gt;
   lt;attribute 
name=quot;WarDeployerNamequot;gt;jboss.web:service=Jettylt;/attributegt;
   lt;attribute name=quot;RootContextquot;gt;axis/lt;/attributegt;
  +lt;attribute 
name=quot;SecurityDomainquot;gt;java:/jaas/otherlt;/attributegt;
 lt;/mbeangt;
   
   lt;/servergt;
  
  
  
  1.4   +5 -1  contrib/jboss.net/docs/TODO
  
  Index: TODO
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/TODO,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- TODO  2001/10/07 20:06:11 1.3
  +++ TODO  2002/02/04 09:38:58 1.4
  @@ -9,12 +9,16 @@
   - 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
   
   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?)
   - JMX mappings for other complex types, e.g., javax.management.Attribute
   - StatefulEJBProvider
   - EntityEJBProvider (do we need that anyway?)
  -- Security model
  +- Remote References via Axis/SOAP
   - MBeanProvider wsdl generation.
   - AxisClient deployment
   - exception (de-)serialisation
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

[JBoss-dev] CVS update: contrib/jboss.net/docs README.html

2002-01-02 Thread Jason Dillon 

  User: user57  
  Date: 02/01/02 20:00:54

  Modified:jboss.net/docs README.html
  Log:
   o migrated all components to a new JMX domain name model.  jboss.system
 is now where to core/spine components live.  moved all components that
 were in JBOSS-SYSTEM that did not move into a jboss.* domain into
 jboss (where the server is now registered).  The point was to limit the
 members of jboss.system to core bits only.
   o Created org.jboss.system.Server, which does the work of initialization
 that org.jboss.Main used to do.  Main now only parses the command line,
 sets up basic legecy properties and creates a Server instance.
   o Moved functionality of Shutdown (component not cl tool) into Server (
 which is bound as jboss.system:service=Server)
   o Moved more Runtime access from Info into Server.  Exposed memory info
 as attributes.
   o Logging a WARN everywhere that uses System.getProperty(jboss.system.home)
 as that should go away soon/eventually.
   o Initialized the invokerMap in the harmi impl to avoid NPE
   o Made getopt.jar a member of the lib/* dir instead of adding it to the
 run.jar and shutdown.jars each time.
   o Minor cosmetic changes along the way.
  
  Revision  ChangesPath
  1.3   +11 -11contrib/jboss.net/docs/README.html
  
  Index: README.html
  ===
  RCS file: /cvsroot/jboss/contrib/jboss.net/docs/README.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- README.html   2001/10/12 12:17:48 1.2
  +++ README.html   2002/01/03 04:00:54 1.3
  @@ -179,12 +179,12 @@
   you have to give it a reference to JBoss.net´s Axis service (in 
conf/default/jboss-service.xml)
   
   pre
  -   lt;mbean code=quot;org.jboss.deployment.AutoDeployerquot; 
name=quot;JBOSS-SYSTEM:service=AutoDeployerquot;gt;
  +   lt;mbean code=quot;org.jboss.deployment.AutoDeployerquot; 
name=quot;jboss:service=AutoDeployerquot;gt;
  lt;attribute name=quot;Deployersquot;gt;
  -  JBOSS-SYSTEM:service=ServiceDeployer;
  -  JCA:service=RARDeployer;
  -  J2EE:service=J2eeDeployer;
  -  JBOSS-SYSTEM:service=Axis
  +  jboss.system:service=ServiceDeployer;
  +  jboss.jca:service=RARDeployer;
  +  jboss.j2ee:service=J2eeDeployer;
  +  jboss:service=Axis
   lt;/attributegt;
   ...
  lt;/mbeangt;
  @@ -198,11 +198,11 @@
   
   lt;servergt;
   
  -  lt;dependsgt;JBOSS-SYSTEM:service=Jettylt;/dependsgt;
  +  lt;dependsgt;jboss.web:service=Jettylt;/dependsgt;
   
 lt;mbean code=quot;org.jboss.net.axis.server.AxisServicequot;
  -  name=quot;JBOSS-SYSTEM:service=Axisquot;gt;
  -lt;attribute 
name=quot;WarDeployerNamequot;gt;JBOSS-SYSTEM:service=Jettylt;/attributegt;
  +  name=quot;jboss:service=Axisquot;gt;
  +lt;attribute 
name=quot;WarDeployerNamequot;gt;jboss.web:service=Jettylt;/attributegt;
   lt;attribute name=quot;RootContextquot;gt;axis/lt;/attributegt;
 lt;/mbeangt;
   
  @@ -217,11 +217,11 @@
   pre

 lt;mbean code=quot;org.jboss.deployment.J2eeDeployerquot;
  -  name=quot;J2EE:service=J2eeDeployerquot;gt;
  +  name=quot;jboss.j2ee:service=J2eeDeployerquot;gt;
   lt;attribute name=quot;DeployerNamequot;gt;Defaultlt;/attributegt;
   lt;attribute 
name=quot;JarDeployerNamequot;gt;:service=ContainerFactorylt;/attributegt;
  -lt;attribute 
name=quot;WarDeployerNamequot;gt;JBOSS-SYSTEM:service=Jettylt;/attributegt;
  -lt;attribute 
name=quot;JavaDeployerNamequot;gt;JBOSS-SYSTEM:service=Axislt;/attributegt;
  +lt;attribute 
name=quot;WarDeployerNamequot;gt;jboss.web:service=Jettylt;/attributegt;
  +lt;attribute 
name=quot;JavaDeployerNamequot;gt;jboss:service=Axislt;/attributegt;
 lt;/mbeangt;
   
   /pre
  
  
  

___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development