Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / June 2005

Tip: Looking for answers? Try searching our database.

filters in WSE3.0

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
serzsa - 09 Jun 2005 02:02 GMT
My current WSE2.0 solution uses custom filters. Downloaded WSE3.0, changed
config section from microsoft.web.services2 to 3. Now I get an error loading
the config and apparently it's related to <filters> section (if I comment it
out the error goes away). The error is: "WSE032: There was an error loading
the microsoft.web.services3 configuration section."

Has anyone encountered that?

Thanks.
uzi - 10 Jun 2005 17:31 GMT
Hi

i've opened the WSE3 settings dll with Reflector and the supprt for filters
has been removed and not supported anymore.

so, filters are out.

> My current WSE2.0 solution uses custom filters. Downloaded WSE3.0, changed
> config section from microsoft.web.services2 to 3. Now I get an error loading
[quoted text clipped - 5 lines]
>
> Thanks.
serzsa - 10 Jun 2005 17:34 GMT
Thanks. I've figured that by looking at the inner exception message. It looks
like lots of other things were also changed/removed and not reflected in the
documentation at all. I guess, it's our job to point all that out :)

I tried since using PolicyAssertion instead. Using doc proved worthless
(everything is old describing relevant configuration elements), so I looked
at one of the samples (custom assertions). But I couldn't make my policy file
to be recognized. Moreover, providing anything at all in the <policy
fileName="garbage here" /> (under <microsoft.web.services3>) element for file
name didn't make any difference and didn't cause any errors.

> Hi
>
[quoted text clipped - 12 lines]
> >
> > Thanks.
serzsa - 11 Jun 2005 18:40 GMT
Apparently, there's a new method SetPolicy on both SoapSender and
SoapReceiver classes that must be called in order to set all that mechanism
in motion.

> Thanks. I've figured that by looking at the inner exception message. It looks
> like lots of other things were also changed/removed and not reflected in the
[quoted text clipped - 23 lines]
> > >
> > > Thanks.
Youenn Trebossen - 13 Jun 2005 10:06 GMT
You should check the Security Hands On Lab for WSE 3.0 CTP available on
MSDN.

The Part 5 of the lab is about "Custom policy Assertions"

HTH

Youenn

> Apparently, there's a new method SetPolicy on both SoapSender and
> SoapReceiver classes that must be called in order to set all that mechanism
[quoted text clipped - 27 lines]
>>>>
>>>>Thanks.
tjanczuk - 14 Jun 2005 05:15 GMT
In order to port a custom filer written in WSE 2.0 to WSE 3.0 you need to:

1. Derive your custom filer class from Microsoft.Web.Services3.SoapFilter.
You will need to implement a ProcessMessage method, much like the WSE 2.0
custom filters did.
2. Implement a class that derives from
Microsoft.Web.Services3.Design.PolicyAssertion and returns an instance of
your custom filer in at least one of the four virtual Create*Filter methods
it must implement.
3. Add an instance of your custom policy assertion to a a Policy. This can
be done either declaratively through the use of XML policy file, or
imperatively by instantiating the Policy class, and adding an instance of
your custom PolicyAssertion to the Policy.Assertions collection.
4. Set the custom policy you have created on the client proxy and/or your
service class. This can be done using the PolicyAttribute or the SetPolicy
method on the proxy class.

The relationship between the concepts of policy and filters has been changed
in WSE 3.0. Policy in WSE 3.0 acts as a description of a the entire pipeline.
Policy containts policy assertions. Pipeline contains soap filtes. Policy
assertions act as factories of soap filters. Policy acts as a factory of a
pipline. Policy is meant to be a cofiguration-time concept, and pipeline is a
runtime concept.

Thank you,

Tomasz Janczuk
Web Services Enhancemenent
Microsoft Corporation

> My current WSE2.0 solution uses custom filters. Downloaded WSE3.0, changed
> config section from microsoft.web.services2 to 3. Now I get an error loading
[quoted text clipped - 5 lines]
>
> Thanks.
serzsa - 14 Jun 2005 06:15 GMT
Thanks Tomasz,

I actually figured all that (including PolicyAttribute over
SoapSender/SoapReceiver descendants instead of calling SetPolicy). It's just
that lots of things seem to be missing/old from/in the documentation without
it stating so, which adds to the confusion. I understand it's CTP and if
something is not there then it's fine. However, the section on <filters> is
still there, as well as wrong attributes on, for example, <policy> elements.
It would be better if they were not there at all than providing
outdated/wrong information.

> In order to port a custom filer written in WSE 2.0 to WSE 3.0 you need to:
>
[quoted text clipped - 35 lines]
> >
> > Thanks.
DaveBradley - 14 Jun 2005 18:58 GMT
Hi serzsa,

Thank you for your feedback.

You are right in that more topics should have been pulled for this CTP. The
next CTP release will be more complete and accurate.

David Bradley
Programmer Writer
Microsoft Corporation.

> Thanks Tomasz,
>
[quoted text clipped - 46 lines]
> > >
> > > Thanks.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.