Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread EWBDatabaseAdapter.Commit
Fri, Dec 2 2016 1:30 AMPermanent Link

Eivind

All

I have been off EWB coding for about 6 months now, and ran into an unexpected Access Violation in Delphi code that have worked for years prior to this. I'm running my server code in ISAPI dll created by Delphi and plugged into IIS. This have worked smoothly for me until now.

I'm using the TEWBDataSetAdapter.BuildRows() to create the JSON packages sent in return to the EWB app. Actually, I saw there was come changes to the BuilRows() method as well. It now needs a TString, and optional username and password. All good there after I changed that in code. Data is served perfectly to the EWB App.

However, I cannot get the commit to work. In the EWB app, I started using Database.AutoTransactions which is great and the commit fires correctly from the app. In the IIS I can debug the data coming from the EWB app and it contains the JSON package with the commit data.  Previously I have forwarded the JSON commit data to the EWBDatabaseAdapter using the EWBDatabaseAdapter.Commit(PostData) (PostData contains the JSON data correctly). The OnGetDataSetAdapter procedure is already set up and have been working previously to return the correct DataSetAdapter. However, when executing the EWBDatabaseAdapter.Commit(PostData), an Access Violation is immediately raised and the OnGetDataSetAdapter is never called.

Is there something I'm missing out on in the last 6 months? Does this work differently now and should I use it differently?

Just as a side note. Before I started coding again, I updated to Delphi Berlin 10.2. Would this affect this and these Delphi components only work for Berlin 10.1?

Looking forward to some pointers in what I'm doing wrong

Br
Eivind
Fri, Dec 2 2016 1:13 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Eivind,

<< The OnGetDataSetAdapter procedure is already set up and have been working previously to return the correct DataSetAdapter. However, when executing the EWBDatabaseAdapter.Commit(PostData), an Access Violation is immediately raised and the OnGetDataSetAdapter is never called. >>

Would it be possible for you to capture the JSON being sent in the commit using the browser's developer tools (F12) and send it to me (email please) ?  I'll try to feed it into the database adapter here and see what I can find out.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Dec 2 2016 10:17 PMPermanent Link

Eivind

Tim

Thanks for your answer. I have sent you an email already with the JSON commit string. Looking forward hearing from you.

Br
Eivind
Tue, Dec 6 2016 11:50 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Eivind,

Handled via email - it's a bug in 2.05 that will be fixed in 2.06.

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Dec 7 2016 6:27 AMPermanent Link

Emin

Tim,

I have reported exact same bug on Sep 19, 2016 if you remember.

September october november december..

Emin Borbor


This was my mail:

When I run my server application with web builder modules 2.05 build
>> 4. I am getting an exception when I call TEWBDatabaseAdapter.Commit.
>> Application perfectly runs with web builder modules 2.04 build 1
>> (204b1ewbmodulersdelphiwin3210s.exe)
>>
>> Development Env.:
>> Delphi 10 Seattle update 1, windows 10
>>
>> Server model:
>> I am not using Elevate Web Builder web server but using IIS with
>> reverse proxy to my delphi web server.
>> I use two EWB components, TEWBDatabaseAdapter and TEWBDataSetAdapter
>> dropped on a web data module.
>> These to components handle all bridging between EWB client JSON and
>> database services for my project.
>>
>> I am sending you my web data module source with the exception line 170
>> commented.
Wed, Dec 7 2016 2:16 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Emin,

<< I have reported exact same bug on Sep 19, 2016 if you remember. >>

I don't, actually, but I will check to see what my reply was.  If I didn't confirm the issue, then that is why it wasn't fixed yet, at least not with a hot fix.

<< September october november december.. >>

Yes, I'm well aware of the time frame between builds/releases.  I'm working very hard right now to get out 2.06, which will include fixes for all issues during that time frame.

Tim Young
Elevate Software
www.elevatesoft.com
Image