Home > database >  Which can be told about the great god, pb webservice how to return to the c # with the dataset
Which can be told about the great god, pb webservice how to return to the c # with the dataset

Time:09-19

CodePudding user response:

With dw savaas () save as XML, HTTP and returns the file in ws

CodePudding user response:

could you speak more specifically

CodePudding user response:

Also, can only be returned json or XML, really can not be returned to the dataset directly???

CodePudding user response:

reference kkxingjin reply: 3/f
and can only be returned json or XML, really can not be returned to the dataset directly???


Yes, the dataset is associated with the database, can't return, you can put the data saved to a list or using Json and Xml

Direct return to the dataset is possible

CodePudding user response:

Saveas () of the XML file will be generated in the below you ws a temporary directory, you can be as long as the specified file name,
C # is to support XML directly into the dataset,

CodePudding user response:

Really not line, I tried N times, is that there is no save, whether in saveas () or fileopen filewrite can't ah, for advice,,,,,,,,,

CodePudding user response:

Method is for me to do, and ws function returns a resultset directly, ws will automatically convert, I don't know c # recognize not recognize, but I know other development language recognition, you can have a try!

CodePudding user response:

This is pb12 development of ws some matters needing attention, the original poster check may be out of the question, is certainly can export XML,

System environment: winxp sp2 + oracle10g + iis5.1

1. Check whether the machine iis is normal, if the iis can not run or the default website times permissions error, check the "local users and groups" in the three related built-in account whether to enable guests (start the iis and asp.net, the Internet),

2. Ws pb12.0 development, must install framework3.5 sp1 and framework sdk2.0, for the sake of simplicity, installed directly vs2008 component with the words (including tool), then play vs2008 sp1 patches, Microsoft's official website the patches need to use a new version of the iso tools to read properly,

3. Due to the.net stricter syntax and signed and unsigned numerical variables can't be the same type of assignment or comparison operations such as each other, for example: int and uint; This problem may lead to a release pb collapse directly!

4. Unsigned value type cannot be used for decreasing cycle, for example: the for uint=100 to 1 step 1; Release will usually give a compiler warnings, but sometimes it can lead to abnormal shutdown in pb!

5. Global function can't use this pronoun, usable GetApplication () instead,

6. C/s application invokes the ws, need to.. \ share \ original concept of pbsoapclient120 PBD (Java standard) or pbwsclient120. PBD (.net) file into the target repository list; They correspond EasySOAP and the.net engine,

7. Use the.net target, the client application must take pbwsclient120. PBX imported into their own group; If import error, can export from pb own ws routines related to three objects for *. The sr * file, then import the own PBL,

8. If the call ws CreateInstance () a runtime error, may be due to the old version of pb in the system32 directory down there with pb Shared directory older versions of the same name DLL, delete or use the new version of the DLL cover can (such as libeay32. DLL),

9. Release the ws detailed log file can be found under this engineering pb2cstempout directory,

10. FileOpen () must be in flow patterns, so FileWriteEx () must also use a blob type,

11. () is yet to be further research cannot be directly read and write the iis virtual directory file, must add it to the iis virtual directory; At the same time to ensure that the file directory and upper directory asp.net have the corresponding access; Virtual directory path available MapVirtualPath (), but can't use the real path to access the virtual directory file, nor the relative path to access the application of the upper directory and file (only accessible/app_root/file/session/__webservice__/c of the session in the temporary directory and file),

12. Ws function called release to the outside world does not allow overloading (this indeed was a very bad),

13. The application object that you can't declare instance variables, global variables are only effective for the current session. The script for the application object will not perform; Call function will not perform in the post way,

14. The template type must be used when creating an object is consistent with statement, not the demotion structure; For example, inherited from the transaction of the custom object n_tran_base, declared as n_tran_base itran_obj, instantiation is can be written as itran_obj=create transaction (assignment, comparison operations in the same way),

15. Need to set up the database driven directory access asp.net (restart), such as c: \ oracle \ product \ 10.1.0 \ client_1,

16. In order to use the sybase datawindow ps printer, need to add asp.net in the security Settings of the printer, Internet guests, network service, start the iis four accounts to allow printing (printing for the first time must be set, then you can delete), can ensure PrintDatawindow (), Print (), SaveAs () these functions can generate PDF files (but db ole controls content can't display),

17. Can through the inet and internetresult two objects, get/app_root/print/session/__webservice__ print file list in the directory, and analysis the right after the print file name; In the same way, also can use this method to obtain the content of the PDF file,

18. () is yet to be further research the Run () function has failed, alternative API, such as the CreateProcess () to start the exe file from the server, but is limited by the iis permissions control, can only see the process in task manager, and can not Run normally, even on the surface of the unbounded exe),

19. (it remains to be further research), according to a sybase newsgroups ole object in the.net applications cannot use, this is not the limitation of pb, but Microsoft's own problems, so the db ole controls also failed, if you still want to be used on the client side, but when retrieving data window containing the db ole to c/s program execution, and then back to the ws,

20. About interprocess communications, DDE pipeline can be set up only, but cannot execute links; Send () function is failure, it is only through the API SendMessage () sends a message to the server process (ws no window handle, can't receive messages), should use WM_COPYDATA transfer data through Shared memory (intercept the message in the other. Number=74), but received the server process is wrong data; Since only the message itself, rather than use pbm_custom01 (1024) is more simple,

21. If the database driver cannot use iis connection pool, it must be in ws, after the completion of execution by the code being disconnected; But because the destructor events will not executed immediately when exit, so must be disconnected before each interface function returns; Moreover, in order to prevent the function of forget to disconnect or abnormal exit, destructor events still need to write the disconnect; ,

22. The isNull () function has failed, judgment, to switch to other methods such as len ()=0,

23. The release to the iis when don't stop, otherwise may cause the damage of iis,
  • Related