Sure, it has to do with wildcards in pages.xml, but the feature is different.
Anyways, I went ahead and created a JIRA issue here:
http://jira.jboss.org/jira/browse/JBSEAM-2608
If the Seam team feels its a dup, they can mark it, but IMO it is unrelated.
I'll try to create a patch and post it
Hmm... seems like a completely different issue to me. I am not referring to
navigation-rules but to page configuration.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4127975#4127975
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&m
Is there any interest in being able to specify a natural conversation for a
wildcard view-id? When a natural conversation spans a number of pages you
currently have to explicitly state the named conversation for each view-id. It
would be nice to simply specify the natural conversation for a wi
"EricJava" wrote : However, Seam POJO components are stateful and have a
conversational scope by default.
Yes, the book is wrong here. This is one of quite a few revisions for the
Second Edition. A preview is coming soon. Stay tuned!
View the original post :
http://www.jboss.com/index.html
"wachtda" wrote : Peter, that means that it should possible to make a
PhaseListener as in JSF?
Yes, this is quite possible, there is just no guarantee on ordering so you
should be aware of that.
With the observer, why not base your execution on the phases you are interested
in?
@Observer("org.
I would recommend instead writing a Seam component that observes the phase
events that Seam raises (i.e. org.jboss.seam.beforePhase,
org.jboss.seam.afterPhase). This is very simple to do and provides you
bijection as well.
View the original post :
http://www.jboss.com/index.html?module=bb&
Yes, the approach nickarls is describing works quite well.
I implemented something similar by wrapping the Seam Identity component and
included the authenticate method in the wrapper. Your wrapping login() method
can then delegate the login call and then return any navigation String you want
b
JIRA issue raised:
http://jira.jboss.com/jira/browse/JBSEAM-2512
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121684#4121684
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121684
_
"MSchmidke" wrote : And since I write many beans which rely on
flushmode=MANUAL, I like to have a common base class which sets this for all of
them.
Maybe instead of a common base class, a way to globally configure the flushmode
setting. Say, a way to configure begins to use flushmode=MANUAL b
Yes, since the action is annotated with @Begin(join=true). If join=true was
not there you would get an exception.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121655#4121655
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=rep
"[EMAIL PROTECTED]" wrote : Is this how it is suppose to be?
| 1. First page render, cid=1
Yes. This first rendering starts a temporary conversation which is cid=1.
Once the page is rendered that temporary conversation is destroyed.
"[EMAIL PROTECTED]" wrote : 2. Post back to @Begin(join=tr
"[EMAIL PROTECTED]" wrote : The last two buttons, executes the action but the
conversation Id is incremented.
This is because each request initializes a temporary conversation if a
long-running conversation is not resumed. This means that your first page
request resulted in a temporary conver
"yanlong11" wrote : code and packaging is almost identical to seam samples
Please post the structure of your archive with more details of its contents.
Also what version of Seam are you using?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121646#4121646
Re
Have you referenced jboss-seam.jar from your application.xml?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4121644#4121644
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4121644
_
I use pages.xml which, IMO, puts the logic where it belongs as generally
conversations are scoped to a section of the application. As page flow is
defined in the pages.xml file, it makes sense to demarcate the boundaries of
the conversation there.
"MSchmidke" wrote : 2. Beginning a conversatio
"[EMAIL PROTECTED]" wrote : ... perhaps we need a new feature to support some
kind of global session tracking.
Sounds like a cool feature to me. Relates to an event requested in the
comments of:
http://jira.jboss.com/jira/browse/JBSEAM-2257
"org.jboss.seam.destroyedSession". Maybe raise a JI
The ServletContexts.instance().getRequest() currently returns null during a JSF
request. I would think this should be returning the ExternalContext for a JSF
request if the request is a Servlet request (the type of the ExternalContext is
not guaranteed since could be in a portal environment).
U
No, the suggestion I posted is not referring to conversation handling, I'm
simply offering an option if the original poster wants to use PAGE context
(which is what the original post referred to).
The only difference in an s:link between pointing to a view-id and an action is
that an action get
I believe scoping to the PAGE would make sense in your case. Outject to the
PAGE *after* the redirect is performed. One way to do this is using @Factory
on your retrieveEmails() and retrievePhones() and changing your s:link to refer
to the view directly. Take a look at the documentation on Pa
"gus888" wrote : I follow Seam wiki pagination sample: manage bean is stateless
bean, outject a event or page scope page, but I don't know why I didn't get
results back to page. Only after I used conversation outjection, I can got
results displayed on page. However, when I try to click a link on
"gus888" wrote : Question 1 : I tried different outjection scopes: EVENT, PAGE
and CONVERSATION, and only the CONVERSATION scope works (outjected data were
displayed on web). When I used EVENT and PAGE scopes, no data were displayed on
web page. I don't know why?
What is the rest of the scenari
"seamdev" wrote : Messages added to current instance of
javax.faces.FacesContext don't show up on next page.
You should add messages to the Seam FacesMessages component as it is scoped to
the conversation which is carried across redirects...
Then again, I believe you are going to have issues he
"tresspicher" wrote : Let's say somewhere in a JSF form we have the EL
expression:
|
| Code:
|
| #{aValue}
You have to outject aValue to access it this way. (i.e. @Out must be placed on
the attribute).
"tresspicher" wrote : How do I know which class submitting the form will affect?
I
A JIRA issue has been raised:
http://jira.jboss.com/jira/browse/JBSEAM-2442
Included the conversationId along with the event so that you actually know what
conversation it was that timed out ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116178#4116178
R
I have the need for event notification when a background conversation-timeout
occurs. It would be nice to simply provide an event
org.jboss.seam.timeoutConversation (or something along these lines). It is a
very simple patch to the Manager component. Is there anyone else interested in
this f
A JIRA issue has been raised:
http://jira.jboss.com/jira/browse/JBSEAM-2432
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115761#4115761
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115761
__
I have recently run into a requirement where it would be nice to have
descriptions applied to wildcard view-ids. For example, if I have the
following:
...
|
| Section 1
| ...
|
| ...
Section 1 would be the description for all pages in /section/* unless specified
otherwise in a
Thanks Pete, I will keep an eye on CVS ;)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114469#4114469
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114469
___
jboss-user ma
I would definitely second this request. I will have to implement this in the
not so distant future. Pete, if you blog with a tutorial on what you've done I
would be much obliged :) I'm assuming you are planning to use JBoss Cache
under the covers? Thanks.
View the original post :
http://ww
This is a very common JSF problem. required=true must be specified because JSF
will not kick off any validation for empty fields. This means that you are
limited to the REQUIRED message unless you do your own custom handling. The
approach I've used in the past can be found at:
http://www.ora
>From my understanding it has always worked this way. Here is a JIRA issue
>that requests documentation of the subject and references some earlier
>postings (all the way back to 1.0.1GA):
http://jira.jboss.com/jira/browse/JBSEAM-1886
I wrote a blog posting last night that describes the convers
No, in this case that would be the foreground conversation which means that it
would only timeout if the session timed out. Now, if the user was to navigate
elsewhere and a different conversation was started, the previous conversation
would then become a background conversation. In that case,
Sorry, should have previewed. When I say the foreground conversation never
times out, I mean that it is tied to the session timeout not the configured
conversation-timeout.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112385#4112385
Reply to the post :
h
When you say you abandon the conversation what do you mean? Do you start a new
conversation and begin interacting with it? The reason I ask is because the
foreground conversation never times out. Background conversations will timeout
according to your configured conversation-timeout. Backgro
anonymous wrote : I would like to create, if possible of course, an interface
as a component. And use this to control the tasks of my business process.
Depending on the implementation of such interface that is deployed, actions
would behave differently.
It is not possible to directly define an
You could use the event model provided by Seam. In the updateuser bean simply
raise an event:
...
| public void updateUser() {
|...
|Events.instance().raiseEvent("userUpdated", user);
| }
| ...
Listen for that event in a method in your getusers component:
...
| @Observer("u
Does your interceptor work with other Seam components that are not annotated
with @Startup? Please post your annotation and interceptor code.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108938#4108938
Reply to the post :
http://www.jboss.com/index.html?m
You can retrieve the method name by calling getMethod() on the
InvocationContext. The method name can be used for pattern matching. Pattern
and Matcher provided by the java.util.regex library will do the trick. This
library is provided with your Java distribution. There are a variety of
ava
"b.reeve" wrote : 1. Is there a way to intercept just the methods and not the
class.
Seam does not support method level interceptors, but you can always place the
interceptor at the class level and use a method-level annotation to define the
method(s) that should be intercepted. I provide an ex
Are you redisplaying the same page after beginning a conversation? If so, see
the following:
http://jira.jboss.com/jira/browse/JBSEAM-1997
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106530#4106530
Reply to the post :
http://www.jboss.com/index.html?mod
Maybe it was snipped from the code but I do not see the RetentionPolicy. Try
the following:
@Target(ElementType.TYPE)
| @Retention(RetentionPolicy.RUNTIME)
| @Interceptors(LoggingInterceptor.class)
| public @interface Logging {}
View the original post :
http://www.jboss.com/index.html?mo
Alright, just being curious, I went ahead and implemented a solution :) The
following blog post describes how it can be done:
http://solutionsfit.com/blog/2007/11/16/session-expired-messages-using-seam-security/
Hope it helps.
View the original post :
http://www.jboss.com/index.html?module=bb
anonymous wrote : The best option I can think of is putting a page in between
that simply displays something like "You have successfully logged out" and then
perform a meta redirect to the login page after a few seconds.
On second look, this should be further specified, sorry. The redirect is g
Hmm... yes, I suppose that would be the case if you redirected directly to the
login page after logout... I have not had to cover that case.
The best option I can think of is putting a page in between that simply
displays something like "You have successfully logged out" and then perform a
met
A JIRA issue has been raised:
http://jira.jboss.com/jira/browse/JBSEAM-2257
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4105285#4105285
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4105285
__
"xshuang" wrote : Then I got another warning saying facesMessages cannot be
null. I checked the forum and one user says facesMessages is not available at
the RESTORE_VIEW phase.
Yes, you can maintain a list of custom messages in an appropriately scoped
component. Observe the event as you are
You have to make some assumptions here, but you can basically notify the user
when the server session has ended with the following in a PhaseListener:
@Observer("org.jboss.seam.beforePhase")
| public void beforePhase(PhaseEvent event)
| {
| if(event.getPhaseId() == PhaseId.RESTORE_VIEW)
Should have specified previously, but for clarity the disinjection only applies
to @In attributes.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104311#4104311
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104311
___
>From my understanding (and maybe a Seam team member can confirm this) all
>bijected attributes are disinjected (set to null) after method invocation. So
>any bijected attributes will not be included in the passivation of the session
>bean.
For any non-bijected attributes, you could either us
"[EMAIL PROTECTED]" wrote : 2) Not sure why i would need a long running
conversation (unless i am completely missing something). The scope is
relatively small...the page is displayed, the validation fails on the page. It
seems to me that the validation failure should return the page as a managed
You have to understand the semantics of @Begin here. The @Begin annotation
does not start a long-running conversation until the method execution
completes. In your case the nested conversation will always begin as your
return type is void, but if you were to have a String return type (for
nav
Depends on what you mean by loading once. If you mean loading once for the
entire application (which I have used in several instances) the following will
work:
@Factory(value="myListBox", scope=ScopeType.APPLICATION)
| public Map getMyListBox()
| {
| // the following log will only
If you include your stacktrace and the snippet of the page where you use the
variable, it will be easier to identify the issue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4102647#4102647
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=pos
Thanks for the feedback guys.
"Delphi's Ghost" wrote : FYI, I already have a JIRA issue requesting a SMPC per
nested conversation.
Thanks for the information Andy. I had submitted an issue as well once the
article was completed so I've marked it as duplicate:
http://jira.jboss.org/jira/brows
Nested conversations have spurred quite a bit of discussion on the forums. The
following article uses an example to discuss the purpose of nested
conversations and why they are useful:
http://developer.redhatmagazine.com/2007/10/31/continuing-the-conversation-understanding-seam-nested-conversat
"jayzaw" wrote : a) for using reflection, I have to be able to reference the
class' name. Unfortunately, "this" - within an aspect's advice means a
reference to the aspect or the advice. But not the class in which the operation
currently executes.
This is more of an AspectJ question, but yes,
anonymous wrote : 1. How do these conversations end if the user does not come
back to generate a click that invokes the method with @End annotation?
Conversations will timeout after a configurable time period. Any conversation
that is not the foreground conversation (the current conversation w
I've had those days myself :) Congrats on CR3!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098939#4098939
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098939
___
jboss-u
The following should help:
http://jira.jboss.org/jira/browse/JBSEAM-1930
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098913#4098913
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098913
_
Thanks Pete, I'm changing my vote :) I like the approach of JBSEAM-2071 better
since this gives you a choice on logging. There are certain situations where I
would like to handle the exception, but still log.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=40
Yes, please vote for:
http://jira.jboss.org/jira/browse/JBSEAM-1021
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098001#4098001
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098001
__
Posted a few days ago:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=121416
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096679#4096679
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096679
___
Review the documentation regarding SMPC:
http://docs.jboss.com/seam/2.0.0.CR2/reference/en/html/persistence.html
or you could perform a fetch join when retrieving an entity to retrieve
associated entities.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=409659
The following post discusses this:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=119611
Knowing this, you may have to consider a slightly different approach to ensure
that the instance is created after nesting. Do you have to send the parameters
through pages.xml? Could you simply
should read "event org.jboss.seam.postCreate."
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096181#4096181
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096181
___
jb
"valbosoft" wrote : the parent of my Home, EntityHome, apparently already
defines the @Create annotation, I get a duplicate error when I use that for my
own method.
Ok, then you could observe the event org.jboss.seam.postCreate. where is the
name of your component to determine creation time.
"amashtakov" wrote : I'm using 1.2.1GA
Yes, 1.2.1.GA uses clr (conversation-long-running-parameter="clr").
There are essentially 2 scenarios:
- GET - conversation attributes passed in query string (the situation you are
referring to)
- POST - conversation attributes posted with the form not in
Which version of Seam are you using? conversation-is-long-running-parameter is
not included in latest (Seam 2.0.0.CR2) due to the addition of
conversation-required.
The key to understanding conversations is the conversationId sent with the
request. The conversationId is maintained along with
Is Seam instantiating your Home instance? If so, I would recommend looking at
the timing of when Home is instantiated. You could do this by adding a method
annotated with @Create and printing out a message. Home must be inserted into
the conversation context AFTER the nested conversation is s
This does not throw an exception due to the behavior of an s:link. An s:link
initiates a GET request which will only capture parameters passed in the query
string (nothing is posted). If you look at the URL generated by your s:link
you will see something like the following:
.../page2.seam?con
Pete, not a problem. The following JIRA issue has been re-opened:
http://jira.jboss.org/jira/browse/JBSEAM-1887
I re-uploaded the example as the initial attachment did not exactly mimic my
usage scenario (although it did demonstrate the issue). Simply use the latest
mp3search.zip to replicate
A JIRA issue has been raised at:
http://jira.jboss.com/jira/browse/JBSEAM-2101
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4094909#4094909
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4094909
___
Done. Please see:
http://jira.jboss.com/jira/browse/JBSEAM-2048
Thanks for the information Pete :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092023#4092023
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092023
_
Please see: http://jira.jboss.com/jira/browse/JBSEAM-1899
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092016#4092016
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092016
>From testing, s:conversationPropagation works embedded in an h:commandLink for
>JSPs, just as f:param works so the docs should definitely be updated.
The hidden form field is how I would expect it to work for an h:commandButton,
but unfortunately just as specified in the bug report it does not
"[EMAIL PROTECTED]" wrote : JSP users can instead directly use ""
Yes Stephen, that will work. Embedding the f:param inside an
or similar component will have the same effect for JSP users. I agree that the
documentation could use improvement there as I've seen a few other posts
recently abou
When you say,
"omilian3" wrote : ... Both of these 'begin' methods are called, so at this
point I expect I'll have a long running conversation...
I am assuming you are saying that the methods are called on different actions,
not from the same action, correct? You shouldn't be calling more than
Actually, on second look that would only work if you were using h:commandLink
(h:commandButton does not support f:param). But you could always place an @End
on your action #{personHome.update} if you are not using Facelets.
View the original post :
http://www.jboss.com/index.html?module=bb&op=
Are you using Facelets? If not the following will work:
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091500#4091500
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091500
___
No it doesn't actually. You have:
public void getAgencyIncidentTypes( Agency selectedAgency )
|{
| this.agencyIncidentTypes = selectedAgency.getAgencyIncidentTypes();
|}
|
which is not the same as #{notificationManager.agencyIncidentTypes}. This
requires an actual getter
By the way, to demonstrate responsiveness to documentation issues based on your
conversationList difficulties the other day:
http://jira.jboss.com/jira/browse/JBSEAM-1999
Resolved in a matter of days. Thanks Seam team!
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
There is a new release of the Yuan/Heute book coming out (the examples in the
current release are a little out of date for the latest release of Seam), but
likely not until early next year some time. I will be posting an article soon
that may help understanding of the semantics of conversations
This is certainly a valid approach IMO and one that I have used for years.
EasyMock and JMock are great frameworks that make this easy to do and you can
always write stubs (which it sounds like you were already considering). I
always strive to make my components testable outside a container as
LOL, apparently I'm having an off day... after looking at my code I am doing
this in several places. I guess I need another cup of coffee :-)
In addition, after looking back, I misread this portion of your post
smithbstl...
"smithbstl" wrote : I have a page where I have a number of these typ
Sorry, with Seam 1.2.1 the method is part of the API so I'm at a loss here.
Maybe someone else could chime in with any insight.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090397#4090397
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=po
"stephen.friedrich" wrote : If you reference a seam component in EL in the
component instance will _always_ be created if it was null.
That's interesting. Is that documented or have you simply experimented and
discovered this? It certainly doesn't work that way for @In.
View the original pos
It looks like you may have conflicting versions of jars (or at least expected
versions). The method Namespace.entrySet no longer exists in Seam 2.0.0.CR1.
What version of Seam are you using?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090382#4090382
Rep
Sorry, the factory method in the above snippet should read,
...
| @Factory(value="person")
| public void loadPerson() {
| if (pid != null) {
| person = (Person) em.find(Person.class, pid);
| } else {
| person = new Person ();
| }
| }
| ...
No value sh
"djfjboss" wrote : I had also assumed that the setPid method would be invoked
via the edit link and thereby set person to the appropriate entity via the id,
but this method isn't even called for me. The fact that the RequestParameter
annotation is commented out is a little disconcerting.
The p
In the scenario you describe, the only time an entity is going to be
automatically created is if it is a named Seam component and it has the
annotation @AutoCreate. Is this how your entity is annotated?
...
| @Entity
| @Name("someEntity")
| @AutoCreate
| public class SomeEntity {
| ..
Please post the page where you are attempting to display the conversationList.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089850#4089850
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089850
"trickyvail" wrote : I agree that a short sentence describing this requirement
added to the documentation at 6.7.3 would be helpful to people using the
conversationList or switcher.
JIRA issue raised:
http://jira.jboss.com/jira/browse/JBSEAM-1999
View the original post :
http://www.jboss.com
JIRA issue created for conversationList issue:
http://jira.jboss.org/jira/browse/JBSEAM-1997
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089817#4089817
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089817
_
"djfjboss" wrote : Actually, there appears to be a little twist - it only works
if I leave this kludge in the @Begin annotated method:
|
| Conversation c = Conversation.instance().begin();
|
| I put this in while stumbling around in the dark.
|
| The @End method seems to work fine b
No, you would not want to do something like that. I think looking at an
example might help...
Take a look at the seam-booking example that ships with Seam. Review
main.xhtml and book.xhtml as well as the actions they use to see how
conversations are started and ended. Then look at the templa
Not a problem, glad it worked out. I would say that this probably indicates
that the documentation could be improved based on your issue and the link that
trickyvail provided. The documentation simply states the following:
anonymous wrote : org.jboss.seam.core.conversationList
|
| Man
You can, you simply have to specify not to propagate the long-running
conversation as I said before. You will remain in the same long-running
conversation across requests unless you specify propagation=none (there are
other ways as well, but this is the general approach). So if you remain in a
This is correct behavior since if you are in a long-running conversation, you
can only join that conversation or nest another conversation. Nesting may be a
good option if you want to have the potential for multiple conversations within
the parent conversation.
If nesting is not appropriate, y
Alright, it will be much easier to discuss once you post the code. I will keep
an eye out for your post.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089530#4089530
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089
Please post your code. When a conversation is nested, contextual variables in
the parent conversation are read-only. This means that if you do something
like:
| @In(value="myList")
| @Out(value="myList")
| private List myList;
| ...
|
| @Begin
| public void beginParentConversat
1 - 100 of 166 matches
Mail list logo
