September 2009 - jboss-user - Jboss List Archives

[jBPM Users] - Re: Implementing Escalation in jBPM 4.1

by kukeltje

Yes I think you do need that. Would be nice if you made a unit test first to test if that really works. I think it does, but not completely sure. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257102#4257102 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257102

16 years, 7 months

1
0
0 / 0

[Clustering] - Re: Failover trouble mod_jk

by bstansberry＠jboss.com

Thanks for the stack trace; yeah that's the JBAS-7123 condition. It's already fixed in SVN and will be fixed in the 5.2 which should be out late this year. It will also be fixed in JBoss Enterprise Application Platform 5. As to a workaround for AS 5.1.0, the only one I can see is to add this to your startup command: -Dorg.apache.catalina.STRICT_SERVLET_COMPLIANCE=false That will prevent the org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:132) call that is leading to the problem. That has a number of effects on the behavior of JBoss Web though, many of which I don't claim to understand. This doc gives a good overview of the effect of that flag: http://tomcat.apache.org/tomcat-6.0-doc/config/systemprops.html The "every request that is associated with a session will cause the session's last accessed time to be updated regardless of whether or not the request explicity accesses the session. (SRV.7.6) " bit on that page is the one specifically relevant to this issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257100#4257100 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257100

16 years, 7 months

1
0
0 / 0

[jBPM Users] - Re: jbpm 4.1 - Task assignment

by kukeltje

Funny, that many people are afraid of using trunk when all unit test are green, but do want to take a chance (and put (a lot of ) effort in it) to get an official release, try to find patches/diffs which might depend on other things solved (or not) and user that. But that is up to ecerybody else to decide. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257097#4257097 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257097

16 years, 7 months

1
0
0 / 0

[JBoss Web Services Users] - Authenticating SOAP Requests with WSSE UsernameToken does no

by sthatcher

I have created a simple EJB3 project and exposed it as a web service (your typical Echo service). I'm using WSSE UsernameToken headers in the SOAP requests to send authentication info. I can successfully authenticate using a username and digesting the password (e.g. Base64 encode of the SHA-1 hash). However, when I encorporate the Created node and add to the digest I get an "Invalid User" exception. But, I can use just the hash of the password (without the created node) and authenticate successfully. According to the docs from the OASIS site the digest is computed as (taken from Web Services Security UsernameToken Profile): | Password_Digest = Base64 ( SHA-1 ( nonce + created + password ) ) | I'm currently not using a Nonce since the spec says that both the Nonce and the Created are optional. It's as if the server is ignoring the fact that the created node exists. I'm not fully confident that I have the jboss-wsse-server.xml file set up or even the security header. See below for the appropriate files. Any thoughts would be appreciated. EJB3 Service: | package com.test; | | import javax.annotation.security.RolesAllowed; | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebParam; | import javax.jws.WebResult; | import javax.jws.WebService; | | import org.jboss.ws.annotation.EndpointConfig; | | @Stateless | @WebService(endpointInterface = "com.test.IEchoSession", serviceName="EchoService", portName="EchoServiceSOAP") | @EndpointConfig(configName = "Standard WSSecurity Endpoint") | public class EchoSession implements IEchoSession { | | /** | * | */ | private static final long serialVersionUID = 1L; | | @Override | @WebMethod(operationName="Echo") | @WebResult(partName="EchoResponse") | @RolesAllowed(value={"friend"}) | public String echo(@WebParam(partName="text") String text) { | return "You said: " + text; | } | | } | jboss.xml (in the EJB3 META-INF folder): <?xml version="1.0" encoding="utf-8"?> | <jboss> | <security-domain>java:/jaas/MyRealm</security-domain> | <webservices> | <context-root>/echo</context-root> | </webservices> | <enterprise-beans> | <session> | <ejb-name>EchoSession</ejb-name> | <port-component> | <port-component-name>EchoSession</port-component-name> | <port-component-uri>/EchoService</port-component-uri> | <transport-guarantee>NONE</transport-guarantee> | <secure-wsdl-access>false</secure-wsdl-access> | </port-component> | </session> | </enterprise-beans> | | </jboss> jboss-wsse-server.xml (also in the META-INF): <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config" | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="http://www.jboss.com/ws-security/config | http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd"> | <config> | <username/> | <timestamp ttl="300"/> | <timestamp-verification createdTolerance="100" warnCreated="false" expiresTolerance="100" warnExpires="false" /> | <authenticate> | <usernameAuth/> | </authenticate> | </config> | </jboss-ws-security> | On the client side (flex component) the following header get's added to the request: | private function addWSSEHeader(): SOAPHeader { | | var date : Date = new Date(); | _ds = getDateString(date); | date.minutes += 3; | | var plain : String = SHA1.hashToBase64(password.text); | | _password = SHA1.hashToBase64(_ds + password.text); | | trace("plain: " + plain); | trace("timestamp " + _password); | var usernameTokenXML:XML = | <wsse:Security 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 xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utilit..."> | <wsu:Created>{_ds}</wsu:Created> | <wsu:Expires>{getDateString(date)}</wsu:Expires> | </wsu:Timestamp> | <wsse:UsernameToken> | <wsse:Username Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...">{username.text}</wsse:Username> | <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr..." | xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...">{_password}</wsse:Password> | <wsu:Created>{_ds}</wsu:Created> | </wsse:UsernameToken> | </wsse:Security> | | var wsse: Namespace = new Namespace("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext..."); | var wsseSecurity: QName = new QName(wsse.uri, "Security"); | var header: SOAPHeader = new SOAPHeader(wsseSecurity, {"wsse":"Security"}); | header.content = usernameTokenXML; | | return header; | } | | And here is an example of the SOAP message: | <SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'><SOAP-ENV:Header><wsse:Security 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:Created>2009-09-25T13:07:29Z</wsu:Created> | <wsu:Expires>2009-09-25T13:10:29Z</wsu:Expires> | </wsu:Timestamp> | <wsse:UsernameToken> | <wsse:Username Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext...'>kermit</wsse:Username> | <wsse:Password Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-pr...'>lKnNIypKvfb27kzvQynQtS+iNUc=</wsse:Password> | <wsu:Created>2009-09-25T13:07:29Z</wsu:Created> | </wsse:UsernameToken> | </wsse:Security></SOAP-ENV:Header><SOAP-ENV:Body> | <tns:echo xmlns:tns='http://test.com/'> | <arg0>test</arg0> | </tns:echo> | </SOAP-ENV:Body></SOAP-ENV:Envelope> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257096#4257096 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257096

