Ideally when working with breeze in an angular application you would not have to remember to call $apply when using async operations in breeze (eg calls to executeQuery).

I have created an angular module that monkey patches the EntityManager prototype so that the executeQuery (etc) returns a $q library promise and also calls $apply on the $rootScope. This angular module internally uses similar code to that posted here: http://www.breezejs.com/documentation/toqjs

However I've hit on a snag: code internal to breeze registers errorCallbacks using the 'fail' method on the promise object eg promise.then(callback).fail(errCallback)

The 'fail' method is not part of the CommonJS promise/A+ spec (https://github.com/promises-aplus/promises-spec), and as such is not included in the angularjs promise api.

The consequence is that the angularjs promise that the patched EntityManager.prototype returns does not have the fail method and so an exception is thrown.

Internally there are only 3 places in breeze that uses this 'fail' method to register an error callback so it seems like it would be very easy to change this code to support the CommonJS A+ spec ie: promise.then(callback, errCallback).

Thanks
Christian Crowhurst

It's cool Breeze might eventually let you use OData to load up some EF stuff, modify it and save it, but right now it's definitely not ready for prime time. The homepage should really have some kind of warning there about it. The Track Changes is particularly misleading if Save isn't possible yet.

In my use case I can't even load Breeze - I have an EF code first class with a key named Id, and then another that inherits from it using Table-per-Type (so it uses Id as a key - but its own in its own table). The Metadata string passed to Breeze for this schema causes Breeze to fail as soon as I call new Manager.

Breeze mentions extensions to the OData query syntax when used with the WebAPI controllers. However, I would like to use the STANDARD syntax and not allow these extensions, without having to revert to the OData provider (which doesn't support saves currently). I have some existing code to validate OData queries for security purposes, and this code has to be aware of the full syntax tree, and makes assumptions based on the standard spec on how the query is fullfilled by the OData Provider.

These assumptions are broken by Breeze's extensions and shortcuts to the OData query language. The extensions are also a moving target, which is untenable for security-related validation code.

I suggest a configuration option for both the client and server side, whereby the client-side code submits queries using only the standard syntax, and where the server side WebAPI provider code only serves query results based on the standard syntax and handling according to the official spec.

Note: I am, in this instance, limiting this suggestion to queries only. I am fine with the non-standard batch changeset request format via a json bundle sent to the SaveChanges action.

Hello,

We would like to enter into a partnership to sell your Software, Themes, Graphics and Plugins via our marketplace Webilicity.com. Majority of the web developers, programmers, designers and vendors, keep themselves busy with their one or several clients or use one platform only to sell their themes, designs, software and do not comprehend that they are not getting the complete result of their potential.

Webilicity is a Software Hub where we sell all kinds of software, such as Computer Programs, Web Themes, Plugins, Apps, Graphics, Motion Effects, Slides, 3D Models, Photos, Icons, SaaS and Robotics.
1. We are always reaching out to new consumers. This will bring exposure and most likely sales for your products.
2. Developers and Vendors revenue share begins with minimum of 75% which means you will be paid 75% for each copy sold on our marketplace.
3. You can list your products on Webilicity as well as on other websites simultaneously. We do not force you to be exclusive with us.
4. You will have an access to all reports for sales and balance within your Webilicity Portal.
5. You will be in charge of the Technical Support and Product Updates for your listed products in Webilicity Marketplaces.
6. You the developer or vendor will choose your software’s license
7. You the developer or vendor will set the price of your software on Webilicity Marketplaces. We do not force you to lower or increase your price for your items.

1. Upon sales of your listed products on Webilicity Marketplaces, you will be paid every two weeks via PayPal, MoneyBookers or AlertPay.




2. If you do not have time to create an account and upload your products to our marketplace, then with your written permission, we can help you by creating your account on Webilicity.com, upload your products, logo, and banner, do your Meta Tags and write your item description free of charge.

I look forward to hear from you regarding this business offer.

Thank you very much,

Ozy Oz
CEO / Founder | Webilicity.com
Email: oz@webilicity.com
Skype: webilicity

So in the method to parse the OData Metadata I am running into 35 entities in our EDMX that are considered bad navigation properties.

I have modified the code to output the bad navigation properties to the screen. Most of them are ChangeSet objects or a few custom types.

REFACTOR: Commented out the throw and use my logger...

        if (badNavProps.length > 0) {

            badNavProps.forEach(function (badNav) {

                badNav.forEach(function(item) {

                    window.app.logger.info(item.toJSON().associationName + " :: " + item.toJSON().entityTypeName + " :: " + item.toJSON().name);

                });

            });


            //throw new Error("Bad nav properties");

        }

RESULTS:

3: fkAddressChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

4: fkAppointmentChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

5: fkBlackoutPeriodChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

6: fkBusinessUnitChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

7: fkBusinessUnitDeviceConfigurationChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

8: fkBusinessUnitDeviceConfigurationCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

9: fkBusinessUnitDeviceConfigurationCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

10: fkBusinessUnitDeviceConfigurationOpenWayConfigurationFileChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

11: fkBusinessUnitDeviceConfigurationOpenWayConfigurationFileFileContentKey :: FileContent:#Itron.Fdm.Data.Entities :: FileContent

12: fkBusinessUnitDeviceConfigurationOpenWayConfigurationFileCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

13: fkBusinessUnitDeviceConfigurationOpenWayConfigurationFileCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

14: fkBusinessUnitDeviceConfigurationOpenWayFirmwareFileChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

15: fkBusinessUnitDeviceConfigurationOpenWayPasswordChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

16: fkBusinessUnitDeviceConfigurationOpenWayPasswordCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

17: fkBusinessUnitDeviceConfigurationOpenWayPasswordCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

18: fkBusinessUnitDispatchViolationTypeAssignmentChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

19: fkBusinessUnitMobileWorkOrderColumnChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

20: fkBusinessUnitMobileWorkOrderColumnCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

21: fkBusinessUnitMobileWorkOrderColumnCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

22: fkBusinessUnitNetworkSecurityKeyChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

23: fkBusinessUnitNetworkSecurityKeyCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

24: fkBusinessUnitNetworkSecurityKeyCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

25: fkBusinessUnitPressureCompensationChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

26: fkBusinessUnitPressureCompensationCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

27: fkBusinessUnitPressureCompensationCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

28: fkBusinessUnitReasonCodeChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

29: fkBusinessUnitUtilityIdChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

30: fkBusinessUnitUtilityIdCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

31: fkBusinessUnitUtilityIdCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

32: fkBusinessUnitWakeupToneChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

33: fkBusinessUnitWakeupToneCultureInfoChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

34: fkBusinessUnitWakeupToneCultureInfoCultureKey :: Culture:#Itron.Fdm.Data.Entities :: Culture

35: fkCarrierFrequencyChangeSetKey :: ChangeSet:#Itron.Fdm.Data.Entities :: ChangeSet

36: fkExportFileContentKey :: FileContent:#Itron.Fdm.Data.Entities :: FileContent

37: UserAccountWorkType :: WorkType:#Itron.Fdm.Data.Entities :: WorkTypes

I am not sure what can be done to handle these types in the method to create the OData metadata.

Thought I better share it with the Breeze team. Hope it is useful.