[EJB 3.0] - Re: Persistence Unit NOTYETINSTALLED
by straiver
I have troubles with Persistence unit too:
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
| State: NOTYETINSTALLED
| Depends On Me:
| jboss.ejb:service=EJBTimerService,persistencePolicy=database
| jboss.mq:service=StateManager
| jboss.mq:service=PersistenceManager
|
| ObjectName: persistence.units:jar=ru.srpu.jtest.dao.jar,unitName=jtests
| State: FAILED
| Reason: org.hibernate.MappingException: Unable to find column with logical name: id in org.hibernate.mapping.Table(Test) and its related supertables and secondary tables
| I Depend On:
| jboss.jca:service=ManagedConnectionFactory,name=MySqlDS
| Depends On Me:
| jboss.j2ee:jar=ru.srpu.jtest.dao.jar,name=UserBean,service=EJB3
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985308#3985308
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985308
19Â years, 7Â months
[JBoss Portal] - using opensso security product with jboss portal 2.4
by moj_sham
Hi,
I am new to JBOSS Portal and need your help to resolve my problem. We are using Jboss Portal 2.4 for portal and using opensso product for the security layer (for user authentication and authorization).
portal url with /auth/* is protected by opensso product. Now when ever user clicks on the protected url i.e url that contains "/auth" string opensso redirects the user to a loginscreen for authentication and after sucessful authentication it redirects to the user requested page. During this redirection opensso sends the userid that was authenticated as the request header attribute.
Now my question here is,
In the request header I have a userid that is already authenticated by the opensso security product but for the portal the user is still unauthenticated. How can I authenticate the user into the portal without asking the portal user to submit the portal login screen.
Can any one provide solution or hooks available in jboss portal to resolve this problem.
Thanks
Manoj
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985306#3985306
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985306
19Â years, 7Â months
[Security & JAAS/JBoss] - using opensso security product with jboss portal 2.4
by moj_sham
Hi,
I am new to JBOSS Portal and need your help to resolve my problem. We are using Jboss Portal 2.4 for portal and using opensso product for the security layer (for user authentication and authorization).
portal url with /auth/* is protected by opensso product. Now when ever user clicks on the protected url i.e url that contains "/auth" string opensso redirects the user to a loginscreen for authentication and after sucessful authentication it redirects to the user requested page. During this redirection opensso sends the userid that was authenticated as the request header attribute.
Now my question here is,
In the request header I have a userid that is already authenticated by the opensso security product but for the portal the user is still unauthenticated. How can I authenticate the user into the portal without asking the portal user to submit the portal login screen.
Can any one provide solution or hooks available in jboss portal to resolve this problem.
Thanks
Manoj
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985305#3985305
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985305
19Â years, 7Â months
[JBoss Messaging] - Re: Connecting to two JBoss messaging servers causes interfe
by davidrh
I have made the changes suggested and patched them into my 1.0.1.GA deployment. The classes that I needed to change were:
| org.jboss.jms.client.container.ConsumerAspect
| org.jboss.jms.client.remoting.CallbackManager
| org.jboss.jms.server.endpoint.ClientDelivery
| org.jboss.jms.server.endpoint.ServerConsumerEndpoint
|
|
| I have re-tested with my original test case and it seems to work. If I put the code back in to close the server1 connection on an exception, then server 2 logs the warning:
|
| | 15:47:08,828 WARN [SimpleConnectionManager] A problem has been detected with the connection to remote client 4h39k3q-6gtwyu-eugdls00-1-eugdlu2o-9. It is possible the client has exited without closing its connection(s) or there is a network problem. All connection resources corresponding to that client process will now be removed.
| |
| and my server2 producer is unable to send a message, so there is still some sort of interaction occurring. Attempting to close the connection on an error does seem to be the reasonable thing to do, so that the messaging client has a chance to clean up any loose ends.
|
| If you don't close the session and/or connection, the client application keeps logging the message:
|
| | 2006-11-13 15:51:00,515 WARN org.jboss.remoting.LeasePinger - Error sending lease ping to server for client invoker (session id 4h39k3q-524pp9-euge7ah3-1-euge7biu-5.
| |
| every 30 seconds or so.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985304#3985304
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985304
19Â years, 7Â months
[JBoss Seam] - Re: Gotchas (so far)
by gavin.kingï¼ jboss.com
1. I think this is normal in facelets.
2. Why on earth not? I'm sure you are mistaken.
3. Not correct, just put the button outside the <f:form/> element that has the validation. (This is standard JSF, nothing to do with Seam.)
4. Yes, this is normal, and is the default in recent (1.1.0.BETA) releases of Seam. That's why the getting started guide says use JBoss 4.0.4 with Seam 1.0.1.
5. We absolutely do not recommend the use of MyFaces tomahawk stuff with Seam, we have found this stuff to be extremely fragile, buggy and generally low quality. We will have examples of Trinidad as soon as there is an actual Trinidad release available (there is already an example on the Wiki).
6. The problem here is that the default SFSB timeout is longer than the default session timeout in JBoss. Bill promises me he will fix this.
By the way, if you are not going into production in the next month, I strongly recommend 1.1.0.BETA2 over of 1.0.1.GA. A *lot* of good work has been done in the past few months.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985303#3985303
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985303
19Â years, 7Â months