[JBoss Seam] - Re: JBoss Seam, a great product that doesn't work :(
by lazar.mihai
Wow, thanks a lot for the prompt reply :).
I had RHDS RC1 and eclipse jee with jboss tools.. What I'm doing is this. I'm making a Seam Web Project with JBoss Seam 2.0.0.GA on JBoss AS 4.2.0.GA
The template works fine. When I access Generate Entities from the tool i get a n error saying something about ejb3deployer not beeing initialized.
Because of the errors I tried going back to the command line. The template worked fine.
Anyway.. I'm now doing JBoss AS 4.2.0.GA with JBoss Seam 1.2.1.GA looks like it works now. :-??
Also, what is that about Seam 2.0 being a technology preview ? Could that be the cause of the errors I get with deployment?
I'm pretty sure that when I was writting by hand I left out some configurations.
In conclusion it seems to be working for now. With Jboss Seam 1.2.1
Compared with Stripes, Seam still takes to much out of me, although if the facts on paper are right it will be worth it, at least that I'm hoping for.
Also found http://in.relation.to/Bloggers/Everyone/Tag/Seam, and it provided with some help.
If you know why I get that ejb3deployer error, or the most recent one
ERROR [SeamLoginModule] Error invoking login method
javax.el.PropertyNotFoundException: Target Unreachable, identifier 'authenticator' resolved to null
In the meanwhile I'll be playing with what works, don't think there is much more I can do right now :).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123693#4123693
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123693
18 years, 3 months
[EJB 3.0] - Re: Accessing EJB3s through a firewall
by magnus.ahlander
I'm employing the following configuration of JBossAS 4.2.1 GA to make stateless EJB3s accessible both through firewall/router and from LAN.
1. Port forwarding
Configure port forwarding of the following ports from router to JBossAS:host:
Naming - 1098, 1099
EJB3 - 3873
HTTP - 8080
2. EJB3 proxies
Modify jboss.service.xml in ejb3.deployer\META-INF:
...
| <mbean code="org.jboss.remoting.transport.Connector"
| name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
| <depends>jboss.aop:service=AspectDeployer</depends>
| <attribute name="Configuration">
| <config>
| <invoker transport="socket">
| <attribute name="serverBindAddress">${jboss.bind.address}</attribute>
| <attribute name="serverBindPort">3873</attribute>
| <attribute name="clientConnectAddress"><external_host_name></attribute>
| <attribute name="clientConnectPort">3873</attribute>
| </invoker>
| <handlers>
| <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
| </handlers>
| </config>
| </attribute>
| </mbean>
| ...
|
3. RMI stubs
Add the following system property when starting JBossAS:
-Djava.rmi.server.hostname=<external_host_name>
4. DNS
Make sure DNS entries are resolved as follows:
<external_host_name> -> <external_host_ip> (outside of the router - WAN)
<external_host_name> -> <internal_host_ip> (inside of the router - LAN)
Regards,
Magnus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123692#4123692
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123692
18 years, 3 months