July 2008 - jboss-user - Jboss List Archives

[JBossWS] - Re: Error SAP WS-Security client calling JBoss Security WS

by lall2

Hi, i found a similar case with a Microsoft WCF client calling an Oracle WS: http://weblogs.asp.net/gsusx/archive/2006/10/20/WCF-Oracle-Application-Se... The last code listing contains a WS-Security request trace with an element KeyInfo without the ValueType attribute: | ... | <KeyInfo xmlns="http://www.w3.org/2000/09/xmldsig#"> | <o:SecurityTokenReference> | <o:Reference URI="#_1"/> | </o:SecurityTokenReference> | </KeyInfo> | ... | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167276#4167276 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167276

17 years, 8 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Hibernate/Writes but does not loads

by skajotde

"pozzo" wrote : Kamil, | | It seems that the cache is working, in the log I see 'cache hit'. But I am very disappointed because the performance is equal and in some cases worse than without cache. And the sql queries continue to appear in the console, which seems strange. | | I know that the cache is not a silver bullet, but in this case, leaves much to be desired. Is there any explanation for this poor performance? | | thank-you | Look out at entity dependencies, if are not lazy that are get every time. What SQL are executed ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167275#4167275 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167275

17 years, 8 months

1
0
0 / 0

[JBoss Tools (users)] - Re: XHTML files and content assist with custom tags

by max.andersen＠jboss.com

Add jsf capabilities does not have any constraint on project structure AFAIK. You can e.g. do it on a seam-gen'ed app if you want to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167274#4167274 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167274

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: JBoss WS security throws javax.xml.ws.WebServiceExceptio

by r12345_2003

Can anyone help? I'm really stuck with this problem, any hints would be really appreciated! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167272#4167272 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167272

17 years, 8 months

1
0
0 / 0

[JBossWS] - Error SAP WS-Security client calling JBoss Security WS

by lall2

