April 2008 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: Hudson file permissions

by richard.opalka＠jboss.com

I was thinking about all those qa things some days ago Thomas. Here is my idea, how it could work: * there will be a new user, let's call him builder for illustration * each team member log in to jbws.dyndns.org * then he switch to builder user * do the QA staff, such as new environment setup, update of existing one What do you think about this idea? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141984#4141984 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141984

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: Hudson file permissions

by thomas.diesler＠jboss.com

I need to recreate the hudson env to verify what I claim above View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141983#4141983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141983

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Hudson file permissions

by thomas.diesler＠jboss.com

Over the last couple of days we did not have any hudson runs because most files belong to ropalka.jbossws and do not have group write permissions. Hudson silently aborts a job if it cannot write the 'nextBuildNumber' It is therefore important that you run | > umask 2 | > hudson-setup | > hudson-start | That should cause all newly created files to have group write access. umask is a build-in shell command that cannot be run from within ant AFAIK. Instead of recreating the hudson environment, I try to fix the file permissions. That may take a while View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141978#4141978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141978

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS 3.0.1 Release Issues

by richard.opalka＠jboss.com

"yhrn" wrote : Hi, | I was told to re-open JBWS-1714 but I can't. I have posted a comment and attached an example though. | | Cheers, | Mattias I reopened it ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141672#4141672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141672

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS 3.0.1 Release Issues

by yhrn

Hi, I was told to re-open JBWS-1714 but I can't. I have posted a comment and attached an example though. Cheers, Mattias View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141662#4141662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141662

18 years

1
0
0 / 0

Re: [Fwd: @SchemaValidation case]

by Thomas Diesler

Hi David, what is your specific question? If the documentation is not clear, you can easily improve it based on your understanding - I of course can help you to improve your understanding. cheers -thomas Heiko Braun wrote: > Do you want to take a look at this? > > > > > ------------------------------------------------------------------------ > > Subject: > @SchemaValidation case > From: > David Boeren <dboeren(a)redhat.com> > Date: > Thu, 03 Apr 2008 08:26:55 -0500 > To: > Heiko Braun <hbraun(a)redhat.com> > > To: > Heiko Braun <hbraun(a)redhat.com> > > > I've got a case where the customer is wanting to use @SchemaValidation > to validate their webservice calls, but is getting errors. > > https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&ti... > > > Note: You will have to select "All Events" to see the relevant information. > > When they set @SchemaValidation(enabled=true) they get this error: > > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler > executor: [] > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS] > callRequestHandlerChain: PRE > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: > [type=PRE,info=[service={http://api.prepaid.tsys.com/system/wsdl}system,po... > <http://api.prepaid.tsys.com/system/wsdl%7Dsystem,port=%7Bhttp://api.prepa...>]] > > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler > executor: > [org.jboss.wsf.framework.invocation.RecordingServerHandler@6421c8] > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Enter: handleIn > BoundMessage > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Exit: handleIn > BoundMessage with status: true > 2008-04-02 10:46:36,806 DEBUG [org.jboss.ws.core.EndpointInvocation] > getRequestPayload > 2008-04-02 10:46:36,806 DEBUG [org.jboss.ws.core.EndpointInvocation] > getRequestParamValue: {http://api.prepaid.tsys.com/system/type}ping > <http://api.prepaid.tsys.com/system/type%7Dping> > 2008-04-02 10:46:36,806 INFO [org.jboss.ws.core.soap.SOAPBodyElementDoc] > Validating: XML_VALID > 2008-04-02 10:46:36,806 WARN > [org.jboss.ws.extensions.validation.SchemaExtractor] Multiple schema > elements not supported. > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class > org.jboss.wsf.spi.management.ServerConfigFactory' > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.wsf.framework.DefaultSPIProvider] class > org.jboss.wsf.spi.management.ServerConfigFactory Implementation: > org.jboss.wsf.framework.management.ServerConfigFactoryImpl@17b9a1a > 2008-04-02 10:46:36,806 ERROR [or2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl] getHandlerChain: > [type=ENDPOINT,info=[service={http://api.prepaid.tsys.com/system/wsdl}syst... > <http://api.prepaid.tsys.com/system/wsdl%7Dsystem,port=%7Bhttp://api.prepa...>]] > > g.jboss.ws.extensions.validation.StrictlyValidErrorHandler] > org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of > element 'm:ping'. > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response > processing > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: > org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@538db1 (Thread > http-127.0.0.1-8080-2) > 2008-04-02 10:46:36,806 DEBUG > [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: > org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS@ee1c42 (Thread > http-127.0.0.1-8080-2) > 2008-04-02 10:46:36,806 ERROR > [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception > org.jboss.ws.WSException: org.xml.sax.SAXException: cvc-elt.1: Cannot > find the declaration of element 'm:ping'. > > > When they add a schemaLocation like this: > @SchemaValidation(schemaLocation="xsd/sample.xsd"), the service fails to > deploy. > > The documentation on our wiki about @SchemaValidation is nearly > non-existant so I'm assuming that I'm probably not telling him the right > way to use this annotation. Can you take a quick look and let me know > what the proper annotation should be? Or, if his error indicates a > different problem source, what should we be looking at? > > Thanks! -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

18 years

2
2
0 / 0

[Design of JBoss Web Services] - Re: A stack MUST NOT have a compile time dependency on jboss

by heiko.braun＠jboss.com

anonymous wrote : I am trying to find a good location for our generic handler base classes Why not put them in common? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141594#4141594 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141594

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: A stack MUST NOT have a compile time dependency on jboss

by heiko.braun＠jboss.com

Stack, as well as container may only have a dependency on the interfaces (SPI) not the implementation (framework). The framework code is an implementation detail that may not be available in all target containers. I know this sounds academic, and probably is not true at the moment, but proper decoupling requires this IMO. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141593#4141593 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141593

18 years

1
0
0 / 0

[Design of JBoss Web Services] - A stack MUST NOT have a compile time dependency on jbossws-f

by thomas.diesler＠jboss.com

Heiko, could you please remind me why this is. |  | <pathelement location="${thirdparty.dir}/jbossws-common.jar"/> | <pathelement location="${thirdparty.dir}/jbossws-spi.jar"/> | I am trying to find a good location for our generic handler base classes View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141592#4141592 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4141592

18 years

1
0
0 / 0

Public Announcement

by Richard Opalka

http://www.theserverside.com/ Richard -- B.Sc. Richard Opalka Senior Software Engineer JBoss, a division of Red Hat Mobile: +420 731 186 942 Mail: ropalka(a)redhat.com

18 years

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev April 2008