January 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: [JBMESSAGING-1367] Create JCA resource adapter for JBM 2

by jesper.pedersen

This could be done by using the jms.client classes directly and only extending the ones needed for RA specific functionality. Or by implementing the classes in the RA and using the jms.client for a delegate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201089#4201089 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201089

17 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: [JBMESSAGING-1367] Create JCA resource adapter for JBM 2

by jesper.pedersen

Mhmm, since the outbound part of the adaptor needs to expose the JMS 1.1 API it maybe would be better to use the jms.client package for the foundation instead of core.client. E.g. the managed connection factory keeps a JBossConnectionFactory instance. It seems like it would save a lot of duplicated work. What are your thoughts on this ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201068#4201068 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201068

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Revert of r82615 / EJBTHREE-1653

by pferraro

Ah - I finally found the issue... Changes to JBossASKernel in ejb3 as module (r82684) dropped a re-entrancy requirement for EJBContainer.create() - which previous prevented the service mbean from deploying. In r82615, EJBContainer.create() is not re-entrant. The previous version (that utilized a ReentrantReadWriteLock) was at least thread re-entrant. I'll add re-entrancy for create() and destroy() (as it was for start() and stop() are re-entrant already) and get this tested and patched today. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201038#4201038 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201038

17 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBCL-77

by kabir.khan＠jboss.com

Also, I would like to have a fix for http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198457#4198457 https://jira.jboss.org/jira/browse/JBCL-78 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201033#4201033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201033

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: 2 root elements question

by alex.loubyansky＠jboss.com

Here is the issue I am going to work on this week. https://jira.jboss.org/jira/browse/JBXB-169 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201021#4201021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201021

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by alex.loubyansky＠jboss.com

I am going to enhance @JBossXmlNsPrefix. https://jira.jboss.org/jira/browse/JBXB-168 Possibly tomorrow. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201011#4201011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201011

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAX-WS Conformance Requirements

by alessio.soldano＠jboss.com

I agree with your interpretation Darran. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201001#4201001 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201001

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - JAX-WS Conformance Requirements

by darran.lofthouse＠jboss.com

I just quickly wanted to double check the interpretation a conformance requirement from the JAX-WS specification. >From section 4.2.4 of the JAX-WS specification describing exception handling: - anonymous wrote : | Conformance (Exceptions During Handler Processing): Exceptions thrown during handler processing on the client MUST be passed on to the application. If the exception in question is a subclass of WebService-Exception then an implementation MUST rethrow it as-is, without any additional wrapping, otherwise it MUST throw a WebServiceExceptionwhose cause is set to the exception that was thrown during handler processing. | I read this as only being applicable on the client side and not on the server side of the call. However the HandlerChainExecutor is enforcing this on both sides, see the processHandlerFailure method: - http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk/modules/core/sr... The problem is that the WSSecurityDispatcher throws a CommonSOAPFaultException so that a faultCode and faultString can be specified but as this class does not extend WebServiceException the HandlerChainExecutor is replacing the exception so loosing the faultCode and changing the faultString. The HandlerChainExecutor is instantiated from three locations, two for clients and one for server side, my proposal is to pass an additional parameter into the constructor to indicate if this is server side or client side and only enforce the conformance requirement if client side. I have considered other options such as changing class hierarchies for the exceptions but these changes potentially start to leak JAX-WS details into JAX-RPC specific code. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200995#4200995 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200995

17 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-1669 : @Service tutorial on JBoss-5.0 GA

by jaikiran

"jaikiran" wrote : | This fails on AS5 trunk I meant AS5.x branch "jaikiran" wrote : When is the beanContext expected to be created? The @Management is being registered as part of the create() whereas the beanContext is being set (later) as part of start(). What is the right phase to create the beanContext? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200986#4200986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200986

17 years, 2 months

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

I see that on XmlSchema (http://java.sun.com/javaee/5/docs/api/javax/xml/bind/annotation/XmlSchema...) we can customize namespace prefix and namespace URI mapping (Example 2 in the above link) and it seems that should do the job (not 100% sure though) I was wondering if it was possible to do that on JBossXmlSchema annotation but it doesn't seem to work either... How hard would it be to support this ? Also not sure this is related at all but the 'namespace-prefixes' property for the SAXParser (http://www.saxproject.org/apidoc/org/xml/sax/package-summary.html#package...) is not set to true, I wonder if that would be better when set to true ? anonymous wrote : Because they are explicitly bound to javaee ns? Indeed, that forces me to create different set of classes depending of whether or not we are unmarshalling a sip.xml that has namespace defined or not, so I'm kind of duplicating the classes which is a sign of code smell. Also it complicates the code of the deployer because I have to get both metadata and push them into a third set of classes (on which I can do the merge with annotations, jboss-web.xml metadata and web.xml metadata to avoid duplicating the merge operation too) since I cannot know in advance if the sip.xml will have namespace or not... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200939#4200939 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200939

17 years, 2 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 January 2009