Home >> All >> org >> jboss >> net >> axis >> [ server Javadoc ]

• org.jboss.net.axis.server: Javadoc index of package org.jboss.net.axis.server.


Package Samples:

• org.jboss.net.axis.server: This package contains server- as well as client-side glue code to integrate the Axis project into JBoss.  

Classes:

• EJBProvider: A JBoss-compatible EJB Provider that exposes the methods of any session bean as a web service endpoint. Basically it is a slimmed downed derivative of the Axis-EJBProvider without the usual, corba-related configuration mumbo-jumbo that is operating under the presumption that the right classloader has already been set by the request flow chain (@see org.jboss.net.axis.SetClassLoaderHandler). Since Version 1.5 and thanks to Kevin Conner, we now also support stateful beans that are tied to the service scope (you should reasonably choose scope="session" in the tag of the corresponding web-service.xml) ...
• JBossAuthenticationHandler: AuthenticationHandler that interacts with a given JBoss autentication manager via default simple principals and passchars from the HTTP Basic Authentication. It is derived from org.apache.axis.handlers.SimpleAuthenticationHandler. Note that this is somehow redundant to the WebContainer security, but we want to be able to install different authentication schemes for different web services behind a single entry-point. Per default, unauthenticated calls will be routed by NOT asking the jboss auth manager for validation (most domains still would refuse NobodyPrincipal, no matter how configured) and ...
• FlashAxisServiceServlet: A AxisServlet that allows the Flash player/plugin to interact with the Axis SOAP engine despite the inability to generate the SOAPAction HTTP header. It spoofs the header by looking at the request parameters and generating a derived HttpServletRequestWrapper class to appear to migrate those that should actually be HTTP headers into the header. This class then just calls its base class's implementation of doPost(). For example, if you were invoking the Hello World SOAP example, you would append: ?SOAPAction=\"Hello\" to the service context: /axisflash/flashservices/Hello Change History jung, 02.05.2002: ...
• JBossAuthorizationHandler: AuthorizationHandler that checks allowed and denied roles against the active subject using a given realmMapping. Is somehow redundant to what, e.g., the JBoss EJB invocation handler does, but maybe we need this to shield access to other container resources such as MBeans for which we will expose security-agnostic providers. Change History jung, 15.03.2002: Added security domain option. To Do jung, 14.03.2002: Cache simple principals. Principal factory for interacting with various security domains.
• FlashNamespaceHandler: This class implements the Apache Axis Handler interface. As such, it is inserted into the chain of Axis Engine Handlers by specifying it in the axis-config.xml file of the jboss-net-flash.sar file. This particular handler flags the generated SOAP Envelope to not include namespace declarations. This is because Flash versions 5 and MX do not support namespaces and only support simple strings. Change notes
• EJBHomeProvider: A JBoss-compatible Provider that exposes the methods of a beanīs home, such as a stateless session bean or an entity bean. It is working under the presumption that the right classloader has already been set by the invocation chain (@see org.jboss.net.axis.SetClassLoaderHandler). Change History To Do jung, 22.03.02: Service-Reference serialisation.
• TransactionRequestHandler: This handler is to create an artifical "client"-side transaction around the web-service request. Useful for interacting with entity beans. It should be complemented by a seperate org.jboss.net.axis.server.TransactionResponseHandler in the response chain to finish the transaction. Change notes
• WsdlAwareHttpActionHandler: This HttpActionHandler will influence the wsdl-generation of action aware service providers, such as EJBProvider .
• EntityBeanDeserializer: Server-side deserializer hitting an existing entity bean. Derived from the axis BeanDeserializer. Currently relies on some silly conventions that must be configurable in the deployment descriptor.
• AxisServiceServlet: An AxisServlet that is able to extract the corresponding AxisEngine from its installation context and builds the right message contexts for the JBoss classloading and deployment architecture.
• SerialisationResponseHandler: This handler is to force serialisation inside transaction and security boundaries. Change notes
• TransactionResponseHandler: This handler is to finish a previously opened client-side transaction. Change notes
• JMXEngineConfigurationFactory: A configuration factory that accesses axis server engines via JMX attribute access.
• AxisService: A deployer service that installs Axis and manages Web-Services within JMX.
• JMXEngineConfigurationProvider: configuration provider that accesses configuration services via JMX.
• AxisAdminServlet: slightly patched admin servlet to contact the right server
• EntityBeanDeserializerFactory: Factory for server-side Entity Bean Deserialization.
• Constants: Some Constants for the server package
• AxisServiceMBean: Mbean interface to the AxisService

Home | Contact Us | Privacy Policy | Terms of Service