September 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3586) Message log browser functionality

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3586?page=com.atlassian.jira.plugin.... ] Jim Ma commented on JBWS-3586: ------------------------------ There is already view log button to monitor the log file content under ${jboss.server.log.dir} in wildfly and EAP6. We can simply leveraget this funcionality to browser SOAP message instead of integrate CXF's logbrowser gui with wildfly/EAP6 console. All soap message log can be handled in seperate logger categories and write into another log file instead of server.log. This is the simple step to configure the soap message monitor. * Execute this script to add file handler and logger categories: {quote} connect batch /subsystem=logging/periodic-rotating-file-handler=SOAPMSG:add(file={path=>"soapmsg.log", relative-to=>"jboss.server.log.dir"}, named-formatter=PATTERN, suffix=.yyyy-MM-dd, append=true) /subsystem=logging/logger=org.apache.cxf.services:add(level=INFO, handlers=[SOAPMSG]) /subsystem=logging/logger=org.apache.cxf.services:write-attribute(name="use-parent-handlers", value="false") run-batch {quote} _Note: This will log soap message for all endpoints. If only want to view one specific endpoint , the logger can be created with service name and port name's local part like:_ {quote} /subsystem=logging/logger=org.apache.cxf.services.EndpointSevice.EndpointPort:add(level=INFO, handlers=[SOAPMSG]) /subsystem=logging/logger=org.apache.cxf.services.EndpointSevice.EndpointPort(name="use-parent-handlers", value="false"){quote} _The deployed endpoint has this @WebServbice annotion:_ {quote}@WebService(name="TestEndpoint", serviceName="EndpointService", portName="EndpointPort", targetNamespace="http://jbossws.jboss.org/test") public class TestEndpoint { ... }{quote} * Log in wildfly/EAPadmin console and go to Runtime->Sever->Standalone Server>Log Files -> View and select the soap message output file soapmsg.log to view the inbound/outbound soap message. soap message can be accessed with CLI: {quote} /subsystem=logging/:read-log-file(name=soapmsg.log){quote} > Message log browser functionality > --------------------------------- > > Key: JBWS-3586 > URL: https://issues.jboss.org/browse/JBWS-3586 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration, productivity > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-5.2.0.Final > > > I'd like to see a SOAP message log browsing functionality for JBossWS / JBoss AS. This should basically be something like the Apache CXF LogBrowser [1] yet integrated with the AS management / console. > We should also evaluate whether it's possible to convert CXF generated logs into the JBossWS SPI Records [4] (in any case, any AS level handling of cxf stuff needs to be hidden behind JBossWS SPI). > Finally we might explore additional functionalities / uses of logs which could be implemented; see for instance [2] and [3]. > [1] http://cxf.apache.org/docs/logbrowser-configuration.html > [2] http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging... > [3] http://sberyozkin.blogspot.it/2012/07/cxf-log-browser-demo.html > [4] https://community.jboss.org/wiki/JBossWS-RecordsManagement -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3586) Message log browser functionality

by Jim Ma (JIRA)

[ https://issues.jboss.org/browse/JBWS-3586?page=com.atlassian.jira.plugin.... ] Jim Ma updated JBWS-3586: ------------------------- Assignee: Jim Ma > Message log browser functionality > --------------------------------- > > Key: JBWS-3586 > URL: https://issues.jboss.org/browse/JBWS-3586 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf, jbossws-integration, productivity > Reporter: Alessio Soldano > Assignee: Jim Ma > Fix For: jbossws-cxf-5.2.0.Final > > > I'd like to see a SOAP message log browsing functionality for JBossWS / JBoss AS. This should basically be something like the Apache CXF LogBrowser [1] yet integrated with the AS management / console. > We should also evaluate whether it's possible to convert CXF generated logs into the JBossWS SPI Records [4] (in any case, any AS level handling of cxf stuff needs to be hidden behind JBossWS SPI). > Finally we might explore additional functionalities / uses of logs which could be implemented; see for instance [2] and [3]. > [1] http://cxf.apache.org/docs/logbrowser-configuration.html > [2] http://cxf.apache.org/docs/debugging-and-logging.html#DebuggingandLogging... > [3] http://sberyozkin.blogspot.it/2012/07/cxf-log-browser-demo.html > [4] https://community.jboss.org/wiki/JBossWS-RecordsManagement -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3947) Add performance tests to the build

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3947: ------------------------------------- Summary: Add performance tests to the build Key: JBWS-3947 URL: https://issues.jboss.org/browse/JBWS-3947 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf, productization Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final In order to simplify performance testing, we should be able to run benchmarks easily, the same way integration tests are run. We could have jmeter integrated with Maven to run the benchmark tests that we currently have disabled in the shared testsuite. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3946) WS-I BSP test failures about R3217 & R3223

by Jim Ma (JIRA)

Jim Ma created JBWS-3946: ---------------------------- Summary: WS-I BSP test failures about R3217 & R3223 Key: JBWS-3946 URL: https://issues.jboss.org/browse/JBWS-3946 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.0.Final Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-5.2.0.Final With cxf is upgraded to 3.1.2 , wss4j 2.1.2 is shipped. There is issue in ws-security-stax module which doesn't use UTC time format for <wsu:Expires> and <wsu:Created> elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3887) Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-3887?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-3887: ------------------------------ Assignee: (was: Jan Blizňák) > Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2 > ------------------------------------------------------ > > Key: JBWS-3887 > URL: https://issues.jboss.org/browse/JBWS-3887 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Bartosz Baranowski > > JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3887) Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-3887?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-3887: ------------------------------ Assignee: Jan Blizňák > Handle SOAP Fault properly for 400 in SOAP 1.1 and 1.2 > ------------------------------------------------------ > > Key: JBWS-3887 > URL: https://issues.jboss.org/browse/JBWS-3887 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Jan Blizňák > > JBossWS SOAPConnectionImpl should handle 400 code properly(for 1.1 and 1.2 protocol versions) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3945) Set property that causes 400 error message to be returned by apache CXF.

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3945?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3945: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.0.Final (was: jbossws-cxf-5.1.0.Final) > Set property that causes 400 error message to be returned by apache CXF. > ------------------------------------------------------------------------ > > Key: JBWS-3945 > URL: https://issues.jboss.org/browse/JBWS-3945 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.1.0.Beta1 > Reporter: R Searls > Priority: Minor > Fix For: jbossws-cxf-5.2.0.Final > > > Change ./modules/client/src/main/java/org/jboss/wsf/stack/cxf/saaj/SOAPConnectionImpl.java -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 7 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-issues September 2015