| Summary: | jUDDI v3 needs "Dynamic Registration of supported UDDIv3 endpoints" | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Len DiMaggio <ldimaggi> |
| Component: | jUDDI - within SOA | Assignee: | Kurt Stam <kurt.stam> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 ER4 | ||
| Target Milestone: | --- | ||
| Target Release: | 5.0.0 ER8 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1666 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-02-10 15:07:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Len DiMaggio
2009-12-03 19:49:13 UTC
Should be addressed in 3.0.1 due mid January. Link: Added: This issue depends JBESB-3156 This is now supported in 3.0.1, integrated into the ESB codebase. This is now dynamic. endpoint variables such a hostname and port are now resolved at runtime, rather then install time. https://issues.apache.org/jira/browse/JUDDI-316 I am not seeing this as fixed in ER8: ./server/default/deploy/jbossesb-registry.sar/esb.juddi.xml <!-- The maximum number of UDDI artifacts allowed --> <!-- per publisher. A value of '-1' indicates any --> <!-- number of artifacts is valid (These values can be --> <!-- overridden at the individual publisher level). --> <entry key="juddi.maxBusinessesPerPublisher">25</entry> <entry key="juddi.maxServicesPerBusiness">20</entry> <entry key="juddi.maxBindingsPerService">10</entry> <entry key="juddi.maxTModelsPerPublisher">100</entry> [ldimaggi@ldimaggi jboss-as]$ grep -r maxBusinessesPerPublisher * samples/quickstarts/helloworld_ejb3_ws/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/xsd_validation/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/JAAS_action/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/swift2xml_action/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/xml2swift_action/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/wsmq_router/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/opensso/juddi.properties:juddi.maxBusinessesPerPublisher=25 samples/quickstarts/helloworld_ejb3_ws_wss/juddi.properties:juddi.maxBusinessesPerPublisher=25 server/all/deploy/jbossesb-registry.sar/esb.juddi.xml: <entry key="juddi.maxBusinessesPerPublisher">25</entry> server/production/deploy/jbossesb-registry.sar/esb.juddi.xml: <entry key="juddi.maxBusinessesPerPublisher">25</entry> server/default/data/esb.juddi.properties:juddi.maxBusinessesPerPublisher=25 As seen in the jUDDI UI: Max Businesses: 100 Max Service Per Business: 1000 Max Bindings Per Service: 100 Max TModels: 100 Len, is your last comment for this bug? Yes - based on this conversation: KurtStam:have you register endpoints with parameters in them; like we do in the default seed data KurtStam:then you can change the value of the parameter in the juddiv3.properties file KurtStam:and it should use the new values lndimaggio: ah - ok! lndimaggio: where is the juddiv3.properties file? KurtStam:I think is called uddi.esb.xml or something KurtStam:in jbossesb-registry.sar lndimaggio: great - thanks! I don't think that is the same, the dynamic endpoint registration refers to the access points similar to the following
<accessPoint useType="wsdlDeployment">${juddi.server.baseurl}/juddiv3/services/subscription-listener?wsdl</accessPoint>
What you seem to be discussing above is to do with other properties.
The juddi.server.baseurl token is now set in the juddiv3.properties file: e.g., in: server/default/deploy/jbossesb-registry.sar/esb.juddi.xml <entry key="juddi.server.baseurl">http://${jboss.esb.bind.address}:8080</entry> |