[JBoss jBPM] - Re: BPEL - receive - invoke
by KVAK_TNT
I think I'll rewrite it here:
| <sequence name="START">
| <receive operation="connectMe" partnerLink="atm" portType="atm:FrontEnd" variable="agilproReq"/>
|
I have implemented a connectMe operation in my agilpro_impl.java file (partner relation) and added the following code (for test purpose):
System.out.println("**** connectMe ****");
|
So I see allways a log message in jBOSS console everytime an operation is performed.
If I start a receive operation like above - this code is not performed. The only way - I now found out - is the following:
sequence name="START">
| <receive operation="connectMe" partnerLink="atm" portType="atm:FrontEnd" variable="agilproReq"/>
| <invoke inputVariable="agilproReq" name="initialConnect" operation="connectMe" partnerLink="agilpro" portType="agi:AgilproIssuer"/>
|
Like above: If I first use a receive on the atm relation and
then an invoke on the partner relation - my code works.
The only thing now: will this cause problems later on?
Or would you say it is "good code"?
Greetings
Claus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976159#3976159
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976159
19 years, 7 months
[JBoss Messaging] - Re: Will future releases be backwards compatible with older
by ovidiu.feodorov＠jboss.com
Oliver,
Dropping insuring compatibility is a decision that we reluctantly took after we evaluated our resources and polled the community (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85729). Given the pace at which the code changes on the head, it is simply not feasible to maintain backward compatibility through all intermediate changes until 1.2.GA. Technically, it can done, the wire format has built-in support for it, but then we would have had to delay the delivery of 1.2, and since there are a lot of people who are waiting for clustering, we decided to temporarily drop the requirement.
The framework for testing backward/forward compatibility exists (take a look at tests/smoke/build.xml) and it was integrated within the release procedure, it is just temporarily disabled now.
We will be back at guaranteeing compatibility starting with 1.2.GA.
We do apologize for any inconvenience this may caused you. If you have a support contract with us, and you already have production clients deployed, we could evaluate what it implies to restore server compatibility in your specific case, as part of a consulting engagement. If you are interested, we can continue this discussion off-line.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976157#3976157
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976157
19 years, 7 months
[EJB 3.0] - optional=true
by monkeyden
I'm trying to define a one-to-one bidirectional relationship in which one row may or may not exist. I thought setting optional=true (on both sides?) would allow for this but I get the following error:
Caused by: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.xxx.entity.UserAlertsProfile#425195]
Here is the code:
@Entity
| @Name("userRecord")
| @Table(name = "RHTCONTACT")
| @Scope(ScopeType.SESSION)
| public class UserRecord implements IUserRecord, java.io.Serializable {
|
| /**
| * Retrieves the ContactKey from the entity
| */
| @Id
| @Length(max = 22)
| @Column(name = "CONTACT_KEY", length = 22, nullable = false)
| public Long getContactKey() {
| return this.contactKey;
| }
|
| /**
| * Sets the ContactKey of the entity
| */
| public void setContactKey(Long contactKey) {
| this.contactKey = contactKey;
| }
|
| /**
| * @return the alertsProfile
| */
| @OneToOne(optional=true, fetch=FetchType.EAGER)
| @JoinColumn(name="USER_KEY", unique=true, nullable=false, updatable=false, insertable=false)
| public UserAlertsProfile getAlertsProfile() {
| return alertsProfile;
| }
|
| /**
| * @param alertsProfile the alertsProfile to set
| */
| public void setAlertsProfile(UserAlertsProfile alertsProfile) {
| this.alertsProfile = alertsProfile;
| }
| ...
| }
|
@Entity
| @Name("alertsprofile")
| @Table(name = "USER_PROFILE_ALERTS")
| public class UserAlertsProfile implements java.io.Serializable {
|
| /**
| * Retrieves the UserKey from the entity
| */
| @Id
| @Length(max = 22)
| @Column(name = "USER_KEY", length = 22, nullable = false)
| public Long getUserKey() {
| return this.userKey;
| }
|
| /**
| * Sets the UserKey of the entity
| */
| public void setUserKey(Long userKey) {
| this.userKey = userKey;
| }
|
| /**
| * @return the userRecord
| */
| @OneToOne(optional=true, mappedBy="accountInfo")
| public UserRecord getUserRecord() {
| return userRecord;
| }
|
| /**
| * @param userRecord the userRecord to set
| */
| public void setUserRecord(UserRecord userRecord) {
| this.userRecord = userRecord;
| }
| }
Thanks for suggestions.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976149#3976149
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976149
19 years, 7 months