Hi, I get the following exception when the SAP system invokes a JBossWS WS-Security WS: | ERROR [WSSecurityDispatcher] Internal error occured handling inbound message: | org.jboss.ws.extensions.security.exception.WSSecurityException: Inavliad message, Reference element is missing a ValueType | at org.jboss.ws.extensions.security.element.DirectReference.<init>(DirectReference.java:78) | at org.jboss.ws.extensions.security.element.Reference.getReference(Reference.java:39) | at org.jboss.ws.extensions.security.element.SecurityTokenReference.<init>(SecurityTokenReference.java:61) | at org.jboss.ws.extensions.security.KeyResolver.extractSecurityTokenReference(KeyResolver.java:70) | at org.jboss.ws.extensions.security.KeyResolver.resolvePublicKey(KeyResolver.java:161) | at org.jboss.ws.extensions.security.element.Signature.<init>(Signature.java:56) | at org.jboss.ws.extensions.security.element.SecurityHeader.<init>(SecurityHeader.java:87) | at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:175) | at org.jboss.ws.extensions.security.WSSecurityDispatcher.decodeMessage(WSSecurityDispatcher.java:219) | at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:83) | at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer.handleInbound(WSSecurityHandlerServer.java:41) | It looks to me that this occurs when the SAP's request Envelope/Header/Security/Signature/KeyInfo/SecurityTokenReference/Reference element is checked. If so, can this check in org.jboss.ws.extensions.security.element.DirectReference be skipped, since the ValueType attribute of Envelope/Header/Security/Signature/KeyInfo/SecurityTokenReference/Reference does not contain specific information? Additionally, the same value type is also contained in Envelope/Header/Security/BinarySecurityToken element with a wsu:Id="token-2-1215429956710-11328770" attribute referencing/referenced in the URI attribute of Envelope/Header/Security/Signature/KeyInfo/SecurityTokenReference/Reference I have outlined the important sections in bold of the two following SOAP trace listings. a) The request from the SAP system looks as follows: | <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"> | <SOAP:Header> | <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..." SOAP:mustUnderstand="1"> | <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." | wsu:Id="sap-17" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu..."> |  | </wsse:BinarySecurityToken> | <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." wsu:Id="wsu-targetID-4f51c3d1-4c31-11dd-c804-52325dc89402"> | <wsu:Created ValueType="xsd:dateTime">2008-07-07T14:30:55Z</wsu:Created> | <wsu:Expires ValueType="xsd:dateTime">2008-07-07T14:31:55Z</wsu:Expires> | </wsu:Timestamp> | <xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="EK7176284"> | <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"/> | <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <wsse:SecurityTokenReference> | <wsse:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu...">tZwIZ4EyuXCscFmLexbBSDw4pXc=</wsse:KeyIdentifier> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | <xenc:CipherData> | <xenc:CipherValue>dN7Jdu9ZrqKdO4gmMhVVqEraDWATPkXyfaOwqTJ9iiNBGslSZxS9wDPaMms+1AVIsEj+zPxOP1m9 | iGzNZgUj36ytFnfMPEYy79LZhjlsrRcuNNIYdIosI1aR55Cg8LWhmExp8xfPwcaero2ku6mnHqZT | PCoAWq859YRnQsmxoF8=</xenc:CipherValue> | </xenc:CipherData> | <xenc:ReferenceList> | <xenc:DataReference URI="#ED52721394"/> | </xenc:ReferenceList> | </xenc:EncryptedKey> | <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:SignedInfo> | <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> | <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> | <ds:Reference URI="#wsuid-body-4f51c3d0-4c31-11dd-962a-52325dc89402"> | <ds:Transforms> | <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> | </ds:Transforms> | <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> | <ds:DigestValue>uPX1GhMMPxAyFhdKOyOWTSXoaFg=</ds:DigestValue> | </ds:Reference> | <ds:Reference URI="#wsu-targetID-4f51c3d1-4c31-11dd-c804-52325dc89402"> | <ds:Transforms> | <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> | </ds:Transforms> | <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> | <ds:DigestValue>720bTnzpOnIall0ooGeyk32Syqs=</ds:DigestValue> | </ds:Reference> | </ds:SignedInfo> | <ds:SignatureValue>AzlqPk9OCrqetQVS2BPZ6u3ZwMHGtPGgYQwMTBLnREKPhNEI/Cb8o3EJAgIfB73kKgKFmw0Dj3WN | c+MesXZ1LEOqvT2YDq6Jxpz4I/cYWbY+79tKKmuOfstfoQzBGn8uo4+wwR8Vn3l0Ns/DuYHwvnNR | 34RzPbLDllZUW4qdXmE=</ds:SignatureValue> | <ds:KeyInfo> | <wsse:SecurityTokenReference> | <wsse:Reference URI="#sap-17"/> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | </ds:Signature> | <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." wsu:Id="sap-17" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu..."> | |  | | </wsse:BinarySecurityToken> | <wsse:BinarySecurityToken ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu..."></wsse:BinarySecurityToken> | <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." wsu:Id="sap-17" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu..."></wsse:BinarySecurityToken> | </wsse:Security> | </SOAP:Header> | <SOAP:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." wsu:Id="wsuid-body-4f51c3d0-4c31-11dd-962a-52325dc89402"> | <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="ED52721394"> | <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"/> | <xenc:CipherData> | <xenc:CipherValue></xenc:CipherValue> | </xenc:CipherData> | </xenc:EncryptedData> | </SOAP:Body> | </SOAP:Envelope> | The SAP request only has the ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." attribute within the Envelope/Header/Security/BinarySecurityToken element. The JBoss request ValueType attribute is contained in Envelope/Header/Security/BinarySecurityToken and Envelope/Header/Security/Signature/KeyInfo/SecurityTokenReference/Reference. Is the second ValueType attribute required by JBossWS internal processing? b) When a JBossWS WS-Security client calls an SAP WS-Security WS, there are no problems. The request looks as follows: | <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> | <env:Header> | <wsse:Security env:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..." xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..."> | <wsu:Timestamp wsu:Id="timestamp"> | <wsu:Created>2008-07-07T11:25:56.523Z</wsu:Created> | <wsu:Expires>2008-07-07T11:26:26.523Z</wsu:Expires> | </wsu:Timestamp> | <wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu..." ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..." wsu:Id="token-2-1215429956710-11328770"> | |  | </wsse:BinarySecurityToken> | <xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> | <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"/> | <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <wsse:SecurityTokenReference wsu:Id="reference-5-1215429957054-30222347"> | <wsse:KeyIdentifier EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-secu..." ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil...">NS0xdPUqf/9XQw4/YZ+lMnTguf8=</wsse:KeyIdentifier> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | <xenc:CipherData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> | <xenc:CipherValue xmlns:xenc="http://www.w3.org/2001/04/xmlenc#">dqWVJQ08cTvj6O/lbEC+e6giBMlU5msZsGS5fShB1bdkkGUh1Fc0Kk38FNYfUW/EZZu0H3/YDInN | W7HcQle5KL0LpD1vGCNlXElGlOfRYdX96stIL8e6r386lglQdYxdL78RaPlI6OF4fnD6XCS3QfM9 | XhODTHWQf8LIw2xQVyI=</xenc:CipherValue> | </xenc:CipherData> | <xenc:ReferenceList xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> | <xenc:DataReference URI="#encrypted-4-1215429956976-6044039" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"/> | </xenc:ReferenceList> | </xenc:EncryptedKey> | <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:SignedInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/> | <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/> | <ds:Reference URI="#element-1-1215429956523-31952022" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:Transforms xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/> | </ds:Transforms> | <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/> | <ds:DigestValue xmlns:ds="http://www.w3.org/2000/09/xmldsig#">ZmQ7YZUv5swk3OnUn5X3w2JyenE=</ds:DigestValue> | </ds:Reference> | <ds:Reference URI="#timestamp" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:Transforms xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/> | </ds:Transforms> | <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" xmlns:ds="http://www.w3.org/2000/09/xmldsig#"/> | <ds:DigestValue xmlns:ds="http://www.w3.org/2000/09/xmldsig#">OyIUQGrnwhkJoimoqv07+ML45IE=</ds:DigestValue> | </ds:Reference> | </ds:SignedInfo> | <ds:SignatureValue xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> |  | </ds:SignatureValue> | <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <wsse:SecurityTokenReference wsu:Id="reference-3-1215429956710-15774883"> | <wsse:Reference URI="#token-2-1215429956710-11328770" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..."/> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | </ds:Signature> | </wsse:Security> | </env:Header> | <env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..." wsu:Id="element-1-1215429956523-31952022"> | <xenc:EncryptedData Id="encrypted-4-1215429956976-6044039" Type="http://www.w3.org/2001/04/xmlenc#Content" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> | <xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#aes128-cbc" xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"/> | <xenc:CipherData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> | <xenc:CipherValue xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> |  | </xenc:CipherValue> | </xenc:CipherData> | </xenc:EncryptedData> | </env:Body> | </env:Envelope> | I use version: JBoss 4.2.2 - JBossWS 3.0.1. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167271#4167271 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167271

