[Design of Messaging on JBoss (Messaging/JBoss)] - Re: [JBMESSAGING-1367] Create JCA resource adapter for JBM 2
by jesper.pedersen
anonymous wrote : I'm not sure what you mean. That is an instance of the interface...
Ok, so I need to pass discoveryGroupName and discoveryGroupPort in through the configuration.
anonymous wrote : Can you explain a bit more what endpoint isn't available means?
In this case it would be that a Message Driven Bean (endpoint) isn't available or failed to handle the incoming message.
| public void onMessage(Message message)
| {
| try
| {
| endpoint.beforeDelivery(JBMActivation.ONMESSAGE);
|
| try
| {
| if (dlqHandler == null
| || dlqHandler.handleRedeliveredMessage(message) == false)
| {
| MessageListener listener = (MessageListener) endpoint;
| listener.onMessage(message);
| }
| } finally
| {
| endpoint.afterDelivery();
|
| if (dlqHandler != null)
| dlqHandler.messageDelivered(message);
| }
| }
|
| catch (Throwable t)
| {
| log.error("Unexpected error delivering message " + message, t);
|
| if (txnStrategy != null)
| txnStrategy.error();
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194105#4194105
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4194105
17 years, 4 months
[Design of POJO Server] - Re: Why do Topic/Queue descriptors need extra metadata in or
by alesj
I've changed it to be more OO + use newly added mechanisms.
e.g. QueueMODefinition
| public class QueueMODefinition extends ManagedObjectDefinition
| {
| private static Logger log = Logger.getLogger(QueueMODefinition.class);
|
| public QueueMODefinition(ManagedObjectFactory factory)
| {
| super(QueueService.class, new QueueMOBuilder(factory));
| }
|
| private static class QueueMOBuilder implements ManagedObjectBuilder
| {
| private ManagedObjectFactory factory;
|
| private QueueMOBuilder(ManagedObjectFactory factory)
| {
| this.factory = factory;
| }
|
| /**
| * Create a ManagedObject from QueueService to QueueServiceMO.
| *
| * @param clazz - the mbean class to create the ManagedObject for
| * @param metaData - the MDR MetaData view
| */
| public ManagedObject buildManagedObject(Class<?> clazz, MetaData metaData)
| {
| ManagedObjectFactory mof = getMOFactory();
| log.debug("Creating QueueServiceMO template for: " + clazz);
| return mof.createManagedObject(QueueServiceMO.class, metaData);
| }
|
| /**
| * Get MO factory.
| *
| * @return the MO factory
| */
| protected ManagedObjectFactory getMOFactory()
| {
| if (factory == null)
| factory = ManagedObjectFactory.getInstance();
|
| return factory;
| }
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193940#4193940
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193940
17 years, 4 months
[Design of JBoss Deployment Framework] - Re: Designing of jain-slee deployers for Jboss5.
by alesj
"alexandrem" wrote :
| Hope so! It's a must-have feature, IMO. :)
|
- https://jira.jboss.org/jira/browse/JBDEPLOY-135
"alexandrem" wrote :
| This looked like a good option... but we start at PARSE phase, and that seems like an issue, cause adding the jboss-dependency.xml didn't solved the problem.
|
Looks like you're doing too much in PARSE.
Like the stage name says, it should be just parsing. ;-)
That's why I put jboss-dependency.xml handling asap,
so it can add dependencies to as much as stages as possible.
You should split your deployment into more fine grained deployers per stages.
"alexandrem" wrote :
| One other thing I've noticed and would like some help on it, is the fact that the jars are not exploded anymore into a tmp folder, the reference to them now comes as, and using the above example, .../server/default/deploy/a.jar/a1.jar and .../server/default/deploy/a.jar/a2.jar instead of the old way .../server/default/tmp/deploy/tmpXXXXXa.jar-contents/a1.jar. We used JarFile/JarEntry to handle it but now it fails due to those references not being a valid path for JarFile/JarEntry. I've managed a workaround for it, having a wrapper for the DeploymentUnit which will then enable me to return an InputStream to read the files... but not sure this is a good practice.
|
There is this discussion:
- http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146597
But if you ask me,
you should just drop the old way (JarFile/Entry) and use VFS.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193936#4193936
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193936
17 years, 4 months