angularjs - JSON from REST service returning under wrong name -


i building angularjs/typescript web app netbeans restful backend. have typescript interface set vendor follows:

interface vendor {     vendorno: number,     name: string,     address1: string,     city: string,     province: string,     postalcode: string,     phone: string,     vendortype: string,     email: string; }

when call rest service pull of vendors javadb pulling json named under different scheme interface, , in order angular directives work, have reference naming scheme of json instead , causing things break:

[{"vendoraddress":"543 sycamore ave","vendorcity":"toronto","vendoremail":"bb@depot.ca","vendorname":"big bills depot","vendorno":1,"vendorphone":"(999) 555-5555","vendorpostalcode":"n1p1n5","vendorprovince":"on","vendortype":"trusted"}, {"vendoraddress":"628 richmond street","vendorcity":"london","vendoremail":"abc@supply.ca","vendorname":"abc supply co.","vendorno":2,"vendorphone":"(519) 123-4567","vendorpostalcode":"n6c1l7","vendorprovince":"on","vendortype":"trusted"}, {"vendoraddress":"123 main boulevard","vendorcity":"burlington","vendoremail":"gs@shack.net","vendorname":"gadget shack","vendorno":3,"vendorphone":"(613) 444-3423","vendorpostalcode":"n3x5s2","vendorprovince":"on","vendortype":"unknown"}]

in order display vendor data in table on partial have use following angular bindings:

<div class="col-lg-1 col-sm-1 col-xs-1 text-left">{{vend.vendorno}}</div> <div class="col-lg-4 col-sm-4 col-xs-4 text-center">{{vend.vendorname}}</div> <div class="col-lg-3 col-sm-3 col-xs-3 text-center">{{vend.vendorcity}}</div> <div class="col-lg-3 col-sm-3 col-xs-3 text-center">{{vend.vendortype}}</div>

is there reason either angularjs or java rest service auto renaming returned json have these property names?

is there reason either angularjs or java rest service auto renaming returned json have these property names

it isn't angular. java rest service.

one option update interface match server returns :

interface vendor {     vendorno: number;     vendorname: string;     // on ... }

Comments

Post a Comment

Popular posts from this blog

html - Outlook 2010 Anchor (url/address/link) -

i'm trying link specific pdf page msoutlook'10 or msword'10, #page=... anchor particularly useful , works fine elsewhere. unfortunately when click [ctr-k] in outlook or winword, links re-formatted assuming unc path. pdf file located on shared drive. using "file:" prefix links open pdf in adobe reader (outside of browser), , "http:" open inside browser. issue seem need open in browser "file:" prefix in order anchor work. know anchors work inside browser. outlook uses windows/explorer default program (based on file extension) seems open in adobe reader neglecting anchor. is aware of solution, link specific page or bookmark of shared-pdf ms outlook and/or winword link? common references: mailermailer.com/...anchor-tags-html-emails campaignmonitor.com/...anchor-links-in-email-newsletters/ stackoverflow.com/...anchor-in-pdf-document
Read more

javascript - Why does running this loop 9 times take 100x longer than running it 8 times? -

consider code: test = function() { } t = new test(); (var = 0; < 8; i++) { result = t instanceof test; } if change number of iterations 8 9 , loop take 100 times longer complete in latest version of firefox (41.0.1). tested on 2 different pcs , magic limit 8. here jsperf test used: http://jsperf.com/instanceof-8-times-vs-9-times does have idea why might happen? seems specific instanceof . not happen if else object, example check property. note: filed bugzilla bug this. jan de mooij mozilla team has posted details in bugzilla thread . here's simplistic interpretation of highly technical answers: in i < 8 case, firefox smart enough hoist result = t instanceof test; statement out of loop (according tests, doesn't seem omit altogether). in i < 9 case, apparently doesn't optimization . why? reason not clear, related fact 9 iterations threshold above function considered "hot" enough run through jit compiler. i < 8 cas...
Read more

Getting gateway time-out Rails app with Nginx + Puma running on Digital Ocean -

following this guide setup app on digital ocean droplet, not working. site not loading , it's throwing: "gateway time-out". the puma server works, since ps aux | grep puma prints: root 15878 0.0 0.4 376832 2168 ? sl 12:50 0:00 puma 2.13.4 (unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock) [20150930164940] root 15881 0.0 0.7 903676 3692 ? sl 12:50 0:06 puma: cluster worker 0: 15878 [20150930164940] root 24654 0.0 0.1 11748 916 pts/2 s+ 18:00 0:00 grep --color=auto puma my nginx config: user root; worker_processes 1; events { worker_connections 1024; } http { upstream puma { server unix:///var/www/myapp/shared/tmp/sockets/myapp-puma.sock; } server { listen 80; server_name myapp.com; root /var/www/myapp/current/public; access_log /var/www/myapp/current/log/access.log; error_log /...
Read more