Pipeline namespaces only valid after a set?

Question

If I try to access a pipeline session attribute before called a set method
on it, I'm getting the following type of error. Can someone confirm this is
either a bug, or that there is a requirement to have "set" something into
the pipeline session before the namespace is considered "valid"?
[java] <Nov 21, 2002 6:44:20 PM CST> <Info> <EJB> <010051> <EJB
Exception during invocation from home: com.bea.p13n.appflow.pipeline.in
ternal.PipelineExecutorImpl_x8bn7v_HomeImpl@167892 threw exception:
Exception[com.bea.p13n.appflow.exception.InvalidArgumentException: Attem
pting to work with an attribute in the PipelineSession and the supplied
namespace [my_account] is invalid.]
[java]
Exception[com.bea.p13n.appflow.exception.InvalidArgumentException:
Attempting to work with an attribute in the PipelineSession a
nd the supplied namespace [my_account] is invalid.]
[java] at
com.bea.p13n.appflow.common.internal.PipelineSessionImpl.containsSessionScop
edAttribute(PipelineSessionImpl.java:450)
[java] at
com.clinsights.presentation.portal.pipelines.principals.LoginSummaryCreation
PC.process(LoginSummaryCreationPC.java:60)
[java] at
com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl.executePipeline(
PipelineExecutorImpl.java:299)
[java] at
com.bea.p13n.appflow.pipeline.internal.PipelineExecutorImpl_x8bn7v_EOImpl.ex
ecutePipeline(PipelineExecutorImpl_x8bn7v_EOI
mpl.java:46)
[java] at
com.bea.p13n.appflow.webflow.internal.PipelineProcessor.process(PipelineProc
essor.java:157)
[java] at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.processTarget(Webf
lowExecutorImpl.java:1233)
[java] at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.gotoNode(WebflowEx
ecutorImpl.java:746)
[java] at
com.bea.p13n.appflow.webflow.internal.WebflowExecutorImpl.gotoNextNode(Webfl
owExecutorImpl.java:684)
Also - I found I needed to add the weflow_servlet.jar to the pipeline.jar's
META-INF classpath before I was able to get past some "class not found
issues"... this is not really mentioned in the documentation (To the best of
my knowledge). I have seen mention in the newsgroups of having to add your
own code's classpath to this METAINF however.
Another issue.... its unclear from the documentation whether or not I can
use the i18n:getMessage tag from within my own portlets.... I mean I'm sure
you can add the tags into the code, but where are the property file(s) which
are then accessed. I see in the framework subdirectories that virtually
every jsp file has its own resource bundle.... does this behavious not
translate into the portlet jsp files.
Thanks for any replies,
Markus

Answer 1

Hello Kamlesh,
Indeed <webflow:getProperty was fixed by specifing the namespace... I was
assuming that by "default" it would use the namespace associated with the
portlet.
However there is more to the original problem, since in the
PipelineComponent itself, I was getting errors with the
pipelineSession.containsxxxx() method and I also was not able to retrieve an
attribute right after having set it (using the same namespace, and in the
same piece of code... ie 2 lines of code - set followed by get).
It's working now though - I'm not sure what the difference is. I changed the
get/set methods to use the ones in the PipelineComponentSupport class. It
appears to me as though these function differently then the get/set methods
in the pipelineSession class.
Also I think maybe having included the servlet_webflow.jar in the pipeline
ejb's manifest classpath is causing some unwanted sideeffects.... even
though doing so stopped the class not found issues I was having.
thanks again,
Markus
"Kamlesh Nanda" <[email protected]> wrote in message
news:[email protected]...
>
Hi Markus,
it seems to me that the problem with your scenario is that you aresetting the
values in a different namespace in Pipeline component and trying toretrieve if
from a different namespace.
By default if you use "<webflow:getProperty" without a namespace it willuse
the current namespace which might be different from the one in which youhave
set the property. Most probably (again its my guess) that you are usingthe getDefaultNamespace()
method in your pipeline component and then setting the property in thedefault
name space.
To debug this at a page level the easiest thing you can do is to include<Portal_HOME>\applications\portal\stockportal\framework\error\configuratione
rror.jsp
at the bottom of you page. [Note: before doing this copy the
<Portal_HOME>\applications\portal\stockportal\framework\error> folder under your web application folder
This page will give you complete details of what and where all theproperties
exist in terms of namespace.
Cheers
Kam
"Markus Blumrich" <[email protected]> wrote:
Finally I'm having some success with pipelines....
Can someone with source confirm my hunch that calling the
get/setSessionAttribute method in PipelineComponentSupport has additional
functionality than being just a shortcut to PipelineSession's methods?
Otherwise I'm at a loss to explain why it is working.
Also... as a side note I had to specify the namespace in the portlet
<webflow:getProperty namespace=" attribute before the JSP was able to
get
at the pipeline session attribute.
Markus