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

[Design of JBoss Web Services] - JBWS-1464 - Adding MTOM support to WSDL To Java - Design

by darran.lofthouse＠jboss.com

This thread is to discuss the options for adding MTOM support to WSDL To Java. There are a number of options for how this can be implemented and a number of obstacles to overcome for the more advanced implementations. The main obstacle is that it is not possible to get access to the expectedContentTypes attribute using the xerces schema API. On the plus side there currently does not apear to be any work required on generating the JAX RPC mapping file, this just requires a variable mapping (which does not contain type information) in the corresponding java-xml-type-mapping. This mapping is already correctly generation. At the moment I see the following options for how this could be implemented: - 1 - Map all binary types to javax.activation.DataHandler A global configuration option can be set to switch on MTOM mapping and all types that are based on xs:base64Binary or xs:hexBinary can be mapped to javax.activation.DataHandler. 2 - Global configuration to specify what binary types should be mapped to. A global configuration option can be added to specify what the binary types should be mapped to. This would assume all binary types can be mapped to the same type. 3 - Allow configuration to map XML types to specific Java types. This would mean if the schema contains different types based off the binary types then it will be possible for each to be mapped to a different Java type. This would however not work when the binary types are mapped as follows as it will not be possible to differentiate between them: - <element name="legacyData" | xmime:expectedContentTypes="text/xml" | type="xmime:base64Binary"/> | 4 - A more advanced configuration to allow the specific elements to be identified. | <complexType name='Employee'> | <sequence> | <element name="firstname" type="xsd:string"/> | <element name="lastname" type="xsd:string"/> | <element name="legacyData" xmime:expectedContentTypes="text/xml" | type="xmime:base64Binary"/> | </sequence> | </complexType> | So for this example the configuration would allow the user to specify that the element legacyData of the type Employee should be mapped to a specific Java type. 5 - Switch on generation of synthetic annotations. The xerces implementation has a feature that can be enabled to generate a synthetic annotation when a schema component has non-schema attributes. This annotation could then be parsed to extract the expectedContentTypes. This of course would be xerces implementation specific. An appropriate Java type can then be selected based on the list of content types. 6 - Add a pre-generation step to read mime information from the WSDL Add a step before generation to read all expectedContentTypes from the schema (Possibly using the synthetic annotations approach), this will store the data in a model - as part of the main generation step this model can be read if a binary type is found to check if mime types have been specified. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004323#4004323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004323

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LayouStrategy and StrategyResponse API

by julien＠jboss.com

If think that using JBoss Portal internals would be a better thing as it is going to remain the same for the 2.x branch. We are not saying there should not be entry points for such customizations by removing them. We wanted to remove something that is flawed by design rather than providing something that half works. You should describe your use case and we can work together to make it work. The rendering process can still be improved to fit your use case and I would be glad to help you there. "radzish" wrote : In what way? ;) | | Should I describe my goal/task? | | Or you probably preparing another way to provide "pluggable API that allows the layout developer to influence the content of the page that is | about to be rendered" (it is from JBossReferenceGuide).? | | You know, it is probably the most important phrase from guide that had a great impact on my decision to use JBoss Portal and not some other Portal Framework. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004322#4004322 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004322

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LayouStrategy and StrategyResponse API

by radzish

In what way? ;) Should I describe my goal/task? Or you probably preparing another way to provide "pluggable API that allows the layout developer to influence the content of the page that is about to be rendered" (it is from JBossReferenceGuide).? You know, it is probably the most important phrase from guide that had a great impact on my decision to use JBoss Portal and not some other Portal Framework. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004289#4004289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004289

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LayouStrategy and StrategyResponse API

by julien＠jboss.com

it is true. We can certainly help you to achieve the customization you are wanting to do in another manner. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004280#4004280 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004280

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: LayouStrategy and StrategyResponse API

by radzish

I installed JBoss Alpha1 and it seems like layout strateries are not invoked at all any more. Is that true? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004273#4004273 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004273

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-674 - Propagating changes on ClusteredConnec

by timfox

I've finally managed to look at the new code. A few questions: 1. The update information is sent from server to client in a ConnectionFactoryUpdateMessage instance. This needs to be wrapped in a MessagingMarshallable, otherwise we can't version it. 2. ServerConnectionFactoryEndpoint::updateclusteredClients() is currently only called when a connection factory is deployed / undeployed. It is not called when a node joins or leaves the cluster. It needs to be called in this case too. Also you need to add tests to check that the update occurs in this situation. 3. Why have you made MessageCallbackHandler and ConnetionFactoryCallbackHandler implement the same (new) interface (CallbackHandler) ? This seems redundant since they are never called polymorphically anyway. 4. I was unsure why init() was being called on the ClientClusteredConnectionFactoryDelegate every time a failover view change occurred... Cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004237#4004237 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004237

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: URLSelectorStrategy

by weston.price＠jboss.com

Hey genman, What are your plans for this? Do you still want to handle this? If so, where are you on it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004236#4004236 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004236

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Problems JCA JMS inflow issue and tx NotSupported

by weston.price＠jboss.com

CRAP...now I remember the issue. The problem you were seeing was that in the old code (now 4.0.5) support for handling a RuntimeException in an non specified transaction context had to be done via a SystemProperty. Being that you had not set this, it didn't work. However, I was never happy about having to set something like that to get that behavior. This requirement is removed in the latest code so it's best to go with that anyway. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004233#4004233 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004233

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Problems JCA JMS inflow issue and tx NotSupported

by weston.price＠jboss.com

Not a problem. Again, it is already backported to 4.2. 4.0.5 is next, however, I am not sure if I have to do anything special for the new cummulative patch cycle stuff. The changes to the adapter need to go in regardless of JBM, they offer improvements all around. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004229#4004229 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004229

19 years, 2 months

1
0
0 / 0

[Design of JCA on JBoss] - Re: Problems JCA JMS inflow issue and tx NotSupported

by timfox

"weston.price(a)jboss.com" wrote : Can you confirm your simple JBM/jPBM test works with the adapter in HEAD? It should be a simple drop in replacement. Certainly. I am a bit rushed right now, but will get around to this sometime early next week. http://jira.jboss.com/jira/browse/JBMESSAGING-763 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004228#4004228 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004228

19 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 2007