ADF with Shale

Question

Is anyone using ADF with Shale, I am having the following (short version of) errors:
Error exercising tag : <tag name>
java.lang.IllegalStateException: No AdfRenderingContext
     at oracle.adfinternal.view.faces.renderkit.core.CoreRenderer.encodeEnd(CoreRenderer.java:154)
     at oracle.adf.view.faces.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:624)
     at javax.faces.webapp.UIComponentTag.encodeEnd(UIComponentTag.java:645)
     at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:568)
Where <tag name> is any of: af:document, af:table, af:showOnePanel, etc.
When I remove the shale library files, everything works fine. I was wondering if anyone knows a workaround the problem.

Answer 1

Thanks Shay,
http://www.oracle.com/technology/products/jdev/collateral/papers/11/newfeatures/index.html
Regarding my question 3 "Design time at runtime" - quoting from "JDeveloper 11g new features" at the above URL, under "ADF Task Flow". The third entry from the paragraph's end reads:
'Support for customization of task flows at runtime using "design time at runtime"'.
I was wondering what this is exactly - web-deployable editor to edit the flow definition after deployment?
Re your point 4, product replacement - with the feature set described in the paragraph above, Task Flows is much more than a Web UI controller. With "save for later", transactions, flow abstraction/nesting, BPEL outcalls, conditional logic, method calls etc etc it probably covers 50% of a typical workflow package and 75% of an embeddable workflow library (audit trail/timeouts/persistence nonwithstanding). This made me wonder whether it is part of a bigger, yet-to-be-announced OAS feature. Especially if one also considers the "design-time-at-runtime" sentence listed above.
Now, definition-wise, I guess it' s whether this feature set is considered half-full or half-empty :-)
Thanks again,
Thanassis