May 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by thomas.diesler＠jboss.com

Do you see the issue when you run the test? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154194#4154194 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154194

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by alex.loubyansky＠jboss.com

Unfortunately I don't know how the issue can be fixed w/o doing that "complication" work. This is essential to work it out. This happens during marshalling, so I need - the XSD against which the object is marshalled; - the classes and initialization part of the object being marshalled. The hint to narrow it down is "Missing value for the required attribute strAttr of element {http://org.jboss.test.ws/jbws720/types}getProperty" View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154171#4154171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154171

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2187] javax.xml.ws.Service handlers and thread saf

by alessio.soldano＠jboss.com

"thomas.diesler(a)jboss.com" wrote : How about making a copy of the handler chain on port creation and scope that copy on the port? Do you mean making a copy of the handler chain or of the handler chain metadata? Well, the port actually already has its own handler chain which is stored in its binding. If the handler chain copy is meant to prevent a port from having its own handlers changed by somebody else, we could also think about not registering the client for notifications when the metadata changes (cfr the observer/observable in place there) and manually ask for binding handler chain rebuild when the config-name/file is set through a given port. Could this be reasonable (I'm not completely aware of the reason that led to the observer/observable pattern being used)? The service will still be touched by an action on the port, anyway (IOW this does not solve the problem completely). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154163#4154163 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154163

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2174] Cannot Obtain Destination for Request

by thomas.diesler＠jboss.com

It is not so much about "like" and "don't like". You change results in a stack specific deployment aspect that is not usable in any but one specific container. Do you understand the fundamentals behind SPI, container/stack integration. The build should enforce these principals to prevent these types of mistakes. If it does not, it is actually my mistake. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154162#4154162 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154162

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2174] Cannot Obtain Destination for Request

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : You fix is fundamentally wrong, because it creates a dependency on the container. How to do it right? Give me an idea and I'll do it. As I said before I don't like my current fix. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154153#4154153 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154153

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2174] Cannot Obtain Destination for Request

by thomas.diesler＠jboss.com

You fix is fundamentally wrong, because it creates a dependency on the container. WS stack integration must stay clear of container details. Container integration must stay clear of stack details. If the problem only pertains to AS50Beta4, we can resolve it as "Won't fix" With the old build system your fix should not even have compiled. I'm looking into how this can be enforced in maven. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154151#4154151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154151

16 years, 7 months

1
0
0 / 0

RE: FW: [JBoss JIRA] Work started: (JBWS-925) Add support for FastInfoset

by Alexander Philippou

