You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Federica Ciotti (JIRA)" <ju...@ws.apache.org> on 2006/12/07 13:21:21 UTC
[jira] Created: (JUDDI-94) AxisHandler
AxisHandler
-----------
Key: JUDDI-94
URL: http://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
Assigned To: Steve Viens
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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org
[jira] Closed: (JUDDI-94) AxisHandler
Posted by "Jeff Faath (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Faath closed JUDDI-94.
---------------------------
Resolution: Invalid
jUDDI no longer uses the classes in the org.apache.juddi.transport.axis package. As far as I can tell, this has been the case for a while now (since before I started working with jUDDI a couple years ago). Handling of requests by the jUDDI "server" are done via classes that extend HttpServlet in the org.apache.juddi.registry package. jUDDI uses Axis (or Axis2) in this regard only for its implementation of SAAJ (while parsing the requests and responses).
Client requests made from the jUDDI API to an external server, however, use one of the transport classes found in the org.apache.juddi.proxy package. The transport class used is configurable in the juddi.properties file.
> 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
[jira] Assigned: (JUDDI-94) AxisHandler
Posted by "Kurt Stam (JIRA)" <ju...@ws.apache.org>.
[ 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
[jira] Commented: (JUDDI-94) AxisHandler
Posted by "Federica Ciotti (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466987 ]
Federica Ciotti commented on JUDDI-94:
--------------------------------------
juddi is deployed like a servet in tomcat, so why I need to register it with the Axis handler?
I have no clear idea about the relationships among juddi, tomcat and axis.
Could you help me?
> 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
> Assigned To: Steve Viens
>
> 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