July 2008 - jboss-user - Jboss List Archives

[JBoss Portal] - Custom-Portlet-Mode in Jboss-Portletcontainer-2.0.0

by terroene

Hello again, does the Jboss-Portletcontainer-2.0.0 support custom-portlet-modes? I can't get it to work! I tried this: portlet.xml: | <?xml version='1.0' encoding='UTF-8' ?> | <portlet-app xmlns='http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:schemaLocation='http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd' version='2.0'> | <portlet> | <description>AuthenticationPortlet</description> | <portlet-name>AuthenticationPortlet</portlet-name> | <display-name>AuthenticationPortlet</display-name> | <portlet-class>fraunhofer.isst.portlets.AuthenticationPortlet</portlet-class> | <expiration-cache>0</expiration-cache> | <supports> | <mime-type>text/html</mime-type> | <portlet-mode>VIEW</portlet-mode> | <portlet-mode>HELP</portlet-mode> | <portlet-mode>UNAUTHENTICATED</portlet-mode> | </supports> | <resource-bundle>fraunhofer.isst.portlets.messages</resource-bundle> | <portlet-info> | <title>AuthenticationPortlet</title> | <short-title>AuthenticationPortlet</short-title> | </portlet-info> | </portlet> | <custom-portlet-mode> | <description xml:lang="en">Authentication failure mode</description> | <portlet-mode>UNAUTHENTICATED</portlet-mode> | </custom-portlet-mode> | </portlet-app> | I'm iterating through all supported modes in doView(); | System.out.println(request.getPortalContext().getPortalInfo()); | Enumeration modeEnum = | request.getPortalContext().getSupportedPortletModes(); | System.out.println("<p>Modes <br />"); | while (modeEnum.hasMoreElements()) | { | PortletMode pMode = (PortletMode) | modeEnum.nextElement(); | | System.out.println("<li> <a href=\"" + pMode.toString() + | "\">" + pMode + "</a></li>"); | } | This returns only: | 16:58:07,642 INFO [STDOUT] JBossPortal/1.0 | 16:58:07,642 INFO [STDOUT] <p>Modes <br /> | 16:58:07,642 INFO [STDOUT] <li> <a href="view">view</a></li> | 16:58:07,642 INFO [STDOUT] <li> <a href="edit">edit</a></li> | 16:58:07,642 INFO [STDOUT] <li> <a href="help">help</a></li> | So, how can I use supported-portlet-mode? Best regards, rene View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162335#4162335 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162335

17 years, 9 months

1
0
0 / 0

Delivery Notification <diman@eng.auburn.edu>

by Postmaster＠lists.jboss.org

This is a delivery status notification, automatically generated by MTA im5.duc.auburn.edu on Thu, 03 Jul 2008 09:56:53 -0500 Regarding recipient(s) : diman(a)eng.auburn.edu Delivery status : Failed. Message could not be delivered to domain <eng.auburn.edu> .Failed while initiating the protocol. <[('diman(a)eng.auburn.edu', 550, '5.1.1 <diman(a)eng.auburn.edu>... User unknown')]> MTA Response :550 The original message headers are included as attachment.

17 years, 9 months

1
0
0 / 0

[JBoss jBPM] - process variable is blank

by scholtz.albert

I have the following code in my process definiton: <task-node name="viewBill"> | <event type="node-leave"> | <script> | <variable name="success" access="write" /> | <expression>"#{billAction.success}"</expression> | </script> | </event> | <transition to="successful" name="toSuccessful"></transition> | </task-node> | | <decision name="successful" expression="#{billAction.success}"> | <transition to="success" name="true"></transition> | <transition to="failure" name="false"></transition> | </decision> In my decision tag the billAction.success variable always has a value of either ture or false which is what i expected. When i run the process instance through my page it transitions to the corrrect node. However the variable "success" is always blank when i i check it in jpbm admin console. I would like this true or false value to be reflected there. Any help will be appreciated Albert Scholtz View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162334#4162334 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162334

17 years, 9 months

1
0
0 / 0

[Beginners Corner] - Re: Load Library problem

by tgcosta

Hey Peter, let me explain with more details what's happened. I need to make some tests with JBoss in a x64 ambient. Then i did a download of the Java Virtual Machine (JDK 1.5.0_15) that can works in a x64 system and get a stable version of JBoss, i choice 4.2.2.GA version. In my test, i need to put one instance of JBoss like a windows service. This is ok but when i try to initiate this service appear this message: "The JBoss service on Local Computer started and then stopped. Some services stop automatically if they have no work to do..." After this, i looking for more details about this message, and i search for this in Event Viewer, then i found it: 1Âº message: "The LoadLibrary function failed for the following reason: LoadLibrary is not a valid Win32 application." 2Âº message: "Could not load the Java Virtual Machine." 3Âº message: "The JBoss service failed to start." Is this what's happened with me. Can you help me? I'm thankful for your attention. Thiago. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162333#4162333 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162333

