February 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: better editor for .xhtml in JBoss IDE - element wrapping

by codelion

These are .xhtml files, and JTidy doesn't show up for them as an option. It does show up as an option for .xml files though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011494#4011494 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011494

19 years, 2 months

1
0
0 / 0

[JBossWS] - Re: JBossWS 1.0.X, JAX-WS compliant JBossWS 2.0 and services

by dwin

hey Andrea you can use the annotation @wsdlLocation to bind your SEI (service end point) to a WSDL. That way the SEI has to confirm to the WSDL. also, you could always do wsgen (WSDL to java) to generate the SEI and the relevant datatypes. To answer your question about moving your JBossWS 1.0.3 to JBossWS 1.2.x and JBossWS 2.x, I would imagine it would be a relatively painless transition. You use your webservice interface (from JAX RPC) as your service interface and tag it with the annotation @Webservice. The JBoss runtime should automatically pick it up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011492#4011492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011492

19 years, 2 months

1
0
0 / 0

[JBossWS] - JBossWS 1.0.X, JAX-WS compliant JBossWS 2.0 and services com

by jova73

Hi, I'm starting in these days to develop new web services for an existing J2EE application and I'm considering using JBoss 4.0.5 and the embedded JBossWS 1.0.3 support. Will my web services be compatible with the new JAX-WS compliant web service stack in JBoss 5?? If now I use JAX-WS RI with JBoss 4, will the migration to JBoss 5 and the JAX-WS compliant JBossWS be easier? Is it possible, in JBossWS 1.0.X and 2.0 (JAX-WS in general), to commit to a WSDL and not to a Java endpoint? That would solve my problem... What do you think? Thanks in advance, Andrea View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011490#4011490 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011490

19 years, 2 months

1
0
0 / 0

[JBossWS] - Error creating SOAPFault message, no NamespaceRegistry

by bcguitar33

