-
30. Re: ProfileService equiv to ServiceBindingManager
Ok so I built and moved the jboss-bindingsservice.jar to the jboss.lib.url so that it picks the library up during bootstrapping. However when I startup the server I get a ClassCastException when trying to install the ServiceBindingStore. I am guessing this has something to do with ServiceBindingSet being a subclass of HashSet and being passed to the PojoBindingServiceStore. I am going try modifying the implementation and rebuilding.
-
31. Re: ProfileService equiv to ServiceBindingManager
Are you trying to use this in an earlier release of the AS?
-
32. Re: ProfileService equiv to ServiceBindingManager
I am working with CR1 and the nightly build version of CR2. Let me try using only the CR2 from the nightly build.
-
33. Re: ProfileService equiv to ServiceBindingManager
Better plan. :-) I made no attempt to make this compatible with CR1.
-
34. Re: ProfileService equiv to ServiceBindingManager
I'm adding a simple service to bindings.xml that can convert ServiceBindingManager values into system properties.
<!-- Conversion of selected bindings into system properties --> <bean name="SystemPropertyBinder" class="org.jboss.services.binding.SystemPropertyBinder"> <constructor> <parameter> <set> <!-- JBM's remoting connector --> <bean class="org.jboss.services.binding.SystemPropertyBinding"> <constructor> <parameter>jboss.messaging.connector.bisocket.port</parameter> <parameter class="int"> <value-factory bean="ServiceBindingManager" method="getIntBinding" parameter="jboss.messaging:service=Connector,transport=bisocket"/> </parameter> </constructor> </bean> </set> </parameter> </constructor> </bean>
This is to support the JBM usage discussed at http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169967#4169967. I imagine it might be useful for some other cases as well; perhaps JGroups configurations where users want strictly defined ports rather than letting JGroups find an available port. JGroups uses custom parsing of its protocol stack configurations, so system properties are the only mechanism for passing in dynamic values.
Downside to this approach is the consuming service no longer has an explicit dependency on the SBM (which is also the upside ;-) ). But, the Naming service depends on SBM, so SBM is always going to deploy very early. If services using this system property approach are careful and understand their dependency relationships, this should be safe enough. -
35. Service deployment failing due to ServiceBindingManager?
Is the inability of the URLDeploymentScanner to load some of the package sevices in the deploy directory caused by the new configuraiton setings done via the bindings.xml? My instance of the nightly build of CR2 is unable to load the TomcatServiceMBean class.
-
36. Re: ProfileService equiv to ServiceBindingManager
You'll need to provide more details on the problem you are seeing.
I haven't seen any issues related to SBM. I just updated my trunk checkout, built and started; no problem. And the last hudson testsuite run showed no problem:
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSuite-sun15/825/testReport/