17 years, 8 months

1
0
0 / 0

[JBoss jBPM] - Call JBPM process with EJB

by ihorvath

Hi All! Could you show me an example to call my JBPM project with EJB? How can i access my projec what run in JBPM server. A cannot find any examples in documentation for EJB or WebService call! Please help me! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167270#4167270 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167270

17 years, 8 months

1
0
0 / 0

Delivery Notification <provea@provea.ru>

by Postmaster＠lists.jboss.org

This is a delivery status notification, automatically generated by MTA mx1.editionsatlas.ch on Tue, 29 Jul 2008 11:46:09 +0200 Regarding recipient(s) : provea(a)provea.ru Delivery status : Failed. Message could not be delivered to domain <provea.ru> .Failed while initiating the protocol. <[('provea(a)provea.ru', 550, '5.7.1 Unable to relay for provea(a)provea.ru')]> MTA Response :550 The original message headers are included as attachment.

17 years, 8 months

1
0
0 / 0

[JBoss jBPM] - Re: how to integrate commandservicebean

by mputz

Check your datasource configuration file, it must have a section for the type-mapping: <metadata><type-mapping>Hypersonic SQL</type-mapping></metadata> | where the value matches one of the entries in server/jbpm/conf/standardjbosscmp-jdbc.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167265#4167265 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167265

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Use of PostCreate in JaxWS WebService implementation cla

by adinn

Apologies, for all occurences of PostCreate please read PostConstruct View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167264#4167264 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167264

17 years, 8 months

1
0
0 / 0

[JBossWS] - Re: Use of PostCreate in JaxWS WebService implementation cla

by adinn

I checked up on Sun's online documentation for Metro and it confirms that PostCreate and PreDestroy annotated methodsof a WebService are supposed to be invoked by JaxWS. See: | https://jax-ws.dev.java.net/jax-ws-ea3/docs/annotations.html | The JaxWS 2.0 and 2.1 spec both refer to JSR 109 in section 11 when discussing the deployment model for @WebService annotated classes. So, I'm going to raise a JIRA against JBossWS Native for not honouring these annotations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167263#4167263 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4167263

17 years, 8 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 July 2008