@In(required=false) @Out(scope=ScopeType.BUSINESS_PROCESS,required=false) long fileId;
The above makes a task expression fail. If I remove the @In annotation then everything works fine. However I have another method within the same seam component that requires the varbiable at a later stage in the workflow. I would have thought that the required=false parameter would allow for a null variable value. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922475#3922475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922475 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
