-
1. Re: GWT - Seam integration: Problem with persistence
dhartford Apr 16, 2008 7:52 PM (in response to milicsrdjan)Seam/GWT gotcha's:
Make sure any DTO's implement com.google.gwt.user.client.rpc.IsSerializable.
http://jira.jboss.org/jira/browse/JBSEAM-2305 -- sample project here.
Security integration challenges:
http://jira.jboss.org/jira/browse/JBSEAM-2325 -
2. Re: GWT - Seam integration: Problem with persistence
milicsrdjan Apr 19, 2008 7:42 PM (in response to milicsrdjan)Hi Darren,
Thanks for your time to reply to me :) Hey did you try the exaple jbseam-2305, cause i have a problem about that example, server show to me some exception like:
NoClassDefFoundError: com.domain.app.QueryGwtLocal
i know that the exception like this will show when i dont have QueryGwtLocal.class in my jar archive which was deployed to server, but i have.
I tried also other examples where gwt modules is connected directly at stateless session bean, but in my jboss they examples dont work. Could you tell me which jboss version you use for JBSEAM-2305 mey be i dont have regular version.My examples (which can run to server) contain gwt modules which is connected at component with @Name(
org.hanson.gwt.client.MyService
) but the component is not a session bean (like stateless). In that component i'm connecting to session bean over jndi tree and initialContext lookup method.
JBSEAM-2305 is a great exaple cause i dont need other component cause i can to connect to session bean directly, but that example dont work on my server.Thanks for all
-
3. Re: GWT - Seam integration: Problem with persistence
dhartford Apr 24, 2008 10:32 PM (in response to milicsrdjan)Hi Srdjan,
yes, that example was and is working in my environment. The intent was to simply show the IsSerializable requirement for the POJO/DTO/Entity beans. This was original dev/tested on Jboss 4.0.5, but I'm now working on 4.2 so should be pretty solid regardless of platform.There is a problem with Seam 2.1.0-SNAPSHOT/GWT 1.5M2 related to just POJO/DTO/Entity beans transfer, but if you use normal datatypes everything else is working fine (non-annotated, using orm.xml entity beans). I haven't posted it yet as I'm limited in time and not exactly sure of the culprit yet.
Sorry I couldn't be much more help with the NoClassDefFound, that seems to be the only gotcha to start directly working with the Seam-Remoting to GWT piece (I did the JNDI lookup approach in the past as well, you aren't alone).
-
4. Re: GWT - Seam integration: Problem with persistence
milicsrdjan Jul 25, 2008 1:53 PM (in response to milicsrdjan)Hi Darren,
i didnt solve my problem with project GWT - SEAM direct calling a session bean. My project sometime work somtime dont. Could you package the seam-security example to .ear and send to me at milicsrdjan@yahoo.com mail as an attachment. Can you tell me what i need to put in my classpath. The example i cant package with maven2 because the depended .jar file which the project need into .pom xml file dont exist on maven repository.
Thanks for all,
Srdjan