I have added ECO ASP.NET Auto Form and run a Web project.
The initial autoform shows all the classes and works ok.
But when I click create link near some class it gives the error below.
Some details:
- Model is external ECO package in DLL
- DB is Oracle.
- There're 5 packages with arround of 50 classes.
What a problem can it be?
I'm really confused here...
Thanks.
-----------------------------------------------------------------------------------------------
Value cannot be null. Parameter name: obj
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null. Parameter
name: obj
Source Error:
An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the exception
can be identified using the exception stack trace below.
Stack Trace:
[ArgumentNullException: Value cannot be null.
Parameter name: obj]
Borland.Eco.Services.Impl.ExternalIdServiceImpl.Borland.Eco.Services.IExternalIdService.IdForObject(IObject
obj) +613
Borland.Eco.Web.WebUtils.IdForObject(EcoSpace ecoSpace, IObject obj) +57
Borland.Eco.Web.AutoForm.SetupPage() +465
Borland.Eco.Web.AutoForm.Page_Load(Object sender, EventArgs e) +5
System.Web.UI.Control.OnLoad(EventArgs e) +55
System.Web.UI.Control.LoadRecursive() +27
System.Web.UI.Page.ProcessRequestMain() +750
> Hi guys,
>
> I have added ECO ASP.NET Auto Form and run a Web project.
> The initial autoform shows all the classes and works ok.
>
> But when I click create link near some class it gives the error below.
>
> Some details:
> - Model is external ECO package in DLL
> - DB is Oracle.
> - There're 5 packages with arround of 50 classes.
is it a "wrapped" database? if you have a database with "attribute
mapped" primary key, you will get this behaviour. This is going to be
fixed in next update.
the reason it crashes is that Eco tries to create an object and
immediately save it before it shows the "edit page". Since the
attributes for the primary key has to be assigned before it is saved,
the update-operation fails, and from there, things go down hill...
In the update, Eco will show a page before the object is stored in the
db so that you can fill in the key-fields
--
/Jonas, Borland Eco R&D
Thanks for your reply.
> is it a "wrapped" database? if you have a database with "attribute
> mapped" primary key, you will get this behaviour. This is going to be
> fixed in next update.
No it is not a wrapped DB. It is new Oracel database.
> In the update, Eco will show a page before the object is stored in the
> db so that you can fill in the key-fields
Are there some workarounds for now?
Thanks.
Dmitriy.