Hi Thomas, Did you find any time to test interop using the service we raised? Best, Alexander > -----Original Message----- > From: Alexander Philippou [mailto:alex@noemax.com] > Sent: Friday 28 March 2008 15:54 > To: 'jbossws-dev' > Subject: RE: FW: [JBoss JIRA] Work started: (JBWS-925) Add > support for FastInfoset > > > Hi Thomas, > > MSFT doesn't offer a Fast Infoset implementation. For WCF, > Fast Infoset is provided by Noemax's WCF-Xtensions. > > I assume that general JBossWS<->WCF interop is given so we > just need to focus on trying Fast Infoset as message > encoding. This will also test content negotiation, which > again is provided only by WCF-Xtensions. > > We have raised a test service, its wsdl is at > http://www.noemax.com:8080/BenchmarkService?wsdl. It will be > great if you can run a client to test it. > > Best, > Alexander > > > -----Original Message----- > > From: Thomas Diesler [mailto:thomas.diesler@jboss.com] > > Sent: Friday 28 March 2008 12:02 > > To: Alexander Philippou > > Cc: jbossws-dev > > Subject: Re: FW: [JBoss JIRA] Work started: (JBWS-925) Add > > support for FastInfoset > > > > > > Hi Alexander, > > > > we are already regularly taking part on the MSFT interop > > events. For us, > > this would be the preferred stop to test FastInfoset > interoperability. > > > > However, if you have public interop endpoints available, I'd > > be happy to > > create test clients for them on our side. > > > > cheers > > -thomas > > > > Alexander Philippou wrote: > > > Hi Thomas, > > > > > > Great that you are adding Fast Infoset support to JBoss! > > > > > > My company offers the leading Fast Infoset implementation > for .NET. > > > Would you be interested in performing some JBoss<->WCF > interop once > > > you are ready? > > > > > > Best, > > > Alexander > > > > > >> -----Original Message----- > > >> From: Thomas Diesler (JIRA) [mailto:jira-events@lists.jboss.org] > > >> Sent: Wednesday 12 March 2008 16:05 > > >> To: alex(a)noemax.com > > >> Subject: [JBoss JIRA] Work started: (JBWS-925) Add support > > >> for FastInfoset > > >> > > >> > > >> [ http://jira.jboss.com/jira/browse/JBWS-925?page=all ] > > >> > > >> Work on JBWS-925 started by Thomas Diesler. > > >> > > >>> Add support for FastInfoset > > >>> --------------------------- > > >>> > > >>> Key: JBWS-925 > > >>> URL: http://jira.jboss.com/jira/browse/JBWS-925 > > >>> Project: JBoss Web Services > > >>> Issue Type: Feature Request > > >>> Security Level: Public(Everyone can see) > > >>> Components: jbossws-native > > >>> Reporter: Thomas Diesler > > >>> Assigned To: Thomas Diesler > > >>> Fix For: jbossws-native-2.0.4 > > >>> > > >>> > > >>> A standard way of doing binary WS is FastInfoset > > >>> http://java.sun.com/developer/technicalArticles/xml/fastinfoset/ > > >>> The Fast Infoset standard draft (currently being > > developed as joint > > >>> work by ISO/IEC JTC 1 and ITU-T) specifies a binary > > format for XML > > >>> infosets that is an efficient alternative to XML. An > > >> instance of this > > >>> binary format is called a fast infoset document. Fast infoset > > >>> documents are analogous to XML documents. Each has a > > >> physical form and > > >>> an XML infoset. Fast infoset documents are, given the results > > >>> presented, faster to serialize and parse, and smaller in > > size, than > > >>> the equivalent XML documents. Thus, fast infoset documents > > >> may be used > > >>> whenever the size and processing time of XML documents is > > an issue. > > >> -- > > >> This message is automatically generated by JIRA. > > >> - > > >> If you think it was sent incorrectly contact one of the > > >> administrators: > > http://jira.jboss.com/jira/secure/Administrators.jspa > > >> - > > >> For more information on JIRA, see: > > >> http://www.atlassian.com/software/jira > > >> > > >> > > >> > > > > > > > -- > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > Thomas Diesler > > Web Service Lead > > JBoss, a division of Red Hat > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > >

16 years, 7 months

2
2
0 / 0

[Design of JBoss Web Services] - Re: sub-tasks of JBAS-5384

by thomas.diesler＠jboss.com

build,deploy,test is only a two step process http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Source#Che... Reproduction of this issue would probably only add complication. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154149#4154149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154149

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: [JBWS-2187] javax.xml.ws.Service handlers and thread saf

by thomas.diesler＠jboss.com

How about making a copy of the handler chain on port creation and scope that copy on the port? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154145#4154145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154145

16 years, 7 months

1
0
0 / 0

[Design of JBoss Web Services] - [JBWS-2174] Cannot Obtain Destination for Request

by richard.opalka＠jboss.com

Hi Folks, I'd like to brainstorm with you on http://jira.jboss.org/jira/browse/JBWS-2174. First of all I'll describe the problem. We're using web context parameter to specify the CXF specific deployment descriptor extension location. However I discovered this parameter isn't propagated for EJB3 endpoints, because for those endpoint we're generating the web.xml (AS 5 Beta 4) or we're generating JBossWebMetaData in memory (for AS 5 trunk). I was able to fix this issue for AS 5 trunk, see: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossws/stack/cxf/trunk/module.... I don't like this fix very much. So my first question is, do you have some ideas how to do it better? The second problem I have is described in JBWS-2174 comments. I'm not able to think out the solution for AS 5 Beta 4 for generated web.xml. So the second question I'm asking do you have an idea or trick how to achieve that? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153853#4153853 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4153853

16 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev May 2008