[prev in list] [next in list] [prev in thread] [next in thread] 

List:       juddi-dev
Subject:    [jira] Assigned: (JUDDI-94) AxisHandler
From:       "Kurt Stam (JIRA)" <juddi-dev () ws ! apache ! org>
Date:       2007-07-27 15:34:19
Message-ID: 23960113.1185550459411.JavaMail.jira () brutus
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/JUDDI-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Kurt Stam reassigned JUDDI-94:
------------------------------

    Assignee: Jeff Faath  (was: Steve Viens)

> AxisHandler
> -----------
> 
> Key: JUDDI-94
> URL: https://issues.apache.org/jira/browse/JUDDI-94
> Project: jUDDI
> Issue Type: Improvement
> Affects Versions: 0.9rc4
> Environment: Linux Fedora5, tomcat 5.5.20, java1.5.0_0.9, Axis2 1.0
> Reporter: Federica Ciotti
> Assignee: Jeff Faath
> 
> In this article http://www.devx.com/java/Article/21390/0/page/4 
> I found out that "
> jUDDI uses Apache Axis to handle SOAP messaging. Axis defines a transparent \
> transport framework that allows different transport protocols to be used. For the \
> HTTP protocol, any servlet derived from the \
> org.apache.axis.transport.http.AxisServlet class is a candidate for handling HTTP \
> requests. In jUDDI, three servlets extend the AxisServlet class: 1. \
> org.apache.juddi.transport.axis.AdminServlet 2. \
> org.apache.juddi.transport.axis.PublishServlet 3. \
> org.apache.juddi.transport.axis.InquiryServlet This all seems quite \
> straightforward, however, there is a slight twist?jUDDI registers these three \
> classes as servlets with an application server, but only uses them to determine the \
> type of request that is made. The actual processing is handled by the \
> org.apache.juddi.transport.axis.AxisHandler class which must be registered with the \
> Axis handler-chain." How can this registration with the Axis handler-chain be \
> archived? And what is the role of the three sevlet?
> Thanks 
> Federica

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]