March 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2871) HttpGatewayServlet: add support for extracting CLIENT-CERT certificates

by Daniel Bevenius (JIRA)

HttpGatewayServlet: add support for extracting CLIENT-CERT certificates ------------------------------------------------------------------------ Key: JBESB-2871 URL: https://jira.jboss.org/jira/browse/JBESB-2871 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples, Security Reporter: Daniel Bevenius Assignee: Daniel Bevenius HttpGatewayServlet currently support extraction of basic authentication (username and password) via HttpServletSecUtil. This task should add support for extracting certificate from the request. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-3089) New XSLT Action

by Fernando Ribeiro (JIRA)

New XSLT Action --------------- Key: JBESB-3089 URL: https://jira.jboss.org/jira/browse/JBESB-3089 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: XsltAction.rar I've developed a XSLT action that takes the properties as a parameter: http://github.com/fribeiro1/XsltAction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
7
0 / 0

[JBoss JIRA] Created: (JBESB-3087) New HTTP Action

by Fernando Ribeiro (JIRA)

New HTTP Action --------------- Key: JBESB-3087 URL: https://jira.jboss.org/jira/browse/JBESB-3087 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro I've developed a HTTP action that takes headers and parameters, unlike HttpRouter: http://github.com/fribeiro1/HttpAction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
7
0 / 0

[JBoss JIRA] Created: (JBESB-3146) New Splitter Action

by Fernando Ribeiro (JIRA)

New Splitter Action ------------------- Key: JBESB-3146 URL: https://jira.jboss.org/jira/browse/JBESB-3146 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro I've created an action that uses XPath to split messages, expect the community to add more to it: http://github.com/fribeiro1/SplitterAction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-3086) New Set/Remove Message Property Actions

by Fernando Ribeiro (JIRA)

New Set/Remove Message Property Actions --------------------------------------- Key: JBESB-3086 URL: https://jira.jboss.org/jira/browse/JBESB-3086 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: RemoveMessagePropertyAction.rar, SetMessagePropertyAction.rar I've developed two useful actions that can be added to JBoss ESB: http://github.com/fribeiro1/SetMessagePropertyAction http://github.com/fribeiro1/RemoveMessagePropertyAction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
9
0 / 0

[JBoss JIRA] Created: (JBESB-3125) New File Reader Action

by Fernando Ribeiro (JIRA)

New File Reader Action ---------------------- Key: JBESB-3125 URL: https://jira.jboss.org/jira/browse/JBESB-3125 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: FileReaderAction.rar I've developed a simple action to read files from the classpath or the filesystem: http://github.com/fribeiro1/FileReaderAction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3118) New DB Action

by Fernando Ribeiro (JIRA)

New DB Action ------------- Key: JBESB-3118 URL: https://jira.jboss.org/jira/browse/JBESB-3118 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Reporter: Fernando Ribeiro Attachments: DbAction.rar I've developed a DB Action with support for many JDBC types, multiple result sets and update counts, etc: http://github.com/fribeiro1/DbAction -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JBESB-3592) Test out jUDDI RMI transport; update documentation

by Tom Cunningham (JIRA)

Test out jUDDI RMI transport; update documentation -------------------------------------------------- Key: JBESB-3592 URL: https://issues.jboss.org/browse/JBESB-3592 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 The docs suggest using jUDDI's RMITransport, but ESB has it's own version to workaround JNDI issues. Investigate whether this has been fixed in jUDDI, and if not, update the documentation so that it is suggesting the correct transport. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3316) jBPM JCA inflow need to support JMSProviderAdapter

by Kevin Conner (JIRA)

jBPM JCA inflow need to support JMSProviderAdapter -------------------------------------------------- Key: JBESB-3316 URL: https://jira.jboss.org/jira/browse/JBESB-3316 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.4 CP3 Reporter: Kevin Conner This is to allow the initial context to be provided by an adapter rather than defaulting to the server values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3589) SOAP Header data from SOAPMessageContext in JAXWS Handlers.

by CYRIL GERBIER (JIRA)

