October 2006 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Why does DOMWriter copy namespaces?

by thomas.diesler＠jboss.com

DOMWriter given any arbitrary DOM element from the the tree should produce valid XML. i.e. it must include the NS declarations from further up if they are not defined on the element that is beeing written out. Previous to the change to DOMWriter, the SOAP content element was beeing assigned invalid XML, which had to be corrected before the fragment was passed to JBossXB. If NS declarations are duplicated on nested elements that would be an error. Correct is, that every XML fragment associated with a SOAPContentElement is valid, which leads to NS declarations on #1 SOAPBodyElement for doc/lit and #2 RPC params for rpc/lit #3 SOAPHeader elements The DOMWriterTestCase should comperensivly test the correct behaviour of the DOMWriter. The XML fragment association may go away in future http://jira.jboss.org/jira/browse/JBWS-1314 when we no longer need to pass XML fragments to JBossXB (i.e can work with DOMSource for example) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979945#3979945 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979945

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Precursor to streaming optimizations, elimination of xml

by thomas.diesler＠jboss.com

http://jira.jboss.org/jira/browse/JBWS-1314 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979943#3979943 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979943

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Why does DOMWriter copy namespaces?

by jason.greene＠jboss.com

Also, why does it add the declarations to every single nested child, and not the just the top level element? -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979935#3979935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979935

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Precurser to streaming optimizations, elimination of xml str

by jason.greene＠jboss.com

At some point, we should remove the xml string fragment processing phase. It's not needed in our long term streaming optimization plan, and it adds unneeded performance overhead in the current design. Instead we could pass the corresponding DOM chunk directly to the marshalling layer. JAXB supports this using InputSource, and it wouldn't be difficult to enhance JBossXB to do the same. This would also be more robust because it would eliminate the xml escape processing that we duplicate from a standard XML parser (see http://jira.jboss.com/jira/browse/JBWS-1240 for an example). -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979932#3979932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979932

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Why does DOMWriter copying namespaces?

by jason.greene＠jboss.com

Why did we add the logic to copy root namespaces to a generic DOM output class? Looking at the other changes in it seems like now other areas of the stack have to do all of this work to remove namespaces. If the namespace copying is only needed on the top level element that is passed into JBossXB/JAXB, then doesn't this belong in SOAPContentElement?, or some other kind of SOAPContentElement specific class. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979931#3979931 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979931

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBAS-3766, port the webservice deployer

by jason.greene＠jboss.com

On this topic, I have created an issue for XML overrides that will need to pull from the new metadata model http://jira.jboss.com/jira/browse/JBWS-1309 -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979164#3979164 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979164

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by maeste

Thanks thomas. We are working also on another problem we are experiencing on a jboss cluster with a jbossws eventing deployed on it. The cluster is viewed (of course) as a single machine by the client, subscribing and getting events to our service. As you can figure out the problem is more than one: 1. The load balancer send subscriptions to only one server, but the subscriptions have to be registered by all servers in the farm (or better in only one place for all cluster's machines IMHO) 2. The notification have to be coordinated. 3. Events like "machine going down" have to be generated according to cluster status, not single machine status. 4. Something else we are thinking about.....:) We (me ad Alessio alias "palin" on these forums) will have fun coding on these issues, but we need some informations about jbossws' core design: a. The easiest way to implement this stuffs is to use clustered ejbs as notification proxy, but we think you don't like any solution using ejb. Isn't it? b. We are thinking to use hajndi to register subsriptions. What do you think about? c. We think the only part of jbossws needing a cluster solution is ws-eventing because it is the only part in which jbossws acts as client (meaning a source of soap message). Isn't it? Are you thinking about a more general clustering enhacement? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979017#3979017 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979017

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by thomas.diesler＠jboss.com

Stefano, Heiko is mostly offline this week. He'll be back next week when you will get qualified feedback on this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979010#3979010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979010

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing: event notification failure

by maeste

ASFAIK the jira issue about this post doesn't exist (yet). I'm asking if my proposed solution seems in the right direction. If you think so, I'll start to work on the code and I'll create the patch on jira. Are there something incorrect in my steps? Do I have to create the jira issue before asking opinions here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979008#3979008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3979008

17 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1133 - Exploded JSR-181 POJO Deployment Fails Redep

by thomas.diesler＠jboss.com

I think we can safely postpone this issue until the complete set of metadata is available in WebMetaData. A possible workaround is not to use exploded wars with jsr181 endpoints. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978780#3978780 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978780

17 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev October 2006