very nice Wesley, down to the second. I think that's as precise a response as I've ever received. lol
The example in the video is pretty simple but it doesn't deploy correctly. Here is the error I get on startup:
Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
java.lang.RuntimeException: error while reading /WEB-INF/components.xml
at sun.reflect.GeneratedMethodAccessor138.invoke(Unknown Source)
Caused by: java.lang.RuntimeException: Error loading element PortalIdentity with component name null and component class null
Can anyone shed some light on it?
In version 1.0.0.CR2 The PortalIdentity component is external to the core api/impl, so make sure you are building your project with the -Psso switch in "mvn install". Also I would recommend using the 2.0.0.CR1 version of the bridge instead of 1.0.x - because PortalIdentity is internal to the later 2.0 versions and you don't need to add it as a dependency of the project..
I would also check your components.xml, there are occasions when the archetype does not parse the maven expression language properly on the windows platform. Make sure everything looks good in that file.
Thanks again Wesley. I've been able to get everything working correctly within my code but transaction committal fails after the request. Seam doesn't know anything about the persistence context the portal API is using so when it tries to commit it fails with:
org.jboss.util.NestedSQLException: Could not enlist in transaction on entering meta-aware object!
Caused by: org.hibernate.exception.GenericJDBCException: Cannot open connection
Here is the bit of code that works, until the response:
UserModule userMod = (UserModule) new InitialContext().lookup("java:portal/UserModule");
user = userMod.findUserByUserName(username);
Any idea of how to get around this?