Ah, the dangers of reflection.
In the course of working on JBREM-727 ("Make Client's implicitly created Connectors accessible") I changed the field Client.callbackConnectors to map from an InvokerCallbackHandler to the *set* of all the Connectors with which it is registered. Since Messaging's JMSRemotingConnection always creates a new InvokerCallbackHandler (CallbackManager, in particular) for each connection, callbackConnectors should map each CallbackManager to a singleton set. I.e.,
| Connector connector = (Connector)callbackConnectors.get(callbackHandler);
|
should be
| Connector connector = (Connector)callbackConnectors.get(callbackHandler).iterator().next();
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030428#4030428
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030428
The problem of ordering notifications can likely be solved.
Another issue is whether this kind of restart-on-merge behavior should be configurable or even turned on by default. HA-JMS needs this; for other use cases having the singleton restart may be undesirable. This is particularly an issue with the HASingletonDeployer mbean, since a restart there means redeploying everything in deploy-hasingleton, a potentially lengthy process.
I've no problem with adding a config flag for this, although that complicates backporting it for CP releases.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030411#4030411
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030411
"alesj" wrote :
| But what's the problem with relaying on jbossbuild?
|
In the long run maven will be easier to maintain, and we get several features that we don't have now (better dependency management, automated releases, project inheritance, etc). If we have them both side by side it will be difficult to keep them in sync.
What are the features that you have with ant? Maybe we can come up with something similar in maven.
Generating a build.xml from the maven pom (using the plugin that Kevin mentioned) can be done with "mvn ant:ant". We can do this for now if needed, but my goal is that eventually it won't be necessary.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030388#4030388
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030388
I added version 2-SNAPSHOT of the parent pom to the repository that includes the eclipse plugin configuration.
I also added a 1.1 version of the jboss-deploy plugin that will deploy all artifacts attached to a project (including aggregates). I added this to the pluginManagement section of the parent. This means that it is not enabled by default in the child poms. To enable the deploy plugin in child projects, you just have to reference it in the plugins section like this:
| <plugins>
| <plugin>
| <groupId>jboss.maven-plugins</groupId>
| <artifactId>jboss-deploy-maven-plugin</artifactId>
| </plugin>
| </plugins>
|
Or you can just copy the configuration from the parent.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030375#4030375
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030375