June 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - Re: Setting the properties on the JAXBContext

by thomas.diesler＠jboss.com

I externalized construction of the JAXBContext in a JAXBHandler which is a property on the Endpoint. | public interface JAXBHandler | { | /** Get a JAXBContext instance. | */ | JAXBContext getJAXBContext(Class[] javaTypes) throws JAXBException; | } | | public interface Endpoint | { | ... | | /** Get the JAXBHandler for this endpoint */ | JAXBHandler getJAXBHandler(); | | /** Set the JAXBHandler for this endpoint */ | void setJAXBHandler(JAXBHandler handler); | | ... | } | The JAXBHandler is injected like any other handler | <bean name="WSEndpointHandlerDeployer" class="org.jboss.wsf.spi.deployment.EndpointHandlerDeployer"> | <property name="requestHandler">org.jboss.wsf.stack.jbws.RequestHandlerImpl</property> | <property name="lifecycleHandler">org.jboss.wsf.stack.jbws.LifecycleHandlerImpl</property> | <property name="jaxbHandler">org.jboss.wsf.spi.binding.jaxb.JAXBContextCache</property> | <property name="invocationHandler"> | <map keyClass="java.lang.String" valueClass="java.lang.String"> | <entry><key>JAXRPC_JSE</key><value>org.jboss.wsf.stack.jbws.ServiceLifecycleInvocationHandler</value></entry> | <entry><key>JAXRPC_EJB21</key><value>org.jboss.wsf.container.jboss42.InvocationHandlerEJB21</value></entry> | <entry><key>JAXRPC_MDB21</key><value>org.jboss.wsf.container.jboss42.InvocationHandlerMDB21</value></entry> | <entry><key>JAXWS_JSE</key><value>org.jboss.wsf.stack.jbws.ServiceLifecycleInvocationHandler</value></entry> | <entry><key>JAXWS_EJB3</key><value>org.jboss.wsf.container.jboss42.InvocationHandlerEJB3</value></entry> | </map> | </property> | </bean> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057999#4057999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057999

18 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failover on Shutdown

by timfox

For now we just need to add the flag as specified in the JIRA task. If true then it shuts down without failing over View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057916#4057916 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057916

18 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failover on Shutdown

by clebert.suconic＠jboss.com

Can't we create a shutdown method where the sysadmin would be able to give an option for the shutdown type he wants to perform? Say.. if the sysadmin decides to take the system down when the load is low.. he could decide to merge queues as he is planning the system out for a long period. The sysadmin already has that option anyway... he would just have to kill the server.. this would be just a cleaner way to do it. I thought about these options on Shutdown (Consider these options as a brain storm for now): I - Keep Trying: (Tell clients to keep trying reconnect until the server is back.. .the user could take that decision for quick restarts). We would need to send a message to every active connection before doing this, closing the valve on clients... and keep trying to connect until the server is back. II - Shutdown as failover (Merge queues as it would happen on a regular crash) III - Just Shutdown (And throw exceptions to clients.. so client would have to catch exception and retry "a la MQ") View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057910#4057910 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057910

18 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Setting the properties on the JAXBContext

by heiko.braun＠jboss.com

I did already break up the JAXBContextCache and the JAXBContextFactory. Regardless on how we proceed, this was a good idea anyway. If Thomas suggestion is correct, which means the customizations are only required for JAX-WS endpoints then we might actually go with a solutions that attaches to the InvocationContext. I.e. a Map like Interface | InvocationContext.addAttachment(JAXBContexCustomisation.class, <Instance>); | that can carry JAXBRI default properties. See http://jsourcery.com/api/java.net/jaxb/2.1.2/com/sun/xml/bind/api/JAXBRIC... for a complete list. This way at least the JBossWS RequestHandlerImpl is open to any JAXB customisation. Other RequestHandler would then just disregard these attachments. Tom, would this be sufficient? Can you supply this information on a per-invocation base? Or might this better be attached to the Endpoint - on a per-deployment base? I don't really grasp the use cases yet. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057907#4057907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057907

18 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Setting the properties on the JAXBContext

by thomas.diesler＠jboss.com

Tom, I assume this only applies to JAXWS endpoints. The JAXWS client API is not affected. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057892#4057892 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057892

18 years, 9 months

1
0
0 / 0

[Design of EJB 3.0] - Re: JBossEjbParsingDeployer can't handle EJB3 jboss.xml

by bill.burke＠jboss.com

I like the idea of having multiple component deployers like CMP/BMP. I want to be able to remove this code for tighter "lighter" distributions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057876#4057876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057876

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Re: JBoss portal and CAS (Central Authentication Service)

by sohil.shah＠jboss.com

The CAS branch is a fully functional/tested integration with Portal 2.6. If you are having issues with the integration, please let us know and we can fix any bugs before merging the branch. The merge is planned for the Portal 2.6.1 release for now. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057861#4057861 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057861

18 years, 9 months

1
0
0 / 0

[Design of JBoss Portal] - Re: JBoss portal and CAS (Central Authentication Service)

by lucboudreau

I'd like to know : - Has anyone been able to use CAS authentication with JBoss Portal ? - When is the merge between the CAS branch and the 2.6 trunk planned ?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057858#4057858 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057858

18 years, 9 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Setting the properties on the JAXBContext

by mark.little＠jboss.com

"tfennelly" wrote : +1 | | We need something agreed for 2.0.0 and I'd guess it's too late for a neutral SPI based solution at this stage, yes/no? | >From a purely ESB perspective, WS neutrality is not important in 4.2. JBossWS is all we'll be supporting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057844#4057844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057844

18 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Message order receipt assumptions

by bela＠jboss.com

Yes, total order is an overkill in this siutuation. What I suggest is to use virtual synchrony, which you can do by adding the FLUSH protocol to your stack. An example of this is JGroups/conf/flush-udp.xml (in 2.5) or JGroups/conf/stacks.xml (the "udp" config in 2.5 as well). I don't read this forum, so ping me when you need me to reply to your reply... Bela View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4057786#4057786 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4057786

18 years, 9 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 June 2007