Dr. Jung, I've been working on Flash being a SOAP client. I didn't realize
how brain dead Macromedia's XML implementation was. There is no namespace
support (it gets confused), no types other than string for which you don't
specify the type, and no validation. However, I still think it will be a
valuable feature.
I believe this can be done by telling the MessageContext to not use
namespace prefixes in the elements of the response. Please correct me if I
am wrong. The code and doc seem to indicate this requires a handler to be
written and then specified in the Axis engine configuration, which is done
in the axis-config.xml file (<responseFlow>) in the ./server/default/conf
directory. The problem is that the top level element is <deployment> which
appears to allow only one Axis Engine to be configured. Its name is
"JBoss.net". This file is actually loaded in the class AxisService [line
200-212] creating a AxisServer (engine) class instance into the data member
"axisServer". So it appears that the AxisService which is also the Axis
deployer only supports one engine and thus only one set of handlers.
Looking at the AxisServiceServlet class, it looks like you intended to
allow each ServletContext to specify a different engine [line
40]. However, this would require that each Servlet configuration
(install-axis.xml) to specify an attribute which would be an XML file that
would effectively be the axis-config.xml file (the Axis engine
configuration specifying handlers). As you have already done, if the
AXIS_ENGINE_ATTRIBUTE ("AxisEngine") attribute in the ServletConfig is not
set, the engine is created, and the attribute set with the engine
instance. The axis-config.xml type file would be exist in the jboss-net.sar.
It doesn't seem that it would be additional overhead to have multiple
"engines" which are just chains of handlers. I'm not sure, but it seems
like this change would also allow support of multiple security
configurations. What are your thoughts on this? Thank you again.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
