<font size=2 face="sans-serif">Hello<br>
<br>
Thanks for the link. I had a look but I couldn't find any TCK tests checking
to see if an observer method will catch the new ConversationContext being
created for the "new transient conversation". To check if a new
conversation was activated I created an entirely fresh server and ran the
test application on it, the behaviour was the same, the first url I pinged
on this new server ended with "cid=" and the observer didn't
. Normally I've just been restarting the old server but restarting frequently.
<br>
<br>
I've attached the recreate you requested. it consists of the three classes
attached to my previous email as well as a minimal html page. To run it
load it onto your server and ping </font><a href="http://localhost:9080/ConversationContextTest/index.xhtml"><font size=2 color=blue face="sans-serif">http://localhost:9080/ConversationContextTest/index.xhtml</font></a><font size=2 face="sans-serif">
to see the observer fire, and </font><a href="http://localhost:9080/ConversationContextTest/index.xhtml"><font size=2 color=blue face="sans-serif">http://localhost:9080/ConversationContextTest/index.xhtml</font></a><font size=2 face="sans-serif">?cid=99999
to see the observer fail to fire. <br>
<br>
Best regards<br>
Benjamin</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Matej Novotny <manovotn@redhat.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Benjamin Confino <BENJAMIC@uk.ibm.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">weld-dev@lists.jboss.org,
Takayuki T Ishii <EBB0F3L@jp.ibm.com></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">27/01/2020 11:39</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">[EXTERNAL] Re:
[weld-dev] Question about conversations scope initilization
obeserver</font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Hello,<br>
<br>
I'd start by pointing you to CDI TCK as that's a good starting point to
see what's covered.<br>
For your question, that would be this test - </font></tt><a href="https://github.com/eclipse-ee4j/cdi-tck/blob/master/impl/src/main/java/org/jboss/cdi/tck/tests/context/conversation/ClientConversationContextTest.java#L344-L349"><tt><font size=2>https://github.com/eclipse-ee4j/cdi-tck/blob/master/impl/src/main/java/org/jboss/cdi/tck/tests/context/conversation/ClientConversationContextTest.java#L344-L349</font></tt></a><tt><font size=2>
<br>
And possibly few more in the same test class.<br>
<br>
As for the linked classes - your `ConversationBean` is listening for @Initialized
event. Can you verify that a new conversation was activated for your request
instead of verifying that context was activated?<br>
E.g. check IDs or something along those lines? I suppose that will hold
true and in that case it works just as spec requires it to.<br>
>From the top of my head I don't really know how we activate/deactivate
ConversationContext, I'd need to dig that up, but looking at CDI spec,
it doesn't mandate that it is activated every time again and it could already
be active for given request.<br>
Plus from just the classes you linked, I cannot know if you test this with
no existing conversation or maybe with some long running one before you
try to send a request for non-existing one...and so on.<br>
So if the above doesn't is not enough to answer your question, then we're
going to need a complete reproducer so that we both talk about the same
scenario :)<br>
<br>
Matej<br>
<br>
----- Original Message -----<br>
> From: "Benjamin Confino" <BENJAMIC@uk.ibm.com><br>
> To: weld-dev@lists.jboss.org<br>
> Cc: "Takayuki T Ishii" <EBB0F3L@jp.ibm.com><br>
> Sent: Monday, January 27, 2020 11:42:14 AM<br>
> Subject: [weld-dev] Question about conversations scope initilization
obeserver<br>
> <br>
> Hello<br>
> <br>
> I have a customer who's sent me a sample application, I have attached
the<br>
> source to it below.<br>
> <br>
> When the customer visits index.xhtml they see the following output:<br>
> <br>
> Conversation initialized.<br>
> Conversation begun. </font></tt><a href="cid:1"><tt><font size=2>cid:1</font></tt></a><tt><font size=2>
, timeout:3600000<br>
> Conversation destroyed. </font></tt><a href="cid:1"><tt><font size=2>cid:1</font></tt></a><tt><font size=2><br>
> <br>
> However when they append "?cdi=" or a non-existnant identifier
like<br>
> "?cdi=10000" to the url they do not see "Conversation
initialized."<br>
> <br>
> The CDI spec says that: If the propagated conversation cannot be restored,<br>
> the container must associate the request with a new transient conversation<br>
> and throw an exception of type<br>
> javax.enterprise.context.NonexistentConversationException.<br>
> <br>
> I'm wondering if this should apply here? Or would it only apply if
the cid<br>
> pointed to an existing conversation that could not be restored? And
is there<br>
> anything in the spec that covers this specific situation?<br>
> <br>
> Unless stated otherwise above:<br>
> IBM United Kingdom Limited - Registered in England and Wales with
number<br>
> 741598.<br>
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU<br>
> <br>
> _______________________________________________<br>
> weld-dev mailing list<br>
> weld-dev@lists.jboss.org<br>
> </font></tt><a href="https://lists.jboss.org/mailman/listinfo/weld-dev"><tt><font size=2>https://lists.jboss.org/mailman/listinfo/weld-dev</font></tt></a><tt><font size=2>
<br>
<br>
</font></tt>
<br>
<br><font size=2 face="sans-serif"><br>
Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU<br>
</font>