August 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBossCache] - Re: Common marshalling infrastructure

by trustin

All sounds good to me, too. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169165#4169165 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169165

17 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: Common marshalling infrastructure

by david.lloyd＠jboss.com

I've been thinking about that - I think it is up to the user to handle detection (through an additional header, or some other mechanism, like the negotiation phase that Remoting 3 uses). The header written by the marshaller should be used to verify the stream's integrity and possibly select a version if the marshaller has multiple supported wire protocol versions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169162#4169162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169162

17 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: Common marshalling infrastructure

by trustin

Would we need to read objects from a stream which contains objects serialized with different marshallers? (Read: Do we need unmarshaller auto-detection?) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169161#4169161 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169161

17 years, 8 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: messagingType optional issue

by scott.stark＠jboss.org

It will be handled in the mdb container as discussed here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169157 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169158#4169158 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169158

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: MDB.getActivationConfigProperties handling of no destina

by scott.stark＠jboss.org

I created https://jira.jboss.org/jira/browse/EJBTHREE-1451 as with the patch applied I have the associated tck test passing. We need a similar mdb test in the ejb3 testsuite. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169157#4169157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169157

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: portal clustering problem when using optimistic locking

by prabhat.jha＠jboss.com

Brian: That's what I thought too. Galder: I will try to get thread dumps. There is a minor complication that AS instances are spawned and managed by Smartfrog which itself is a java process. I need to see how I can capture it to a file. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169153#4169153 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169153

17 years, 8 months

1
0
0 / 0

[Design of JBoss Portal] - Re: portal clustering problem when using optimistic locking

by bstansberry＠jboss.com

"prabhat.jha(a)jboss.com" wrote : What I would like to mention though that the cluster name, mcast_addr, port parameters are different in jboss-service.xml in web-cluster.sar and portal.sar. Do they need to use same cluster config? No, they have to be diffferent. The different caches use different JGroups channels and those settings keep those channels' traffic separate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169151#4169151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169151

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - MDB.getActivationConfigProperties handling of no destination

by scott.stark＠jboss.org

For the JBCTS-604 issue, the mdb container needs to be defaulting the destination type. I have fixed the deployment error using this change to the MDB.getActivationConfigProperties: | // We need a destiation-type | ActivationConfigPropertyMetaData destTypeMD = result.get(DESTINATION_TYPE); | if (destTypeMD == null) | { | JBossMessageDrivenBeanMetaData md = (JBossMessageDrivenBeanMetaData) getMetaData(); | String destinationJNDI = md.getDestinationJndiName(); | try | { | InitialContext ctx = new InitialContext(); | String destType = super.getDestinationType(ctx, destinationJNDI); | ActivationConfigPropertyMetaData metaData = new ActivationConfigPropertyMetaData(); | metaData.setName(DESTINATION_TYPE); | metaData.setValue(destType); | result.put(metaData.getName(), metaData); | } | catch(Exception e) | { | log.warn("Failed to determine destination type", e); | } | } | Should I create an ejb3 issue or is there a better way to default this? It would seem the container has the most information on the destination endpoint. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169150#4169150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169150

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: eclipse build problems

by scott.stark＠jboss.org

Running eclipse:m2eclipse before importing is what was needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169141#4169141 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169141

17 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: eclipse build problems

by ALRubinger

I'm not having these problems, either with mvn eclipse:eclipse or the m2eclipse plugin... Maybe manually remove .classpath locally and import fresh? This gets back to lots of debate about what form the Eclipse project files should take. Carlo's been committing plugin-specific stuff, though I wouldn't be surprised if they've fallen out of sync. My opinion is that all IDE-specific stuff is out of scope for version control due to these types of problems. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169138#4169138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169138

17 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums August 2008