Hi,
before 3.2 final
will be built, the following bugs have been addressed in Branch_3_2 and
HEAD:
Bug#638994 -
JBossAuthenticationHandler can now handle null-passwords if the associated
SecurityDomain does.
Bug#594137 - A
special HttpActionHandler has been installed in the default http transport chain
that will signal its presence to any passing messagecontext requesting to
generate WSDL. This way, supporting providers (such as our EJBProvider and the
MBeanProvider) can include the correct SoapAction="ServiceName" annotations
depending on the transport through which the wsdl request came
through.
Bug#708691 - The
central Deployment repository has been added additional classloader awareness
when trying to obtain the
service descriptions
for generating the http://localhost:8080/jboss-net/services
HTML overview page.
Bug#617517 - The
MBeanProvider has been reworked. We have removed the nasty string array of
classnames that was required as the first parameter of each web service
invocation, because it operates on MBeanInformation meta-data anyway. The
generated WSDL is now much more straightfoward and
correct.
Finally I have
removed the automatic insertion of transactional handlers for ejb-web
services from the xdoclet module. These are only needed, if you like to
immediately (de-)serialize entity beans into/from XML elements within the scope
of some session bean method.
If you would like to
retain them, you have to annotate your bean with the @jboss.net:processEntities
tag.
Please keep on
providing valuable feedback to us,
CGJ
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