16 years, 7 months

1
0
0 / 0

[JBoss Web Services Users] - Re: avoid lazy-initialization exceptions

by lespoches

I think the solution is to use @XmlAccessorFactory on Entity Bean and override default accessor ! But by default, Jboss do not exploit this annotation when creating JAXBContext and i can't find how to enable this Binding customization. If anyone have an idea, help would be greatly appreciated Jo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257095#4257095 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257095

16 years, 7 months

1
0
0 / 0

[jBPM Users] - Re: Migrating custom workflow to jbpm

by p2auljr

I am using jBPM4. I haven't found anything in the javadoc api that will allow me to place an execution in a specific node. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257094#4257094 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257094

16 years, 7 months

1
0
0 / 0

[EJB 3.0 Users] - Re: EJB Entity Bean works in default configuration, failes u

by gldnrtvr

Ok, I must have had a typo in my original grep because as I expected, there was a hard-coded URL in the jndi.properties file. Thank you jaikiran for encouraging me to revisit the jndi.properties file, where I should have found the problem in the first place. I guess sleep deprevation doesn't mesh well with software engineering. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257093#4257093 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257093

16 years, 7 months

1
0
0 / 0

[Beginner's Corner] - Re: Is JBoss Enterprise App Platform a commerical fork of JB

by PeterJ

Yes. Super. Go to http://www.jboss.com/products/platforms/application/ and download the datasheet. Look at the "Components and Features" section. In a nutshell: EAP 4.2 = AS 4.2.0 + Seam + patches EAP 4.3 = AS 4.2.1 + Seam + JBoss Messaging + patches EAP 5 = AS 5.1.0 + Seam (this is from my understanding, still waiting for my trial copy) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257092#4257092 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257092

16 years, 7 months

1
0
0 / 0

[Beginner's Corner] - Re: JBoss: Windows vs Linux

by PeterJ

Our fairly extensive performance testing using the SpecJAppServer and other benchmarks running in JBoss AS on Windows and Linux has shown that there is no difference - we hit the same performance numbers on both OSes. So which one are you more comfortable with? And how much is cost a factor? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257091#4257091 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257091

16 years, 7 months

1
0
0 / 0

[JBoss Portal Users] - Re: Removing Dashboard Feature

by PeterJ

Try this. In jboss-portal.sar/conf/data/default-object.xml, delete the entire 'deployment' entry that starts with: <deployment> | <if-exists>keep</if-exists> | <context> | <context-name>dashboard</context-name> | <properties> | . . . | </deployment> Disclaimer: I haven't tried this, so no guarantees. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257086#4257086 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257086

16 years, 7 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 September 2009