17 years, 9 months

1
0
0 / 0

[JBoss Tools (users)] - Re: Help Running Wizard-generated project as an EAR

by c0upal

Hi Im using JBoss AS 4.2 I created a Seam application called MyFirstSeam. So it has 4 Project Folders: MyFirstSeam, MyFirstSeam-ear, -ejb, -test. Then I have succesffully run Seam Generate Entities, so i have Entities already. I Right Clicked MyFirstSeam folder, and Clicked Run-As Server. No code yet. I got the error, and then looked at the console... ....DeploymentException ... cannot find .... default\deploy\MyFirstSeam-ear.ear\jboss-seam.jar. I copied all the jar files manually from \myWorkspace\MyFirstSeam-ear\ to the deploy Folder and it worked OK. But my question is, isn't Eclipse suppose to copy that automatically for me? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162331#4162331 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162331

17 years, 9 months

1
0
0 / 0

[JBossWS] - JBossWS, Websphere 5.1 WS-Security interoperability

by forgr

I'm developing a webservice client using jbossws native stack v2.0.4 that interact with a web service deployed in websphere 5.1. Authentication was managed by ws-security username profile. By the way, webspehere ws-security implementation was based on draft 13 of ws-security standard while jbossws implements final specs. The result was the following error: 16:14:16,093 INFO [STDOUT] 16:14:16,078 WARN DefaultExceptionHandler:90 - Unhandled exception caught by the Stripes default exception handler. javax.xml.ws.soap.SOAPFaultException: com.ibm.wsspi.wssecurity.SoapSecurityException: The Application Server expected a Security header with the http://schemas.xmlsoap.org/ws/2003/06/secext or http://schemas.xmlsoap.org/ws/2002/07/secext or http://schemas.xmlsoap.org/ws/2002/04/secext namespace, but it was not found. at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) So, I can: - suggest an upgrade of websphere to v6 (not possible!!!) - use websphere webservice gateway (8() - downgrade to draft 13 ws-security specs used by jbossws (is possible?) - generate ws-security tag via a custom handler (is possible?) - any other ideas? Thanks, ForGR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162327#4162327 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162327

17 years, 9 months

1
0
0 / 0

[JBoss Portal] - Re: WSRP: JBoss Portal (2.6.6) Consumer, Liferay 4 Producer

by Lightguard

Found the problem, but I'm really not sure of good solution :) Because we're using the relaxed checking it tries to do a substitution on a null string. We figure out the capabilities (which handles the markupTypes) before we do the MetaInfo and PortletInfo so we could use the first locale in the capabilities as the default, or we could simply default to English, but I'm not sure how great either of those two options are. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162326#4162326 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162326

17 years, 9 months

1
0
0 / 0

[JBossWS] - Re: Problem WS-Security Standard implementation difference -

by alessio.soldano＠jboss.com

You just need to configure the token reference type in JBossWS Native; see this: http://jbws.dyndns.org/mediawiki/index.php?title=WS-Security_options#Toke... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162318#4162318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162318

17 years, 9 months

1
0
0 / 0

[JBoss Messaging] - Re: Exception when starten 2nd node

by mbreuer

I tried it in the other way and moved the queue definitions from deploy-hasingleton to deploy folder. | <server> | <mbean code="org.jboss.jms.server.destination.QueueService" | name="jboss.messaging.destination:service=Queue,name=..." | xmbean-dd="xmdesc/Queue-xmbean.xml"> | <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends> | <depends>jboss.messaging:service=PostOffice</depends> | <attribute name="Clustered">true</attribute> | </mbean> | </server> | Both servers are now starting without any error, the queues are found. My test-app does following: 1. call session bean 2. session bean puts message to queue A 3. mdb (queue A) receives the message Locally this works fine. Then i moved 3. to the other node and started again. 1.+2. work but 3. (now on other cluster node) does not receive the message. What's wrong? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162316#4162316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162316

17 years, 9 months

1
0
0 / 0

[JBossWS] - Problem WS-Security Standard implementation difference --> i

by lall2

Hi all, I built a JBoss 4.2.2 JBossWS Native 2.0.4/3.0.1 WS Client with the following jboss-wsse-client.xml security configuration: | <?xml version="1.0" encoding="UTF-8"?> | <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> | <config> | <timestamp ttl="30"/> | <sign type="x509v3" alias="SimpleClientCertPrivateKey" includeTimestamp="true"/> | <encrypt type="x509v3" alias="SimpleClientCert"/> | <requires> | <signature/> | <encryption/> | </requires> | </config> | <timestamp-verification createdTolerance="500" warnCreated="true" expiresTolerance="100" warnExpires="true"/> | </jboss-ws-security> | All certificates and KeyStores have been installed properly on both sides. The resulting SOAP message trace looks as follows: (Listing 1) | <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-06-13T12:45:10.976Z</wsu:Created> | <wsu:Expires>2008-06-13T12:45:40.976Z</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-1213361111663-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-1213361112194-30222347"> | <wsse:Reference URI="#token-2-1213361111663-11328770" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..."/> | </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#">lg6tOjzqKs26HX6KFk1nLA5YF5W5fQZ6dh2mzM9/V3r5Pg80vLz4x0EJ10Y1KdhXH08ijZxRZWjf | v1dqulorSnIyV7X0uk25y/OMDmkVYQ/VlQF7bxZr/5Q+UB6YwLy74N1jpx7lo4BZXUM9kEZmgFAo | o8SW8P3AcSgBAUoOpOc=</xenc:CipherValue> | </xenc:CipherData> | <xenc:ReferenceList xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"> | <xenc:DataReference URI="#encrypted-4-1213361112116-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-1213361110976-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#">l2LG3Bc2Rk+LgAjU2OP2vrVwYBM=</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#">GNamS8F3tDSDlfUzNxIzfYZpXdc=</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-1213361111663-15774883"> | <wsse:Reference URI="#token-2-1213361111663-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-1213361110976-31952022"> | <xenc:EncryptedData Id="encrypted-4-1213361112116-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> | | Due to researching, I know that the WebService system expects a reqeuest that looks as follows (Listing 2) | <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-9" 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-1f10b320-0181-11dd-aebd-00144f2515b0"> | <wsu:Created ValueType="xsd:dateTime">2008-04-03T13:23:17Z</wsu:Created> | <wsu:Expires ValueType="xsd:dateTime">2008-04-03T13:25:17Z</wsu:Expires> | </wsu:Timestamp> | <xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Id="EK52789332"> | <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...">yk+Civrkf+wQdj30aJid9VGnjtY=</wsse:KeyIdentifier> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | | <xenc:CipherData> | <xenc:CipherValue> | |  | | </xenc:CipherValue> | </xenc:CipherData> | <xenc:ReferenceList> | <xenc:DataReference URI="#ED13608949"/> | </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-1f108c10-0181-11dd-838e-00144f2515b0"> | <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>UaW58GCrg/nrA/EfW+OyHP2DCio=</ds:DigestValue> | </ds:Reference> | <ds:Reference URI="#wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0"> | <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>LFuszgJ412Fe8PRtK3W69RTXndY=</ds:DigestValue> | </ds:Reference> | </ds:SignedInfo> | <ds:SignatureValue> | |  | | </ds:SignatureValue> | <ds:KeyInfo> | <wsse:SecurityTokenReference> | <wsse:Reference URI="#sap-9"/> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | </ds:Signature> | </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-1f108c10-0181-11dd-838e-00144f2515b0"> | <xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="ED13608949"> | <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> | There is a significant difference of the Envelope/Header/Security/EncryptedKey/KeyInfo element (printed in bold). This difference causes an error message: "No SecurityTokenReference was found in the <xenc:EncryptedKey>/// element.", showing the reason for the failure of the WS Client request processing by the system implementing the WebService. JBoss Native's | <ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> | <wsse:SecurityTokenReference wsu:Id="reference-5-1213361112194-30222347"> | <wsse:Reference URI="#token-2-1213361111663-11328770" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profil..."/> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | vs. system implementing the WebService | <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...">yk+Civrkf+wQdj30aJid9VGnjtY= | </wsse:KeyIdentifier> | </wsse:SecurityTokenReference> | </ds:KeyInfo> | It looks to me that there is a difference in the implementation of WS-Security between JBossWS Native and the one of the system on which the WebService runs. I am wondering if JBossWS Metro 3.0.2 behaves like JBossWS Native, differently or even the same like in the second listing. Does anyone know that? I am about to build a test case to find out, but it would time saving to know that beforehands ;-) Obviously, when looking at http://support.microsoft.com/?scid=kb%3Ben-us%3B922779&x=8&y=13, the MS Web Services Enhancements 3.0 for Microsoft .NET implement the WS-Security like in Listing 2 with a <ds:KeyInfo>/<wsse:SecurityTokenReference>/<wsse:KeyIdentifier> instead of <ds:KeyInfo>/<wsse:SecurityTokenReference>/<wsse:Reference> Why does JBoss Native implement WS-Security in this way? Greets Andy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162315#4162315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162315

17 years, 9 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