Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
10.21.3. XML Registries
J2EE 5.0 mandates support for Java API for XML Registries (JAXR). Inclusion of a XML Registry with the J2EE 5.0 certified Application Server is optional. JBoss EAP ships a UDDI v2.0 compliant registry, the Apache jUDDI registry. JAXR Capability Level 0 (UDDI Registries) is also supported through Apache Scout integration.
Section 10.21.3, “XML Registries” describes how to configure the jUDDI registry in JBoss and some sample code outlines for using JAXR API to publish and query the jUDDI registry.
10.21.3.1. Apache jUDDI Configuration Link kopierenLink in die Zwischenablage kopiert!
Link kopierenLink in die Zwischenablage kopiert!
jUDDI registry configuration happens via a MBean Service that is deployed in the
juddi-service.sar
archive in the all
server profile. The configuration of this service can be done in the jboss-service.xml
of the META-INF
directory in the juddi-service.sar
Let us look at the individual configuration items that can be changed.
DataSources configuration
<!-- Datasource to Database --> <attribute name="DataSourceUrl">java:/DefaultDS</attribute>
<!-- Datasource to Database -->
<attribute name="DataSourceUrl">java:/DefaultDS</attribute>
Database Tables (Should they be created on start, Should they be dropped on stop, Should they be dropped on start etc)
JAXR Connection Factory to be bound in JNDI. (Should it be bound? and under what name?)
Other common configuration:
Add authorized users to access the jUDDI registry. (Add a sql insert statement in a single line)