[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-613) jboss-portal.sar dependencies to PortalDS too strict for resource adapter (.rar) based JCA service

[Xavier Dury (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBPORTAL-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12451022#action_12451022 ] 

Xavier Dury commented on JBPORTAL-613:
--------------------------------------

I experienced the same problem while using JCA-defined datasources with EJB3/JPA... I ended up with a jboss.jca:service=ConnectionFactoryBinding,name=MyDS and the server complained about not having a jboss.jca:service=DataSourceBinding,name=MyDS. It had nothing to do with JBoss-Portal so it is a more global problem than that. I never found a way to make it work! Did you by any chance?

> jboss-portal.sar dependencies to PortalDS too strict for resource adapter (.rar) based JCA service
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBPORTAL-613
>                 URL: https://jira.jboss.org/jira/browse/JBPORTAL-613
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>            Reporter: Tuomas Kiviaho
>            Priority: Minor
>
> It seems that dependecies to 'PortalDS' JCA service are hardcoded against DataSourceBindings thus when using resource adapters you'll be getting
> --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
> ObjectName: jboss.jca:service=DataSourceBinding,name=PortalDS
>   State: NOTYETINSTALLED
>   Depends On Me:
>     portal:service=CMS
>     portal:service=TreeCache,type=persistent
>     portal:service=Hibernate
>     portal:service=Hibernate,type=globalinstance
>     portal:service=Hibernate,type=globalportal
> I don't think JMX pattern "language" supports OR mechanism so that dependencies can be spiced up with *:service=ConnectionFactoryBinding. Then again omitting service attribute completely makes the pattern too ambiquous.
> Temporary fix is of course to use datasource deployment with driver .jar, but I'd prefer using .rar. And besides the services differ only by their prefix so it's quite hard to figure out what's wrong even when JBoss JCA deployment is familiar to you.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira