Can Java apps integrate with VB apps?

Question

I am not sure exactly what I am asking....The guys that do the software development for the company I work for write everything in VB. I am currently the Web developer for this company and I specialize in Flex apps. I am thinking about expanding into their area. But I do not want to do VB, I don't mean to bash on VB but the coding syntax is not for me. So I am wondering if Java can integrate with VB? Also not sure if it matters but I think everything they do is procedural, and I will be doing OOP.

Thanks.

Answer 1

There are lots of integration opportunities, but before examining them, if I were you I would re-examine the question itself.

It should be exceptional to introduce a new language into an established project. The desires or aesthetic preference or skillset of a single developer is not a good enough justification to do so. Introducing a new language into a project should be a strategic decision for the project, not a backhanded one.

If you do choose to expand the core languages used to develop the system,

• COM interop
  is possible with JACOB. I believe IBM has a bridge as well.(Check alphaworks)
• Java-.NET bridging
  is possible via JNBridge and other bridges. This makes sense only if VB.NET is in use.
• SOAP, XML document exchange, REST
  suitable over a services boundary. It requires TCP or HTTP or some network protocol.
• common data stores
  can serve as a rendezvous point. Both Java and VB can read and update data in SQL Server, Oracle, MSMQ, MQSeries, and so on. Even a filesystem can be an integration point.

Think of data format as related to, but ideally independent of, the integration mechanism. What I mean is: You can use an XML document for integration, whether it is stored in a database, or sent over a REST interface, or stored in a filesystem, or put/get on a queue. You can use a comma-separated file over any of those mechanisms as well.

Answer 2

Potentially they could expose a service layer via soap or something simpler? Also you could always work against the same database with different languages however unless most of the logic is in stored procedures (not necessarily recommending this approach) then you end up with repeated code.