[IronJacamar] - trying to understand JBoss ra.xml required-config-property for inbound
by jleinawe
jleinawe [https://community.jboss.org/people/jleinawe] created the discussion
"trying to understand JBoss ra.xml required-config-property for inbound"
To view the discussion, visit: https://community.jboss.org/message/725194#725194
--------------------------------------------------------------
My resource-adapter has 3 required-config-property elements
from ra.xml:
| | <inbound-resourceadapter> |
| | <messageadapter> |
| | <messagelistener> |
| | <messagelistener-type> |
| | javax.jms.MessageListener |
| | </messagelistener-type> |
| | <activationspec> |
| | <activationspec-class> |
| | weblogic.jms.ra.ActivationSpecImpl |
| | </activationspec-class> |
| | <required-config-property> |
| | <config-property-name>*ConnectionFactory*</config-property-name> |
| | </required-config-property> |
| | <required-config-property> |
| | <config-property-name>*Destination*</config-property-name> |
| | </required-config-property> |
| | <required-config-property> |
| | <config-property-name>*DestinationType*</config-property-name> |
| | </required-config-property> |
My ra implemetation supports optional config-properties, such as MessageSelector that I specify in the MDB source
@MessageDriven(
name="MyMdb",
activationConfig = {
@ActivationConfigProperty(propertyName = "*ConnectionFactory*",
propertyValue = "java:jboss/wljmsra/cf"),
@ActivationConfigProperty(propertyName = "*DestinationType*",
propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "*Destination*",
propertyValue = "java:jboss/wljmsra/queue2"),
@ActivationConfigProperty(propertyName = "*MessageSelector*",
propertyValue = "Recipient = 'MDB'"),
})
When I deploy, I get this warning and my MDB's MessageSelector is ignored.
WARN [org.jboss.ejb3] (MSC service thread 1-1) JBAS014105: ActivationConfigProperty MessageSelector will be ignored since it is not allowed by resource adapter: wljmsra
The only way I can work around this is to add MessageSelector to my ra.xml as a required-config-property.
I can also add other required-config-property elements and not assign values to them in my MDB's @ActivationConfigProperty. This seems to defeat the purpose of having to identify "required"-config-property elements for inbound in ra.xml.
while the app-server is not required to enforce "required-config-property", the app-server and deployment tools are allowed to do so.
JCA Section 12.4.2.2: "The resource adapter may also provide in its deployment descriptor, using the required-config-property element, an optional list of configuration property names required for each activation specification. This information may be used during deployment to ensure that the required configuration properties are specified."
So while adding all of the RA's optional activation spec properties as "required-config-property"s in ra.xml might be a work-around for vanilla JBoss, it would make the RA non-JCA-compliant and may cause failures on other app-servers or when using various deployment tools. Even on JBoss it may cause problems if the user is using a deployment tool that enforces "required-config-property".
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/725194#725194]
Start a new discussion in IronJacamar at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
[JBoss Tools] - org.hibernate.annotations.Type and jboss tools
by John Franey
John Franey [https://community.jboss.org/people/jjfraney] created the discussion
"org.hibernate.annotations.Type and jboss tools"
To view the discussion, visit: https://community.jboss.org/message/725094#725094
--------------------------------------------------------------
With jboss tools in eclipse I get the following false errors when I annotate using hibernate's TypeDef and Type annotations.
Code:
@TypeDef(name="encryptedPassword", typeClass=org.jasypt.hibernate.type.EncryptedStringType.class,
parameters = {
@Parameter(name="password", value="blah blah blah.")
})
Error:
| Description | Resource | Path | Location | Type |
| Type class "org.jasypt.hibernate.type.EncryptedStringType" should implement one of interfaces "org.hibernate.type.Type","org.hibernate.usertype.UserType", "org.hibernate.usertype.CompositeUserType", "org.hibernate.usertype.UserCollectionType". | zzzz.java | /xxxx/src/main/java/... | line 91 | JPA Problem |
Class Hierarchy: jasypt's EncryptedStringType extends jasypt's AbstractEncryptedAsStringType which implements hibernate's UserType.
Code:
@Type(type="org.joda.time.contrib.hibernate.PersistentDateTime")
private DateTime startTime;
| Description | Resource | Path | Location | Type |
| Type class "org.joda.time.contrib.hibernate.PersistentDateTime" should implement one of interfaces "org.hibernate.type.Type","org.hibernate.usertype.UserType", "org.hibernate.usertype.CompositeUserType", "org.hibernate.usertype.UserCollectionType". | yyyy.java | /xxxxx/src/main/java/xxx | line 172 | JPA Problem |
Class Hierarchy: joda time's PersistentDateTime implements hibernate's EnhancedUserType which extends UserType.
What am I doing wrong?
jboss by redhat, Hibernate tools: 3.4.0v20120307-2104-H60-Beta1
jboss by redhat, jboss as tools: 2.3.0.v20120308-1629-H87-Beta1
Indigo Service Release 2 Build id: 20120216-1857
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/725094#725094]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
[jBPM] - jBPM5.2 + JBossESB4.10 + JBoss 5.1.0GA
by Alan Ooi
Alan Ooi [https://community.jboss.org/people/ayooi] created the discussion
"jBPM5.2 + JBossESB4.10 + JBoss 5.1.0GA"
To view the discussion, visit: https://community.jboss.org/message/725193#725193
--------------------------------------------------------------
Hi,
I am trying to get the aforementioned jboss products integrated and working with each other. I have been able to get as far as installing JBoss ESB into JBoss 5.1.0GA and using the packaged jbpm that comes with that for creating workflows and orchestrating services. The main features I'm looking to use are assigning tasks to people and utilizing services on the ESB.
I need to be able to somehow do everything I currently am doing but with jBPM 5.2 instead, but there seems to be a lack of documentation on the matter of using jBPM5.2 for service orchestration. I also have no idea how to install jBPM5.2 without having clashes between the packaged jBPM3.2.7 and the new jBPM5.2.
Am I just not looking in the correct places or does jBPM 5.2 not immediately handle service orchestration out of the box?
Also, how do I go about integrating jBPM 5.2 and JBoss ESB 4.10?
All I am trying to do currently is follow the ant build script instructions to install necessary components into JBoss from jBPM and JBossESB. This has unfortunately, not worked out as I believe a lot of the configuration files conflict with each other.
Any help would be greatly appreciated!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/725193#725193]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
[jBPM] - Re: Errors in named queries: TasksAssignedAsPotential Owner
by ramkijbpm
ramkijbpm [https://community.jboss.org/people/ramkijbpm] created the discussion
"Re: Errors in named queries: TasksAssignedAsPotential Owner"
To view the discussion, visit: https://community.jboss.org/message/725175#725175
--------------------------------------------------------------
this is completely wrong. It cannot work if you remove the TaskOrm.xml having all those namedQueries. if you remove you will get the following exception,
Caused By:
javax.persistence.PersistenceException: [PersistenceUnit: org.jbpm.persistence.jpa] Unable to find XML mapping file in classpath: META-INF/Taskorm.xml
I get this very same exception about namedQueries in Weblogic. Is there any good solution to this below problem? It really is very painful!!! Is JBPM compatible to weblogic server?
Caused By:
org.hibernate.HibernateException: Errors in named queries: TasksAssignedAsPotentialOwner, UnescalatedDeadlines, TasksAssignedAsTaskStakeholder, TasksAssignedAsRecipient, TasksAssignedAsPotentialOwnerByGroup, TasksAssignedAsExcludedOwner, TasksAssignedAsBusinessAdministrator, SubTasksAssignedAsPotentialOwner, ProcessInstancesWaitingForEvent, TaskByWorkItemId, TasksOwned, TasksAssignedAsPotentialOwnerWithGroups, GetSubTasksByParentTaskId, TasksAssignedAsTaskInitiator
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/725175#725175]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years
