[JBoss Seam] - s:link EL bug, seam-2.0.0.BETA1
by msznapka
Hello,
i moved my project to seam-2.0.0.BETA1, because of great new jboss-el
PROBLEM:
i am looping over conversation scoped array and generating links with action with integer parameter:
| <ui:repeat value="#{someArray}" var="item">
| <h:commandLink action="#{util.action(item.id)}" .../>
| </ui:repeat>
|
where util is application scoped object:
| @Name("util")
| @Scope(APPLICATION)
| @Startup
| public class Utils {
| public String action(Integer id) {
| ...
| }
| }
|
which works fine until i change h:commandLink to s:link, because of right onversation management
s:link always call action with parameter 0, h:commandLink calls action with right integer
if this is bug, please repair it, i really like new jboss-el
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071871#4071871
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071871
18Â years, 8Â months
[EJB 3.0] - Invoke remote EJB3 from JVM 1.4 client
by bmaras
I managed to call remote EJB3 from a JVM 1.4 client.
I would be glad to have some feedback on the way I dit it : is it safe? Should I open a JIRA to publish a patch?
I use JBoss 4.0.3SP1 with EJB3 RC6. A JDK 1.5 is needed for the EJB3.
I need to remotely call some of these EJB from a client that runs on JDK 1.4.
It doesn't work natively, because the jboss-ejb3.jar bundled with EJB3 RC6 is compiled with JDK 1.5. It gives errors on major/minor version.
So I used JBossRetro (http://labs.jboss.com/jbossretro/) to convert this jar in jdk 1.4 compatible format.
That gave me a jar that works in my jdk 1.4 client.
I also needed to create a client jar for my EJBs, compiled with a 1.4 target.
I had to include the EJB interfaces in it, but they don't compile by default because of the annotations @Local and/or @Remote, so I needed to remove these annotations when I compile the client jar.
Thus, I can call my EJB 3 Session Stateless Beans. I need on my client :
- the client jar for my EJBs, compiled as explained above
- the generated jboss-ejb3-client14.jar
- jbossretro-rt.jar
- jboss-backport-concurrent.jar
- javassist.jar
I tested that on JBoss 4.0.3SP1+EJB3 RC6, with Session Stateless Beans only.
I have a patch for the current version of ejb3/build.xml. I could not test the generated jar from this script, because I only use JBoss 4.0.3SP1 that doesn't support the latest version of EJB3 jars.
I generated my jboss-ejb3-client14.jar with another ant script, that does this :
- uncompress the file jboss-ejb3.jar bundled with EJB3 RC6
- delete all files that are not included in jboss-ejb3-client.jar (based on the list of current ejb3/build.xml)
- run jbossretro on the classes, using the jboss 4.0.3SP1 libraries on the classpath
- recompress the jar
Should I create a JIRA for that ?
I would be glad to have some feedback on all that.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4071870#4071870
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4071870
18Â years, 8Â months