W E B   S E R V I C E S  

JBoss.Net comes with a set of suitable handlers which use the JBoss infrastructure to 

perform useful processing tasks, such as authentication, authorization, transaction 

management, classloading and the like.   

Finally, JBoss.Net contains special purpose type mappings and serialization hooks to 

tie particular Web Service clients, such as Macromedia Flash and Microsoft .Net 

applications, to the JBoss server. This is an ongoing effort. 

Picture of the integration   CGJ 

Installation   PB 

JBoss.Net is packaged as a service archive file called 

jboss net.sar

. It deploys 

automatically with JBoss with a default configuration: 

4. registers with the MainDeployer 

5. installs the Servlet in the WebContainer 

6. some basic type mappings 

Configuration   FB 

The default configuration can be modified by editing the JBoss.Net configuration file found 

inside the sar as 

jboss net.sar/META INF/jboss service.xml

.  To modify it, first 

unpack the sar, make your changes, repack it and copy it back to the deploy directory. JBoss 

will reload and restart JBoss.Net with it s new configuration.  Alternatively, for non 

permanent configuration changes, you can use the JMX Agent on port 8082.  

The default JBoss.Net 

jboss service.xml

 file looks like: 

Basic Security 

How to set the main security domain and shield the servlet. 

Using Tomcat as the WebContainer 

Change the dependency 

Building A Pojo Web Service with JBoss.Net   FB 

How to bundle wsdd. How to obtain wsdl. 

130