Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsXMLXMLFeature request consume SQL 2005 Server endpointsFeature request consume SQL 2005 Server endpoints
Previous
 
Next
New Post
7/9/2007 6:45 PM
 

If it doesn't do it already, I think it would be nifty to have the XML module be able to connect to endpoints and be able to do what endpoints do for web services. :)

If it does it already, configuration of the XML module know-how would be handy.

 

Thanks.

 
New Post
7/10/2007 1:04 AM
 

Can you access the endpoint with a web browser? Even from your DotNetNuke Server? If so, use that url. I did not work with end-points before, maybe I should.

I am currently working on databases as source for the XML module, but this will worked out using direct connections.

 
New Post
7/10/2007 1:52 PM
 

Hi Stefan,

What can be accessed via the web browser is the wsdl gizmo that spits out all sorts of XML. It spits out what methods are exposed so that when doing a SOAP/HTTP request, dunno how this works because so far any docs or examples have been lacking in information that I can figure out (but somebody seems to have figured it out since nobody is changing the documents on MS's site).

Being able to access endpoints might be a handy feature to add. In a previous posting someplace I asked why the XML module didn't really appreciate .cfm's, so I had to run over to my freebsd system and create a .php file to generate XML and that's when I found the items about SOAP/HTTP and MSSQL endoints, and I'm like groovy! Not so groovy because a few bits are missing to link the whole thing together and have one of those Eureka! moments.  Well the link is missing for me that is.

What I've done so far is create a .cfm that runs to the database and does the deed then presents the XML, in IE it works fine to see the XML, but when asking DNN to access the url http://10.10.2.20/jobs2xml.cfm no such luck.

Next I went to an apache and php area and created jobs2xml.php and again the XML was just fine, and DNN liked that. Life was good.

Then came.... Endpoints (see http://technet.microsoft.com/en-us/library/ms181591.aspx) and was like, sweet something for the XML module to also have access to. Not so sweet, exmaples seem to be lacking. :(

So there it is. Dunno if endpoints are one of those technologies that SQL server will keep, or why it's there but hey, why not. :|

 
New Post
7/11/2007 5:19 PM
 

Hello Stefan,

Been futzing around with Endpoints a bit more have had some success.

After creating a module with the Starter Kit I added the following code to module load event:

 

 

'SoapBubbles stuff!

Dim ds As System.Data.DataSet'Dim resultXML As System.Xml.XmlElement

Dim apple As New Object

Dim myCredentials As New System.Net.NetworkCredential("myAccount", "myPassword")

Dim foo As New refSoapBubbles.EmploymentListings 

'refSoapBubbles is created when I went in to Website then Web Reference it then walked me through the creation process of the end connection to the SOAP/HTTP gizmo. The information gets stored in a directory called App_WebRerferences. Since the Wizard mucks up the process one of the files needs to be editted by hand. More on that later perhaps.

foo.Credentials = myCredentials.GetCredential("myIPaddress", myPort, "")

apple = foo.TopEmploymentListings

ds = apple(0)

'Depending on if there is a FOR clause at the select statement within the stored procedure or function the item may either be a DataSet or XMLelement sort of thing.

xmlHere.Text = ds.GetXml

xmlHere.Text is a text box so I can stuff the XML data in to that just to see what's coming out.

My connundrum is how do I get the SoapBubbles (that's what I call the module) module to make a consumable XML document for the XML module to use? I just need to get the ViewSoapBubbles.ascx to be the result of ds.GetXML, nothing more, nothing less and Eureka, XML consumable for the XML module.

Of course the other option is to go in to the XML module itself and add all the needed functionality to do the above directly in to the XML module itself, or at least a hard coded reference of the needed settings for now and a checkbox added to Settings that says to use wsdl, but I'm unsure where I would need to stick the code I just suggested within the XML module source. The following would sort of need to be added at a later time.

Add Endpoint option to location of XML file in Settings.
 When selected
  display option of where wsdl is located.
  display authentication options (Username and password)
  display dropdown of exposed webmethods (this is found by accessing the wsdl location and parsing out the XML)
   display various parameters so they can be opted if needed (dunno parameter and parameter types and requirements can be determined automaticly)

 

 

 

 

 

 

 

 

 
New Post
7/12/2007 4:37 AM
 
Douglas,
We have a serious problem using SOAP as a source for the xml module. If you connect to a SOAP web service in your VS, it seems very easy to connect: as all you need is entering the URL of the web service. The magic behind is that VS reads the WSDL description and start to generate code which gets hidden to you (You can switch on show all files to view them).
DNN or the XML module is not able doing that on the fly. I never worked with sql server 2005 endpoints, but I am afraid that every endpoint will have a different WSDL contract behind describing the functions you are offering at this place.
So t is easy for you writing a module that access the data, but it I horrible for a module doing at on its own. The only generic solution I am aware of was written by Christian Weyer (http://www.thinktecture.com/resourcearchive/tools-and-software/dynwslib). As this dynamic proxy is generating managed code on the fly it will not run under medium trust, which is a common setup for a lot of hosters.
As I wrote before, I am currently extending xml module to support more datasources than file and URL. It will be a provider based architecture, so you will be able to extend the xml module very fast to use your particular needed SOAP services.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsXMLXMLFeature request consume SQL 2005 Server endpointsFeature request consume SQL 2005 Server endpoints


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out