Bug 779277 (SOA-1666) - jUDDI v3 needs "Dynamic Registration of supported UDDIv3 endpoints"
Summary: jUDDI v3 needs "Dynamic Registration of supported UDDIv3 endpoints"
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1666
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: jUDDI - within SOA
Version: 5.0.0 ER4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.0.0 ER8
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-03 19:49 UTC by Len DiMaggio
Modified: 2010-02-10 15:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-10 15:07:38 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1666 0 None None None Never

Description Len DiMaggio 2009-12-03 19:49:13 UTC
Date of First Response: 2009-12-16 13:33:43
project_key: SOA

See:  http://issues.apache.org/jira/browse/JUDDI-316

Right now - the seed data is static.

Comment 1 Kurt Stam 2009-12-16 18:33:43 UTC
Should be addressed in 3.0.1 due mid January. 

Comment 2 Kevin Conner 2010-01-26 13:46:15 UTC
Link: Added: This issue depends JBESB-3156


Comment 3 Kevin Conner 2010-01-27 09:36:32 UTC
This is now supported in 3.0.1, integrated into the ESB codebase.

Comment 4 Kurt Stam 2010-02-03 14:47:26 UTC
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

Comment 5 Len DiMaggio 2010-02-04 21:03:20 UTC
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
	




Comment 6 Kevin Conner 2010-02-05 10:19:15 UTC
Len, is your last comment for this bug?

Comment 7 Len DiMaggio 2010-02-05 15:53:01 UTC
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!


Comment 8 Kevin Conner 2010-02-05 15:58:21 UTC
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.

Comment 9 Len DiMaggio 2010-02-10 15:07:38 UTC
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>



Note You need to log in before you can comment on or make changes to this bug.