[JBossWS] - Re: wstools and Log4J
by sam.griffith＠jboss.com
Martin,
I'm not sure about the C# calls failure, but as far as the log appender, you can put the following log4j code in a log4j.xml file in your WS build dir so it gets packaged up with your WS when deployed and it'll be used as the appender. You don't have an appender defined for the WSTools so this one will serve as a default. I'll try and look into a more correct way to define the logger for WSTools when it's being invoked but in the mean time this should help get rid of that message.
| <?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
| <log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/" debug="false">
|
| <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
| <errorHandler class="org.jboss.logging.util.OnlyOnceErrorHandler"/>
| <param name="Target" value="System.out"/>
| <param name="Threshold" value="INFO"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <!-- The default pattern: Date Priority [Category] Message\n -->
| <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
| </layout>
| </appender>
|
|
| <root>
| <appender-ref ref="CONSOLE"/>
| </root>
|
|
| </log4j:configuration>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992514#3992514
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992514
19 years, 4 months
[JBossWS] - LinkageError when connecting to webservice
by draken
Hi,
I'm trying to connect (using Apache Cactus ServletTestRunner) to a WS deployed on JBoss4.0.5GA, and I'm getting the following exception:
|
| loader constraints violated when linking org/jboss/util/xml/JBossEntityResolver class
|
| java.lang.LinkageError: loader constraints violated when linking org/jboss/util/xml/JBossEntityResolver class
| at org.jboss.ws.jaxb.SchemaBindingBuilder.buildSchemaBinding(SchemaBindingBuilder.java:90)
| at org.jboss.ws.metadata.ServiceMetaData.getSchemaBinding(ServiceMetaData.java:332)
| at org.jboss.ws.metadata.ServiceMetaData.eagerInitialize(ServiceMetaData.java:400)
| at org.jboss.ws.metadata.UnifiedMetaData.eagerInitialize(UnifiedMetaData.java:147)
| at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:129)
| at org.jboss.ws.deployment.JSR109ClientMetaDataBuilder.buildMetaData(JSR109ClientMetaDataBuilder.java:82)
| at org.jboss.ws.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:96)
| at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
| at org.jboss.ws.jaxrpc.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:128)
| at com.mycompany.MyCactusTest.testFunctionalityAsWebservice(Unknown Source)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at org.apache.cactus.internal.AbstractCactusTestCase.runBareServer(AbstractCactusTestCase.java:153)
| at org.apache.cactus.internal.server.AbstractWebTestCaller.doTest(AbstractWebTestCaller.java:119)
| at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody0(AbstractWebTestController.java:93)
| at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest_aroundBody1$advice(AbstractWebTestController.java:224)
| at org.apache.cactus.internal.server.AbstractWebTestController.handleRequest(AbstractWebTestController.java)
| at org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody2(ServletTestRedirector.java:101)
| at org.apache.cactus.server.ServletTestRedirector.doPost_aroundBody3$advice(ServletTestRedirector.java:224)
| at org.apache.cactus.server.ServletTestRedirector.doPost(ServletTestRedirector.java)
| at org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody0(ServletTestRedirector.java:72)
| at org.apache.cactus.server.ServletTestRedirector.doGet_aroundBody1$advice(ServletTestRedirector.java:224)
| at org.apache.cactus.server.ServletTestRedirector.doGet(ServletTestRedirector.java)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:697)
| 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.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| 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:534)
|
|
The code I'm invoking is:
|
| try {
| URL url = new URL(WSDL_URL);
|
| QName qname = new QName(WS_NAMESPACE, WS_NAME);
|
| ServiceFactory factory = ServiceFactory.newInstance();
| Service service = factory.createService(url, qname);
|
| (....)
| } catch(Exception e) {
| e.printStackTrace();
| }
|
|
Thanks in advance for your help,
Marcin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992465#3992465
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992465
19 years, 4 months
[JBossWS] - wstools and so
by mchamoun
i m having the following error when i try to generate jbossws artifacts
| Running JBossWS wstools for [IPayment]
| directory: C:\DATA\jboss-4.0.5.GA\bin
| command: cmd.exe /C wstools.bat -config C:\DOCUME~1\MIL~1\LOCALS~1\Temp\wstools-config48758.xml -dest C:\workspace1\TESTWS\TESTWS
| ========================================================================="
| .
| WSTools Environment
| .
| JBOSS_HOME: C:\DATA\jboss-4.0.5.GA\bin\\..
| .
| JAVA: C:\Program Files\Java\jdk1.5.0_09\bin\java
| .
| JAVA_OPTS:
| .
| ========================================================================="
| .
| Exception in thread "main" java.lang.NullPointerException
| at java.io.File.<init>(File.java:194)
| at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:282)
| at org.jboss.ws.tools.WSTools.process(WSTools.java:138)
| at org.jboss.ws.tools.WSTools.generate(WSTools.java:120)
| at org.jboss.ws.tools.WSTools.main(WSTools.java:61)
|
and this is my wstools-config.xml
| <?xml version="1.0" encoding="UTF-8" ?>
| - <jbos:configuration xmlns:jbos="http://www.jboss.org/jbossws-tools">
| - <jbos:wsdl-java file="C:\DOCUME~1\MIL~1\LOCALS~1\Temp\tempdir48759.tmp\PaymentWS.wsdl" unwrap="true">
| <jbos:mapping file="jaxrpc-mapping.xml" />
| </jbos:wsdl-java>
| </jbos:configuration>
|
|
can someone please help me resolve this error
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992354#3992354
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992354
19 years, 4 months
[JBossWS] - wstools and Log4J
by martinconnolly
Hi,
I recently switched over from using Axis to wstools for my webservice. A C# client connects to the JBoss WS. The Web Service starts up fine but when I attempt to call any method from the C# GUI I get the following exception:
EJBException in method: public abstract boolean com.systemejb.MyManagementEndPoint.MyMethod(java.lang.String) throws java.rmi.RemoteException, causedBy:
java.lang.reflect.UndeclaredThrowableException
at org.jboss.ejb.plugins.AbstractInstancePool.get(AbstractInstancePool.java:204)
According to the logger this is caused by:
java.lang.StackOverflowError
at org.apache.log4j.CategoryKey.equals(CategoryKey.java:33)
at java.util.Hashtable.get(Hashtable.java:339)
at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:259)
at org.apache.log4j.Hierarchy.getLogger(Hierarchy.java:233)
at org.apache.log4j.LogManager.getLogger(LogManager.java:179)
at org.apache.log4j.Logger.getLogger(Logger.java:94)
When I run wstools in my ant script I also get the following warnings:
wstools:
[wstools] log4j:WARN No appenders could be found for logger (org.jboss.ws.tools.WSTools).
[wstools] log4j:WARN Please initialize the log4j system properly.
I have checked the log4j.xml file and the appenders are enabled. I am unsure whether the issues are related. If anyone could help shed some light on these issues I'd appreciate it.
Thanks
MC
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992306#3992306
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992306
19 years, 4 months
[JBossWS] - Re: Missing Content-Length in response
by heiko.braun＠jboss.com
Here, this is taken from our SOAPMessageImpl.java:
anonymous wrote :
| /*
| * We are lazily encoding our message, which means that currently
| * Content-Length is not being calculated. This should not be a problem
| * because HTTP/1.1 does not require that it be sent (WS Basic Profile 1.1
| * states that implementations SHOULD send HTTP 1.1). If it is determined
| * that it must be sent, this perhaps should be done by the transport
| * layer. However, there could be a space optimization where length is
| * precalulated per attachment, and that calculation would, of course,
| * belong here.
| */
|
|
I don't consider it to be a bug. What issue's do you have with it? What client consumes that service?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992290#3992290
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992290
19 years, 4 months