[Installation, Configuration & Deployment] - Re: log messages printed twice to the console
by Elhanan
this is the one inf the ear file
| <?xml version='1.0' encoding='ISO-8859-1' ?>
| <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
|
| <log4j:configuration>
|
| <appender name="PMP_FILE" class="org.apache.log4j.RollingFileAppender">
| <errorHandler class="org.apache.log4j.helpers.OnlyOnceErrorHandler"/>
| <param name="File" value="underwrite-log.log"/>
| <!--<param name="Append" value="false"/>-->
| <param name="MaxFileSize" value="5000KB"/>
| <param name="MaxBackupIndex" value="10"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern"
| value="%d{dd MMM yyyy HH:mm:ss,SSS} [%-5p] %c %x - %m%n"/>
| </layout>
| </appender>
|
| <appender name="PERF_FILE" class="org.apache.log4j.RollingFileAppender">
| <param name="File" value="pmp-perf-log.csv"/>
| <param name="MaxFileSize" value="5000KB"/>
| <param name="MaxBackupIndex" value="10"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern"
| value="%d{dd MMM yyyy HH:mm:ss,SSS} [%-5p] %c %x - %m%n"/>
| </layout>
| </appender>
|
| <!--
| <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="DEBUG"/>
|
| <layout class="org.apache.log4j.PatternLayout">
|
| <param name="ConversionPattern" value="%d{ABSOLUTE} %-5p [%c{1}] %m%n"/>
| </layout>
| </appender>
| -->
| <!--appender name="HB8_FILE" class="org.apache.log4j.RollingFileAppender">
| <param name="File" value="hb8-log.log"/>
| <param name="MaxFileSize" value="5000KB"/>
| <param name="MaxBackupIndex" value="10"/>
|
| <layout class="org.apache.log4j.PatternLayout">
| <param name="ConversionPattern"
| value="%d{dd MMM yyyy HH:mm:ss,SSS} [%-5p] %c %x - %m%n"/>
| </layout>
| </appender-->
|
| <!--
| <logger name="org.springframework.transaction" additivity="true">
| <level value="ALL"/>
| <appender-ref ref="PMP_FILE"/>
| <appender-ref ref="CONSOLE"/>
|
| </logger>
| -->
| <!--logger name="org.hibernate">
| <level value="TRACE"/>
| <appender-ref ref="HB8_FILE"/>
| </logger-->
|
| <!--<logger name="com.pnx.pmp.common.log.PerformanceWatch" additivity="false">
| <level value="DEBUG"/>
| <appender-ref ref="PERF_FILE"/>
| </logger>-->
|
| <!--
| <logger name="net.sf.hibernate.SQL">
| <level value="DEBUG"/>
| <appender-ref ref="STDOUT"/>
| </logger>
| -->
|
| <!--
| <logger name="log4j.logger.org.apache">
| <level value="WARN"/>
| <appender-ref ref="STDOUT"/>
| </logger>
|
| <logger name="org.springframework">
| <level value="INFO"/>
| <appender-ref ref="STDOUT"/>
| </logger>
|
| <logger name="net.sf.hibernate">
| <level value="INFO"/>
| <appender-ref ref="STDOUT"/>
| </logger>
|
| <logger name="com.opensymphony.webwork">
| <level value="INFO"/>
| <appender-ref ref="STDOUT"/>
| </logger>
|
| <logger name="org.apache.velocity">
| <level value="INFO"/>
| <appender-ref ref="STDOUT"/>
| </logger>
| -->
|
| <!--
| Leave root definition commented !
| When uncommented it causes problems on JBoss.
| -->
| <!--<root>-->
| <!--<priority value="ERROR"/>-->
| <!--<appender-ref ref="FILE"/>-->
| <!--</root>-->
|
| </log4j:configuration>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251283#4251283
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251283
16 years, 8 months
[JBoss Web Services Users] - regarding message types in bottom-up service generation
by wuyanbo
Hi,
I am learning web service using jboss 5 and jbossws as runtime. I have created a POJO which is quoted below:
| @WebService
| public class HelloWorld {
|
| @WebMethod
| public String sayHello(@WebParam(name="name") String name) {
| return "Hello, " + name;
| }
| }
|
The problem is when i deployed the service into jboss, at runtime, the wsdl file generated contains complex type definitions for the parameter and return value. I expected xsd:string as message type, but it wasn't so. Can anybody be kind to tell me why this happens and how to avoid it? Thanks
Here is the wsdl file generated:
| - <definitions name="HelloWorldService" targetNamespace="http://ws.wuyb.com/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://ws.wuyb.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
| - <types>
| - <xs:schema targetNamespace="http://ws.wuyb.com/" version="1.0" xmlns:tns="http://ws.wuyb.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
| <xs:element name="sayHello" type="tns:sayHello" />
| <xs:element name="sayHelloResponse" type="tns:sayHelloResponse" />
| - <xs:complexType name="sayHello">
| - <xs:sequence>
| <xs:element minOccurs="0" name="name" type="xs:string" />
| </xs:sequence>
| </xs:complexType>
| - <xs:complexType name="sayHelloResponse">
| - <xs:sequence>
| <xs:element minOccurs="0" name="return" type="xs:string" />
| </xs:sequence>
| </xs:complexType>
| </xs:schema>
| </types>
| - <message name="HelloWorld_sayHelloResponse">
| <part element="tns:sayHelloResponse" name="sayHelloResponse" />
| </message>
| - <message name="HelloWorld_sayHello">
| <part element="tns:sayHello" name="sayHello" />
| </message>
| - <portType name="HelloWorld">
| - <operation name="sayHello" parameterOrder="sayHello">
| <input message="tns:HelloWorld_sayHello" />
| <output message="tns:HelloWorld_sayHelloResponse" />
| </operation>
| </portType>
| - <binding name="HelloWorldBinding" type="tns:HelloWorld">
| <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
| - <operation name="sayHello">
| <soap:operation soapAction="" />
| - <input>
| <soap:body use="literal" />
| </input>
| - <output>
| <soap:body use="literal" />
| </output>
| </operation>
| </binding>
| - <service name="HelloWorldService">
| - <port binding="tns:HelloWorldBinding" name="HelloWorldPort">
| <soap:address location="http://127.0.0.1:8080/HelloWorld/HelloWorld" />
| </port>
| </service>
| </definitions>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251282#4251282
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251282
16 years, 8 months
[JBoss AOP Users] - Deploy AOP to jboss 5.1
by kgreenejpmc
Hi,
I am trying to get my aop deployed to jboss 5.1. I have written an annotation, aspect, and jboss-aop.xml. I have verified that the aspect code gets executed when a method is annotated with the JobFlow annotation through eclipse.
However, when deploying the code to jboss, the annotation has no effect.
I did the following to deploy the aop:
1. jar up the annotation and aspect into a jar file and deploy it to farm
2. deploy the jboss-aop.xml and deploy it to farm
3. set enableLoadtimeWeaving in aop.xml to true
4. copied pluggable-instrumentor.jar to the bin directory and modified run.sh to include -javaagent:pluggable-instrumentor.jar
Then I also deployed as a separate jar class that use the annotations. However, the aop is not being applied.
I can run a test outside of jboss that has the annotation and see that the aop is being applied.
Can someone tell me what I am doing wrong?
| Here is the jboss-aop.xml:
|
| <?xml version="1.0" encoding="UTF-8"?>
| <aop xmlns="urn:jboss:aop-beans:1.0">
| <aspect class="com.jpmc.etl.jobflow.aspect.JobFlowAspect" scope="PER_VM"/>
|
| <bind pointcut="execution(* *->@com.jpmc.etl.jobflow.aspect.JobFlow(..))">
| <advice name="executeFlow"
| aspect="com.jpmc.etl.jobflow.aspect.JobFlowAspect"/>
| </bind>
| </aop>
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251271#4251271
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251271
16 years, 8 months