Hi there, I'm developing a simple jboss endpoint and I'm having trouble. I've used WStools to generate the necessary files. Things work fine when the user provides the correct input, and things also work fine (the server sends an appropriate fault) when the user sends bad input such as an unsupported function name or the wrong arguments. However, if the user sends a bad SOAP request entirely, such as the tags don't match up, the server generates an error and doesn't send the client anything back at all. I would like this to generate a fault to the client, instead of merely being silent. Does anyone have any idea as to why this may be happening? Here's the jboss stack trace: 13:29:47,229 ERROR [STDERR] [Fatal Error] :4:60: The end-tag for element type "CustomerID" must end with a '>' delimiter. 13:29:47,242 ERROR [SOAPFaultExceptionHelper] SOAP request exception java.io.IOException: org.xml.sax.SAXParseException: The end-tag for element type "CustomerID" must end with a '>' delimiter. at org.jboss.util.xml.DOMUtils.parse(DOMUtils.java:110) at org.jboss.ws.soap.MessageFactoryImpl.createSOAPEnvelope(MessageFactoryImpl.java:238) at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:227) at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:157) at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:215) at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) 13:29:47,323 ERROR [SOAPFaultExceptionHelper] Error creating SOAPFault message org.jboss.ws.WSException: Cannot obtain NamespaceRegistry, because there is no SOAPMessage associated with this context at org.jboss.ws.soap.SOAPMessageContextImpl.getNamespaceRegistry(SOAPMessageContextImpl.java:140) at org.jboss.ws.soap.SOAPMessageContextImpl.getSerializationContext(SOAPMessageContextImpl.java:130) at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.toSOAPMessage(SOAPFaultExceptionHelper.java:223) at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:177) at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:248) at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) 13:29:47,380 ERROR [AbstractServlet] Error processing web service request javax.xml.rpc.JAXRPCException: Cannot create SOAPFault message for: javax.xml.rpc.soap.SOAPFaultException: java.io.IOException: org.xml.sax.SAXParseException: The end-tag for element type "CustomerID" must end with a '>' delimiter. at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:183) at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:248) at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) 13:29:47,388 ERROR [[SVAEndpoint]] Servlet.service() for servlet SVAEndpoint threw exception javax.xml.rpc.JAXRPCException: Cannot create SOAPFault message for: javax.xml.rpc.soap.SOAPFaultException: java.io.IOException: org.xml.sax.SAXParseException: The end-tag for element type "CustomerID" must end with a '>' delimiter. at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:183) at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:248) at org.jboss.ws.server.ServiceEndpointServlet.doPost(ServiceEndpointServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011484#4011484 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011484

19 years, 2 months

1
0
0 / 0

[Installation, Configuration & Deployment] - Re: JBOSS - JDK Compatibility Information

by khaleelmys

Hi, Is anyone know whether Jboss 3.2.3 is supported with JDK 1.5 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011483#4011483 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011483

19 years, 2 months

1
0
0 / 0

[JBoss Seam] - Re: Conversational(initiator=true) when immediate=true

by pdpantages

I am not certain about the behavour. I would expect to have to specify the component.... The API doc says that the usage of initiator with @Conversational is depricated, and to use pages.xml. This is the only reason I started looking at doing it this way. I can stick with the original annotation. I am more interested in a way to get my cancel button to work.... PdP View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011480#4011480 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011480

19 years, 2 months

1
0
0 / 0

[Installation, Configuration & Deployment] - jboss not able to follow soft links

by garyxjones

Sorry if this is a newbie question but I've seen several postings in regards to the allowLinking="true" in the server.xml file, but I'm still not able to get the soft links to work. I'm adding the following line to the /usr/local/jboss/server/default/deploy/jbossweb-tomcat55.sar/server.xml file. (Is this the correct location?) <DefaultContext allowLinking="true" useNaming="true" override="true"/" (This is in the <Host name="localhost" section of server.xml) This is running on a Solaris 5.9 server. Jboss - Version: 4.0.5GA(build: CVSTag=Branch_4_0 date=200610162340) Version Name: Zion Built on: October 16 2006 Apache Tomcat/5.5.20 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011479#4011479 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011479

19 years, 2 months

1
0
0 / 0

[JBossCache] - Calling remveObject on JBossCacheAop causes warn message

by sdhaliwal

We are using JBossCacheAOP and add a instrumented Pojo to the cache using the following statement. | pojoCache.putObject("/sessionCache/xyz1", pojoObject); | Then at a later time this object is removed using the following : | pojoCache.removeObject("/sessionCache/xyz1"); | This code seems to behave correcly as it finds the object. However, we see a waring message in the log that looks like the following : WARN [TreeCache] node /sessionCache/xyz1 not found Just wonderning whether there is a problem with using the API this way or the warning message can be ignored safely. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011478#4011478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011478

19 years, 2 months

1
0
0 / 0

[JBoss Eclipse IDE (users)] - webdoclet classpath issue

by rmerewood

I'm attempting to build an existing project and keep running into this error when running xdoclet: [webdoclet] Make sure the jar file containing the javax.servlet.Servlet class is on the classpath specified in the <taskdef> that defined webdoclet. These classes are needed in order to generate correct output. This looks like it's pretty easy to fix, but I'm completely stumped. I have the J2EE 1.4 Libraries in the build path, which includes servlet-api.jar. I also tried dropping servlet-api.jar in xdoclet's lib directory, but this had no effect. Am I missing something obvious, or is this a symptom of running 3.2.1 with JBossIDE 2.0.0.Beta2 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011477#4011477 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011477

19 years, 2 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: 403 error with custom JAAS login Module.

by wbrown338

Greetings: Updating our login-config.xml with the client login module solved the issue for us. <application-policy name="ebizDomain"> <login-module code="com.gocsc.ebiz.JBossLoginModule" flag="required"> <module-option name="dsJndiName">java:/MSSQLDS</module-option> <module-option name="driverName">net.sourceforge.jtds.jdbc.Driver</module-option> <module-option name="connectionURL">jdbc:jtds:sqlserver://LASALLE/artemis;user=ArtemisProcs;password=*183461*</module-option> <module-option name="keyProc">{call art_prcGetKey()}</module-option> <module-option name="passwordProc">{call art_prcGetPassword(?)}</module-option> <module-option name="rolesProc">{call art_prcGetRoles(?)}</module-option> </login-module>  <login-module code="org.jboss.security.ClientLoginModule" flag="required" /> </application-policy> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011470#4011470 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011470

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-user February 2007