SOAP Header data from SOAPMessageContext in JAXWS Handlers. ------------------------------------------------------------ Key: JBESB-3589 URL: https://issues.jboss.org/browse/JBESB-3589 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP2 Environment: Release ID: JBoss [SOA] 5.0.2.GA_SOA (build: SVNTag=5.0.2.GA_SOA date=201006221603) java version "1.6.0_07" Java(TM) SE Runtime Environment (build 1.6.0_07-b06) Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing) Reporter: CYRIL GERBIER I would like to add some JAXWS handlers in web services SOAP. I am using JBOSS SOAP 5.0.2.GA_SOA release (see boot.log for more details). I made a sample based on webservice_wsaddressing quickstart samples (samples\quickstarts\webservice_wsaddressing): - for WSAClient, I added a new JAXWS handler (MyClientHandler extends SOAPHandler<SOAPMessageContext>). This one adds context data in SOAPHeader from xml marshalled by JAXB. - for StatefulEndpointImpl, I added a new JAXWS handler (MyServerHandler implements SOAPHandler<SOAPMessageContext>). This one reads xml context data in SOAPHeader and give an context object from JAXB. This system works fine with JBOSS AS 4.2 and CXF stack. But using, JBOSS SOAP 5.0.2.GA and native JBossws stack, I encountered severals problems: - on client side, data are not correctly sent : hereafter a sample of HTTP SOAP Request sent : <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <cv:ContextVersion xmlns:cv="http://si.msa.fr/GestionnaireEchangesInternes/SOA/AppelServices">1.0</cv:ContextVersion> <ns2:MDWTargetContext xmlns:ns2="http://si.msa.fr/GestionnaireEchangesInternes/SOA/AppelServices/Objets/Re..."/> <wsa:To>uri:jaxrpc-samples-wsaddressing/TestService</wsa:To> <wsa:ReplyTo> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address> <wsa:ReferenceParameters> <ns1:clientid xmlns:ns1="http://somens">clientid-2</ns1:clientid> </wsa:ReferenceParameters> </wsa:ReplyTo> <wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:Action> <wsa:MessageID>urn:uuid:6f521ca2-fa85-49a7-9f1f-f9719237629e</wsa:MessageID> </env:Header> <env:Body> <ns1:getItems xmlns:ns1="http://webservice.webservicewsa.quickstart.samples.esb.soa.jboss.org/"/> </env:Body> </env:Envelope> We can see that MDWTargetContext has no data when marshalling in SOAPHeader (just xml structure) whereas it is correct when marshalling in System.out: <MDWTargetContext xmlns="http://si.msa.fr/GestionnaireEchangesInternes/SOA/AppelServices/Objets/Re..."> <CORGAMO>021</CORGAMO><DPT>82</DPT><ED>E</ED><ND>N</ND></MDWTargetContext> - on server side, when I send a manually a correct request (because of issue on client) : <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"> <cv:ContextVersion xmlns:cv="http://si.msa.fr/GestionnaireEchangesInternes/SOA/AppelServices">1.0</cv:ContextVersion> <ns2:MDWTargetContext xmlns:ns2="http://si.msa.fr/GestionnaireEchangesInternes/SOA/AppelServices/Objets/Re..."> <ns2:CORGAMO>021</ns2:CORGAMO> <ns2:DPT>82</ns2:DPT> <ns2:ED>E</ns2:ED> <ns2:ND>N</ns2:ND> </ns2:MDWTargetContext> <wsa:To>uri:jaxrpc-samples-wsaddressing/TestService</wsa:To> <wsa:ReplyTo> <wsa:Address>http://www.w3.org/2005/08/addressing/anonymous</wsa:Address> <wsa:ReferenceParameters> <ns1:clientid xmlns:ns1="http://somens">clientid-2</ns1:clientid> </wsa:ReferenceParameters> </wsa:ReplyTo> <wsa:Action>http://org.jboss.ws/addressing/stateful/action</wsa:Action> <wsa:MessageID>urn:uuid:6f521ca2-fa85-49a7-9f1f-f9719237629e</wsa:MessageID> </env:Header> <env:Body> <ns1:getItems xmlns:ns1="http://webservice.webservicewsa.quickstart.samples.esb.soa.jboss.org/"/> </env:Body> </env:Envelope> datas from ns2:MDWTargetContext are correctly unmarshalled, by I can't read ContextVersion data : node is found but getTextContent returns null: 17:34:15,953 INFO [MyServerHandler] Fournisseur : Request message 17:34:15,984 INFO [MyServerHandler] ContextVersion : 17:34:15,984 INFO [MyServerHandler] TargetContext : ED E 17:34:15,984 INFO [MyServerHandler] TargetContext : ND N 17:34:15,984 INFO [MyServerHandler] TargetContext : CORGAMO 021 17:34:15,984 INFO [MyServerHandler] TargetContext : DPT 82 Can you help me to solve this problem : - to send xml context data from client in SOAP Header - to receive correcly ContextVersion (why getTextContext returns null). I attach quickstart sample in order to reproduce the problem. Please copy it to quickstart sample directory and type "ant deploy" to deploy esb archive and "ant runtest" to test from client. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2011