[Installation, Configuration & Deployment] - JBoss 5.0 beta1 + client side libraries are incomplete
by vbndeveloper
Hi,
I'm trying to get a Swing application to connect to an annotated stateless EJB that running under JBoss 5.0 beta1. Since there is some confusion as to which Jars I need to run I've been using jbossall-client.jar on the client. It seems to be imcomplete though as I had to add jboss-logging-spi.jar and I am running into an exception while trying to log on. I have not found the jar containing org.jboss.security.plugins.JBossSecurityContext yet.
The exception I'm running into is below.
Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/security/plugins/JBossSecurityContext
at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:77)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:102)
at $Proxy0.openSession(Unknown Source)
at com.vanbelle.hydra.client.ejb.Test.main(Test.java:49)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017952#4017952
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017952
19Â years, 2Â months
[JBoss Seam] - Re: Question about conversations
by quilleashm
Case 2 is usally handled by conversations timing out. So if the user navigates away and doesn't come back (using the Back button) then the conversation will eventually die and clean up it's state.
If the user navigates back to the page (not using the back button) then they will not pick up the active conversation by default. Instead it will start a new conversation assuming there is a @Begin or equivalent somewhere.
Maybe an example...
Say the user is on a search screen, they search for something and decide to edit an item.
The view changes to the edit view and a conversation (1) is started. The user makes a few changes in the browser form but decides not to finish the edit and uses the back button to return to the search screen.
User clicks the same item again from the search screen, view changes to the edit view and a new conversation (2) is started. Note the user will not see the changes they made in conversation (1) as the changes were not saved.
So now there are two active conversations both on the edit view of the same item. Perfectly valid, if a little tricky to get your head round.
User makes some edits to the item in conversation (2) and hits update. View redirects to the search.
User wanders off for a cup of tea.
Conversation (1) times out and silently dies (get cleaned up on the next request).
So although there were two conversations editing the same item they didn't get in each others way and the discarded conversation died without any nasty side-effects or cleanup code.
The only possibility of something messing up here is if the user managed to get back to conversation (1) (using the conversation switcher) and save some changes, in which case I would be trusting my database layer to throw a versioning/stale data error on the second update.
Note that this is EXACTLY the same as if two users on separate machines/server sessions decided to try and edit the same item at the same time so this isn't a Seam issue, just the price you pay for optimistic locking.
HTH.
Mike.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017948#4017948
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017948
19Â years, 2Â months
[JBoss Seam] - Re: Question about conversations
by hstang
"dustismo" wrote : I am little confused about conversations.
|
| I have a number of instances where I wanted to start a conversation and end it either when
| 1. the task is completed
| 2. the user navigates away from the page(s) that comprise the conversation.
|
| But reading the manual it looks like I can leave the conversation open in 2 which will get picked back up when the user navigates back to that page. Is this true? If so, how does the coversationId get picked up again? If not, I haven't found a good way to end a conversation when a user navigates away from a page (which would seem like a necessary feature).
|
|
The conversationId get picked back up when rendering a page with <s:link> or some other propagation mechanism supported by Seam.
Could you not use <s:link propagation="end".../> for out-going links on the page?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017943#4017943
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4017943
19Â years, 2Â months