[Mono-list] A Plugin and WebService Issue
Pablo Fischer
pablo@pablo.com.mx
Sat, 22 May 2004 12:09:33 -0500
--=-6TdqAuTfvimWmqkFklmE
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: quoted-printable
But that is after compiling the code, right?, with the MethodInfo, Get,
Invoke methods.
I know that I can do this when the assembly is already compiled, but I'd
like to do this BEFORE the assembly is compiled, so, if a method doesn't
exists the compilation process should stop.
Pablo
El s=E1b, 22-05-2004 a las 11:48, Mark Gimelfarb escribi=F3:
> If I understand you correclty,
> you can make use of the MethodInfo class to do method discovery.
>=20
> Regards,
> Mark.
>=20
> Quoting Pablo Fischer <pablo@pablo.com.mx>:
>=20
> > Ok ok, sorry ;-)
> >=20
> > If I want to create a plugin, I should generate the wsdl code of my
> > webservice (SOAP) then compile it as a library.. this library is the
> > plugin.
> >=20
> > What I'm looking for is that, when the user tries to make it library,
> > the user should compile it with a resource or another library. The
> > resource SHOULD look in the code before making it a library.
> >=20
> > What SHOULD look in the WSDL code?, methods, so the resource should loo=
k
> > if the WSDL code has a : Post method, a DeletePost, etc. if these
> > methods are ok, then make it a library with some AssemblyInfo.
> >=20
> > Pablo
> > El s=E1b, 22-05-2004 a las 11:08, Rob.Tillie@Student.tUL.EDU escribi=F3=
:
> > > I don't fully understand you.
> > > If you require that any plugin implements your interface ( which shou=
ld
> > have
> > > those methods of you like Post etc.) then you're fine.
> > > What else should you want then?
> > >=20
> > > Greetz,
> > > -- Rob.
> > >=20
> > > -----Original Message-----
> > > From: Pablo Fischer [mailto:pablo@pablo.com.mx]=20
> > > Sent: Saturday, May 22, 2004 6:00 PM
> > > To: mono-list@lists.ximian.com
> > > Subject: RE: [Mono-list] A Plugin and WebService Issue
> > >=20
> > > Sure,
> > >=20
> > > I'd like to be sure that the plugin of the user has a 'Post' method f=
or
> > > example, or a 'DeletePost', if all the 'rules' are ok the code will b=
e
> > > compiled with an AssemblyInfo.
> > >=20
> > > I know that I can verify if the method exists invoking it and if I ge=
t
> > > Null there's no method, but I'd like to do this also in the compilati=
on
> > > process.
> > >=20
> > > See ya!
> > > El s=E1b, 22-05-2004 a las 00:22, Rob.Tillie@Student.tUL.EDU escribi=
=F3:
> > > > Could you tell us why you want to check the code?
> > > >=20
> > > > Greetz,
> > > > -- Rob.
> > > >=20
> > > > -----Original Message-----
> > > > From: Pablo Fischer [mailto:pablo@pablo.com.mx]=20
> > > > Sent: Thursday, May 20, 2004 5:04 PM
> > > > To: mono-list@lists.ximian.com
> > > > Subject: Re: [Mono-list] A Plugin and WebService Issue
> > > >=20
> > > > Thanks people!
> > > >=20
> > > > When I start writing my app (mbloggy) I was using Interfaces as plu=
gins
> > > > (xmlrpc plugins), then I started reading info about SOAP and I'm in
> > love
> > > > with it, the fact that SOAP supports any encoding makes me happy :-=
).
> > > >=20
> > > > What I was looking for is to do the same that "Plugins in Mono" (M.
> > > > Icaza) says :-).
> > > >=20
> > > > However, I'd like to ask something else: I want EVERY plugin be
> > compiled
> > > > like I want, yeah, when I compile the plugin (the .dll) I'd like to
> > > > check the methods and validate the plugin, if the plugin is ok, com=
pile
> > > > it and add some Assembly Info (AssemblyInfo, right?), where should =
I
> > > > look?, NUnit I think is to check compiled applications but I want t=
o
> > > > 'check' my code BEFORE being a .dll.
> > > >=20
> > > > Thanks!
> > > > Pablo
> > > > El jue, 20-05-2004 a las 05:38, RoBiK escribi=F3:
> > > > > Hi,
> > > > >=20
> > > > > I would use this approach:
> > > > >=20
> > > > > 1) you must have a plug-in Interface defined, that each plug-in m=
ust
> > > > > implement
> > > > > 2) when the application starts, use static
> > > System.IO.Directory.GetFiles()
> > > > > method to get the names of assemblies in the plug-in directory
> > > > > 3) for each plug-in-assembly file call static
> > > > > System.Reflection.Assembly.LoadFrom() method to load the assembly
> > into
> > > the
> > > > > current AppDomain, then call the method
> > > > > System.Reflection.Assembly.GetTypes() on the
> > System.Reflection.Assembly
> > > > > instance that you've got from the previous LoadFrom() method
> > > > > 4) for each Type that you get from previous GetType() method use =
the
> > > "is"
> > > > > operator to check if the particular type implements the plug-in
> > > interface,
> > > > > if it does, you have a type that implements your plug-in interfac=
e.=20
> > > > > 5) call static Syste.Activator.CreateInstance() method with the t=
ype
> > > from
> > > > > previous step as parameter. Cast the result to the plug-in-interf=
ace
> > > type
> > > > > and store it for example in an array for later use.
> > > > > 6) now you have an array of plug-in instances and can call the
> > interface
> > > > > methods on them
> > > > >=20
> > > > > This is just an example, there are several other approaches which=
are
> > > more
> > > > > or less similar to this one... everything depends on the needs of
> > your
> > > > > application.
> > > > >=20
> > > > > RoBiK
> > > > >=20
> > > > > Quoting Pablo Fischer <pablo@pablo.com.mx>:
> > > > >=20
> > > > > > Hi!
> > > > > >
> > > > > > I would like to have some comments and suggestions about a issu=
e.
> > > > > >
> > > > > > I am working in a Blog Client (mbloggy) that will work ONLY in =
SOAP
> > > (NO
> > > > > > XMLRPC) for different CMS and Blogs (phpnuke, postnuke, jaws, e=
tc,
> > > etc).
> > > > > > To work with all these blogs I'm planning to use a 'plugin'
> > system,
> > > > > > based in assemblies, for example:
> > > > > >
> > > > > > If a developer wants the plugin for a CMS (like drupal), he can
> > save
> > > his
> > > > > > .dll plugin in ~./mbloggy/plugins and when mbloggy starts it wi=
ll
> > read
> > > > > > default plugins (in /etc/mbloggy) and the user plugins. When
> > mbloggy
> > > > > > finds a new plugin it will be added to a 'drop down' (gtk#) so =
the
> > > user
> > > > > > can use it.
> > > > > >
> > > > > > My problem?, yes, I don't know which is the best option:
> > > > > >
> > > > > > a) Use .dll assemblies as plugins. But, how to connect to each
> > plugin
> > > > > > from the front end?, exists a data type that can 'clone' anothe=
r
> > > > > > object?, so I can do something like this:
> > > > > >
> > > > > > Wrapper wrap =3D new Wrapper();
> > > > > > wrap.Clone("assemblie.dll");
> > > > > > wrap.Url =3D "http://www.foo.bar.com/foo.aspx?wsdl"
> > > > > > wrap.DeletePost(3);
> > > > > >
> > > > > > So I can use the 'methods' of assemblie.dll in the wrap object?=
.
> > > > > >
> > > > > > b) Or use just one .dll and let the developers to 'develop' jus=
t
> > the
> > > > > > WebService (server)?, So I can just work like this:
> > > > > >
> > > > > > Client c =3D new Client();
> > > > > > c.Url =3D "http://www.foo.bar.com/foo.aspx?wsdl"
> > > > > > c.DeletePost(3);
> > > > > >
> > > > > > Which is the best option? and where can I find more information=
for
> > > the
> > > > > > best option?.
> > > > > >
> > > > > > Thanks!
> > > > > > Pablo
> > > > > > --
> > > > > > Pablo Fischer Sandoval (pablo [arroba/at] pablo.com.mx)
> > > > > > Fingerprint: 5973 0F10 543F 54AE 1E41 EC81 0840 A10A 74A4 E5C=
0
> > > > > > http://www.pablo.com.mx
> > > > > > http://www.debianmexico.org
> > > > > >
> > --=20
> > Pablo Fischer Sandoval (pablo [arroba/at] pablo.com.mx)
> > Fingerprint: 5973 0F10 543F 54AE 1E41 EC81 0840 A10A 74A4 E5C0
> > http://www.pablo.com.mx
> > http://www.debianmexico.org
> >=20
>=20
>=20
>=20
> _______________________________________________
> Mono-list maillist - Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
--=20
Pablo Fischer Sandoval (pablo [arroba/at] pablo.com.mx)
Fingerprint: 5973 0F10 543F 54AE 1E41 EC81 0840 A10A 74A4 E5C0
http://www.pablo.com.mx=20
http://www.debianmexico.org
--=-6TdqAuTfvimWmqkFklmE
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada
digitalmente
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQBAr4lNCEChCnSk5cARAoqpAJ96yiL3O22sQ/Uee6G32cWJhy3wlACfRUWf
+nAxeT+mWQ4cfXsEseq1Yqs=
=YnX/
-----END PGP SIGNATURE-----
--=-6TdqAuTfvimWmqkFklmE--