March 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.

by mageshbk

Delete the "thirdparty" directory and make force.thirdparty.get=true in the ant.properties and rebuild it! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027048#4027048 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027048

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.

by sudarshan_srivathsav

PLZ REPLY ME SOON..ANYONE WHO KNWS IT...IT IS VERY URGENT...:( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027045#4027045 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027045

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Using jbossws/trunk for jboss-5.0, jboss-4.2, jboss-4.0.

by sudarshan_srivathsav

Hi guys... when i try execute the ant file after following all the steps....but when i do a ANT....im getting lot of errors like this , [sudharsans@linux0064 jbossws-samples-1.2.0.GA]$ ant Buildfile: build.xml prepare: [echo] ----------------------------------------------- [echo] jboss.home = /home/sudharsans/jboss-4.0.5.GA [echo] tomcat.home = /usr/java/tomcat [echo] java.home = /apps-es4/vendor/java/jdk1.5.0/jre [echo] endorsed = /home/sudharsans/jboss-4.0.5.GA/lib/endorsed [echo] excludesfile = tests-jboss40-noejb3-excludes.txt [echo] ----------------------------------------------- thirdparty-get: thirdparty-classpath: thirdparty: common-classpath: jboss-classpath: tomcat-classpath: init: wsconsume: compile14: compile15: [javac] Compiling 215 source files to /home/sudharsans/jbossws-samples-1.2.0.GA/output/classes [javac] /home/sudharsans/jbossws-samples-1.2.0.GA/src/main/java/org/jboss/test/ws/JBossWSTest.java:40: package org.jboss.logging does not exist [javac] import org.jboss.logging.Logger; [javac] ^ [javac] /home/sudharsans/jbossws-samples-1.2.0.GA/src/main/java/org/jboss/test/ws/JBossWSTest.java:56: cannot find symbol [javac] symbol : class Logger [javac] location: class org.jboss.test.ws.JBossWSTest [javac] protected Logger log = Logger.getLogger(getClass().getName()); [javac] ^ [javac] /home/sudharsans/jbossws-samples-1.2.0.GA/src/main/java/org/jboss/test/ws/JBossWSTestHelper.java:33: package org.jboss.logging does not exist [javac] import org.jboss.logging.Logger; [javac] ^ [javac] /home/sudharsans/jbossws-samples-1.2.0.GA/src/main/java/org/jboss/test/ws/JBossWSTestHelper.java:45: cannot find symbol [javac] symbol : class Logger [javac] location: class org.jboss.test.ws.JBossWSTestHelper [javac] private static Logger log = Logger.getLogger(JBossWSTestHelper.class); [javac] ^ [javac] /home/sudharsans/jbossws-samples-1.2.0.GA/src/main/java/org/jboss/test/ws/TestDeployerTomcat.java:36: package org.jboss.util does not exist [javac] import org.jboss.util.Base64; There are many such errors....arounf 100 errors. IM a real newbie to it..can u guys pls help me to resolve it or atleast can u guys help me giving a small HELLOWORLD WEBSERVICE example with build file..so that i can get more familiar. It would be so great if u guys could reply as soon as possible ..Since it is very urgent. SUDARSHAN View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4027041#4027041 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4027041

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by heiko.braun＠jboss.com

You may also want to take a look at this one: http://www.innoq.com/resources/ws-standards-poster/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026328#4026328 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026328

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by heiko.braun＠jboss.com

Just to make sure we are on the same page. I am looking at WS-RX: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ws-rx Not to be confused with WS-RM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026326#4026326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026326

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by kukeltje

Reading the specs I tend to agree. They are so limited. No things like: - number of retries - retry interval What other specs are those in? I am starting to hate the ws-hell (no offence to you guys) and long back to the x.400 or the best, ebXML-MS specs... those were 'clean'. If these other parts come in, it becomes a REAL messaging system. JMS implementations lack a lot of functionality to on this part, regarding retries sequences etc... but for the basic ws-rm (rx) it might be sufficient IF all other AS' support the same subset as JBossMQ/Messaging To be continued View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026316#4026316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026316

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by heiko.braun＠jboss.com

IMO JBPM is the wrong approach. Try to keep it simple and external dependencies to a minimum. RM sequence management is really simple and actually only knows a few conditions. RM source and RM destination just figure out the delta and make the source resubmit the missing messages. Looking at the overall picture (like for instance the way a RM destination treats incomplete sequence termination) I agree that it might be regarded as a state machine or could be desinged as such. But IMO this is an implementation detail and JBPM probably adds too much overhead for too little gain. You could probably come up with a simple state machine yourself. Regarding the persistence: I think the only relevant bit to this is the need for a pluggable persistence mechanism. In the beginning some JDBC persistence manager might be sufficient. You may want to take alook at JBossMQ for instance, how they designed it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026236#4026236 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026236

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by kukeltje

I'm studying the specs to, mainly the ws-rm at the moment. At the same time, I'm thinking about ways to implement it, high level that is. Since the sequences etc do need some kind of persistency and there is some kind of flow, I'm thinking of using jBPM (jpdl?) for this. Especially since I will eventually need ebMS 3.0 as well, which uses ws-rm. Any thoughts on this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026215#4026215 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026215

17 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by thomas.diesler＠jboss.com

Ok, please ping me when you're done with studingthe three specs View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4026191#4026191 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4026191

17 years, 2 months

1
0
0 / 0

Re: SAAJ compatibility tests

by Alejandro Guizar

Lance, Allow me to clarify: this is about inconsistent interpretation of SOAP 1.2 requirements in the CTS, not enhancing test coverage. http://jira.jboss.com/jira/browse/JBCTS-553 According to the SOAP 1.2 specification: -Body allows whitespace text only. Text is considered significant -Header allows whitespace text only. Text is NOT considered significant The CTS and the RI interpret SOAP 1.2 requirements inconsistently: -SOAPBody always accepts text, whitespace or otherwise. This is LESS restrictive than SOAP 1.2 -SOAPHeader never accepts text, whitespace or otherwise. This is MORE restrictive than SOAP 1.2 I propose the CTS be made JUST AS restrictive as SOAP 1.2: -SOAPBody accepts whitespace text only. The text is preserved in a javax.xml.soap.Text node. -SOAPHeader accepts whitespace text only. The text is discarded. Regards, Alejandro Lance J. Andersen wrote: > Hi Alejandro, > > Thanks for the note. > > > > Alejandro Guízar wrote: >> Lance, >> >> In the first place, thanks for the time you have spent following up >> this issue. >> >> > What is the specific issue in either of these tests below that are in >> > question (it would help if you could include the code in question in >> > your reply) >> >> CTS validates SOAPHeader more strictly than SOAPBody with no apparent >> reason. >> >> Consider class SOAPElementTestServlet (in >> com.sun.ts.tests.saaj.api.javax_xml_soap.SOAPElement). >> >> The code below adds non-whitespace text to a SOAPBody instance and >> expects the invocation to succeed. addTextNodeTest1 gets called two >> times, one for SOAP 1.1 and one for SOAP 1.2. >> >> void addTextNodeTest1(HttpServletRequest req, HttpServletResponse res) >> { >> ... >> Iterator iStart = body.getChildElements(); >> int countStart = SOAP_Util.getIteratorCount(iStart); >> SOAPElement se = body.addTextNode("<txt>This is text</txt>"); >> if(se == null) { >> pass = false; >> } else if(!body.getValue().equals("<txt>This is text</txt>")) { >> String s = body.getValue(); >> pass = false; >> } >> ... >> } >> >> The code below adds non-whitespace text to a SOAPHeader instance and >> expects the invocation to fail for SOAP 1.2. >> >> void addTextNodeSOAP12Test2(HttpServletRequest req, >> HttpServletResponse res) >> { >> ... >> try { >> Iterator iStart = hdr.getChildElements(); >> int countStart = SOAP_Util.getIteratorCount(iStart); >> SOAPElement se = hdr.addTextNode("<txt>This is text</txt>"); >> >> TestUtil.logErr("Did not throw expected SOAPException"); >> pass = false; >> } catch (SOAPException e) { >> TestUtil.logMsg("Did throw expected SOAPException"); >> } >> ... >> } >> >> Apparently, the intent of addTextNodeSOAP12Test2 is to verify only >> whitespace text can be added to Header elements, as required by SOAP >> 1.2. A similar requirement exists for other SOAP elements, including >> Body. However, addTextNodeTest1 does not verify it. >> >> The CTS should verify this requirement consistently. Either both >> SOAPHeader and SOAPBody validate text addition or none does. > The test above is valid as you point out and yes, the coverage > could/should be expanded going forward. >> >> > WRT, coverage issues, it is possible that not every assertion is >> > tested and i take that is one of the issues that you are referring to >> > below? >> >> If the SAAJ team considers text validation desirable, then the CTS >> should be extended to validate not only Header and Body, but all SOAP >> elements that disallow non-whitespace text content. > As i mentioned in my earlier note, not every assertion is covered and > there is always room for improved coverage as you point out. > > We will look at enhancing coverage going forward for additional SOAP > elements. > > Regards > Lance >> >> Best, >> >> -Alejandro >> >> >> Lance J. Andersen wrote: >>> Alejandro, >>> >>> >>> I need a bit more info here to move forward. >>> >>> - What is the specific issue in either of these tests below that are >>> in question (it would help if you could include the code in question >>> in your reply) >>> - WRT, coverage issues, it is possible that not every assertion is >>> tested and i take that is one of the issues that you are referring to >>> below? >>> Regards >>> Lance >>> >>> Alejandro Guízar wrote: >>>> Lance, >>>> >>>> I am a member of the JBoss Web Services team. The project lead, >>>> Thomas Diesler, indicated you as the person to go to when >>>> questions/issues about the CTS emerge. >>>> >>>> I have one such question with regard to SAAJ tests. I was hoping you >>>> could help me, either directly or by forwarding my question to the >>>> SAAJ team at Sun. >>>> >>>> ----------- >>>> >>>> The test case saaj/api/javax_xml_soap/SOAPElement contains two >>>> tests, addTextNodeTest1 and addTextNodeTest2, that verify the >>>> addition of non-whitespace text to SOAPBody and SOAPHeader under >>>> SOAP 1.1 and SOAP 1.2. Of the four assertions, only adding Text to a >>>> SOAPHeader under SOAP 1.2 is expected to throw an exception. >>>> >>>> No explicit requirement on Text children of Elements appears in the >>>> SOAP 1.1 specification. This is consistent with the CTS assertions: >>>> text nodes are always accepted. >>>> >>>> The table below summarizes explicit requirements on 'character >>>> information item' children of 'element information items' defined by >>>> the SOAP 1.2 specification. >>>> >>>> EII CII content Significant? >>>> --- --- --- >>>> Envelope white space no >>>> Header white space no >>>> HeaderElement any character yes >>>> Body white space yes >>>> BodyElement any character yes >>>> Fault white space no >>>> Detail white space yes >>>> DetailEntry any character yes >>>> >>>> Given the table above, adding non-whitespace text to SOAPHeader or >>>> SOAPBody under SOAP 1.2 is invalid. This applies to SOAPEnvelope, >>>> SOAPFault and Detail as well. The CTS expects SOAPHeader to throw an >>>> exception but not SOAPBody. Other elements are not even tested. >>>> >>>> What is the rationale behind requiring SOAPHeader to throw an >>>> exception, but not other elements? >>>> >>>> ---------- >>>> >>>> Thanks, >>>> >>>> Alejandro Guizar >>>> Senior Software Engineer >>>> JBoss, a division of Red Hat >>>> E: aguizar(a)redhat.com >>>> M: 512-905-0841

17 years, 2 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 March 2007