Hi saasira,
We need some more details.
What version of websphere/seam/ejb3fp etc...?
More info from log? And config?
Did you see the reference doc and were you able to get the jee5 example running
without remote ejbs?
thanks
View the original post :
http://www.jboss.com/index.html?module=bb&o
actually, may have found it. Don't waste your time. I'll report back.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041131#4041131
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041131
_
Anyone get a chance to look at this. I'm really stuck :(
Not sure what I'm doing wrong so that session context is not active.
Thanks,
PVM
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041130#4041130
Reply to the post :
http://www.jboss.com/index.html?modu
Solution for this problem:
I add a function, wich used SessionContext and if faces context will left, seam
use el-*.jar directly. To that extend you have to add el-*.jars as modules in
application.xml:
| el-api.jar
|
|
| el-ri.jar
|
View the original post :
http://www.jboss.co
the libs should normally be in web-inf/lib of your project's WAR which is
contained inside the EAR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991755#3991755
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991755
___
Yes i have it in my Eclipse. I created Projekt with Seam Gen and imported as a
Java standart project, if i push save eclipse copies the projekt automatecally
to JBoss path, but can you say where exactly, where have this libs to stay in
ear ?
View the original post :
http://www.jboss.com/index.
Thanks so much for you quick answer!!!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991744#3991744
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991744
___
jboss-user maili
You need el-api.jat and el-ri.jar in the EAR classpath
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3991743#3991743
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3991743
___
If what you mean is that *Seam* is using /local, well, that is because that is
what is specified in org.jboss.seam.core.init.jndiPattern
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961665#3961665
Reply to the post :
http://www.jboss.com/index.html?module=
This doesn't appear to be related to Seam. From this error it looks like you
have different versions of your classes on your client and server.
You also appear to be mixing RMI, EJB 2.x and EJB 3. I suggest using pure EJB
3 with Seam. Try looking at an EJB 3 tutorial and/or an EJB 3 book (fre
It seems to be bound anyways to "ClassName/remote" even though this is not
explicitly listed. I assume this because if I specify this, I get an error that
differs from the error I get when misspell something in this string.
However, none-the-less I cannot really figure out what's going on, sinc
That was fast! I found the section on interceptors in the Seam reference, but
that section seems to be describing interceptors that happen before a
particular action is executed.
I'm assuming this means that I need to read up on the EJB3 spec some more to
find out about client-side interceptor
OK, so I have implemented client-side interceptors for Seam. All you do is
write a normal Seam interceptor (using @Interceptors as a meta-annotation),
and then annotate the actual interceptor class @Interceptor(type=CLIENT).
That is a good place to handle stuff like remote exceptions.
View the o
"[EMAIL PROTECTED]" wrote : 3. You need to implement your own exception
handling layer for this. Either deal with the exception in client code, or in a
servlet filter or web.xml. Unfortunately JSF (amazingly) does not provide any
good place to handle these kinds of exceptions :-(
H. One th
1. At least in CVS it is conceptually possible to have a remote Seam component.
(I forget whether a nonbuggy implementation made it into 1.0.1.)
However, this feature requires that the implementation class for the remote
bean is in the client classpath, which is not usually the case. (I'm not q
15 matches
Mail list logo
