SQL Server 2005 Endpoints

Question

Hello,
I am trying to fetch data from SQL Server 2005, bypassing
IIS. SQL 2005 Endpoints require a username and password and don't
support anonymous access. How can I send a username and password
for authentication? This is the Flex 2 Beta 2 code I am using to
call the service:
<mx:WebService id="zoban" wsdl="
http://zoban/Library?WSDL">
<mxperation name="GetBooks">
<mx:request>
<Text>{kaka.text}</Text>
</mx:request>
</mxperation>
Well, this does not work. If I point my browser to the
service I get the username popup - prompt.
Can I squeeze in something like <mx:username> and
<mxassword> in the flex code?
Best!

Answer 1

WELL NEXT WAS UR QUESTION OF using a query string parameter
pART 2 Passing request data into Flex applications
You can pass request data to Flex applications by using a
query string parameter or defining flashVars properties in the HTML
wrapper. When you use query string parameters, Flex converts them
to flashVars variables and passes them to the application.
Inside the Flex application, you access flashVars properties
and query string parameters exactly the same way, but the way that
you pass them to the Flex application is different:
* The flashVars properties: You explicitly define the
flashVars properties in the HTML wrapper that points to the Flex
application.
* Query string parameters: You attach query string parameters
to the URL in the browser's target window and the Flex Enterprise
Services 2.0 converts them to flashVars variables.
Changing either the query string parameter or the flashVars
property does not trigger a recompilation of the Flex application
if you are using the Flex Enterprise server.
To use flashVars or query string parameters inside your MXML
file, you access the Application.application.parameters object. The
parameters property points to a dynamic object that stores each
parameter as a name-value pair. You can access variables on the
parameters object by specifying parameters.variable_name. As with
any variable, you can bind the parameters object's properties to a
display control or modify the value and return it to another
function.
The following example defines the myName and myHometown
variables and binds them to the text of Label controls:
<mx:Application xmlns:mx="
http://www.macromedia.com/2005/mxml"
creationComplete="initVars()">
<mx:Script><![CDATA[
// Declare bindable properties in Application scope.
[Bindable]
private var myName:String;
[Bindable]
private var myHometown:String;
// Assign values to new properties.
private function initVars():void {
myName = Application.application.parameters.myName;
myHometown = Application.application.parameters.myHometown;
]]></mx:Script>
<mx:VBox>
<mx:HBox>
<mx:Label text="Name: "/>
<mx:Label text="{myName}" fontWeight="bold"/>
</mx:HBox>
<mx:HBox>
<mx:Label text="Hometown: "/>
<mx:Label text="{myHometown}" fontWeight="bold"/>
</mx:HBox>
</mx:VBox>
</mx:Application>
When a user requests this application with the myName and
myHometown parameters defined, Flex displays their values in the
Label controls. The following URL passes the name Nick and the
hometown San Francisco to the Flex application:
http://localhost:8100/flex/myApp.swf?myName=Nick&myHometown=San%20Francisco
To view all the flashVars properties, you can iterate over
the parameters object, as the following example shows:
for (var i:String in Application.application.parameters) {
ta1.text += i + ":" + Application.application.parameters +
"\n";
Flex does not recompile the application if the request
variables have changed. As a result, if you dynamically set the
values of the flashVars properties or query string parameters, you
do not force a recompilation.
Query string parameters must be URL encoded. The format of
the string is a set of name-value pairs separated by an ampersand
(&. You can escape special and nonprintable characters with a
percent symbol (%) followed by a two-digit hexadecimal value. You
can represent a single blank space using the plus sign (+).
The encoding for flashVars properties and query string
parameters is the same as the page. Internet Explorer provides
UTF-16-compliant strings on the Windows platform. Netscape sends a
UTF-8-encoded string to Flash Player.
Most browsers support a flashVars String or query string up
to 64 KB (65535 bytes) in length. They can include any number of
name-value pairs.