[ 
http://issues.apache.org/jira/browse/OFBIZ-391?page=comments#action_12449134 ] 
            
Jacques Le Roux commented on OFBIZ-391:
---------------------------------------

OK,

I can't create an account to book a room on Open travel, I get :

The Following Errors Occurred:

    * ERROR: Could not complete the Create Contact Mechanism 
[file:/opt/ofbiz/test/ofbiz/applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml#createContactMech]
 process [problem creating the newValue value: The current transaction is 
marked for rollback, not beginning a new transaction and aborting current 
operation; the rollbackOnly was caused by: Failure in getNextSeqId operation 
for seqName [ContactMech]: java.lang.IllegalArgumentException: Could not get 
next sequenced ID for sequence name: ContactMech. Rolling back 
transactionjava.lang.IllegalArgumentException: Could not get next sequenced ID 
for sequence name: ContactMech (Could not get next sequenced ID for sequence 
name: ContactMech)] calling service createContactMech in createPostalAddress 
calling service createPostalAddress in createPartyPostalAddress

However I see that there are no rooms booked after the 29 oct 2006. One 
question a this stage, how are you using TechDataCalendarExcDay ?

> Bug in room booking
> -------------------
>
>                 Key: OFBIZ-391
>                 URL: http://issues.apache.org/jira/browse/OFBIZ-391
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Bug
>          Components: ecommerce
>            Reporter: Bilgin Ibryam
>         Attachments: OrderServices.patch, Screenshot-1.png
>
>
> Hi, 
> If we make a room booking in ecommerce application, including the last Sunday 
> of October ( 29 October ), the bookings that are after that date are not 
> visualized in the fixed asset calendar. Because of Daylight Saving Time, we 
> lost one hour and even the reservation is marked in the Database ( with -1 
> hour ) we cannot see the reservations on the fixed asset calendar.
> Here is a little patch that solves the problem.
> Regards,
> Bilgin 

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

        

Reply via email to