Jan Schroeder wrote:
our development group here is very java centric. We now have to use (and extend) a product that is entirely Microsoft oriented (COM, ActiveX, VB, JavaScript).
We have the immediate need to provide access to an LDAP server (over SSL). For that we are supposed to write an appropriate COM object.... which I am sure is very doable but given our skill set it will take a little bit too long. So we considered writing the logic in Java and to somehow wrap it up and register it as a COM component. We found a few websites describing something like this (Suns ActiveX Packager For Beans; Microsofts JavaReg, which doesn't seem to exist on their web site anymore).
I was wondering if anybody of you has some experiences with such a solution and can tell us about possible problems.
Right now we are looking into the following options:
1) bite the bullet and write the component in whatever 'Microsoft based' language we can (we don't have any tools for that and we don't know yet how to do that -> takes long)
2) try to find a third party component for LDAP access and costumize it (no idea if this is doable; I read about a component but it didn't allow SSL connections)
3) write a JavaBean and use Sun's ActiveX Packager For Beans to deploy it (we don't know about any possible problems with that solution; how do we make all the necessary java libs accessible? Does it matter that we have to use a specific, very old Miccrosoft JVM?)
4) write the Java logic and use JavaReg to deploy it (I can't find JavaReg anywhere; + all the problems above in the ActiveX Packager item)
5) write a tiny server application in Java that just listens on a port for requests, handles the LDAP lookup and responds with an appropriate document fragment; then we just (still) have to write a COM component that does the request to this port and handles the reply
Does anybody have better ideas, experiences, answers to any of the questions? Comments (especially about the options 3 and 4) are VERY welcome!
You can write a Java web service and call it from a .Net component (which is easy) . Then expose the .Net component as a COM component (which is easy too). And you're done!
_______________________________________________ Juglist mailing list [EMAIL PROTECTED] http://trijug.org/mailman/listinfo/juglist_trijug.org
