Please join us at the new JavaWorld Q&A Forums. Your existing login will work there. The discussions here are now read-only.
Anonymous
Unregistered
|
|
the architecture still suffers from some shortcomings for example what if you are trying to access microsoft's msmq queues from java the only way is jini and it its very limited. Also how can a microsoft app access a jms queue? only vendors support this stuff like ibm mq 5.3 that comes with dlls to let .net application talk to queues. few vendors support this. until the ability for hetergeneous can connect seamlessly to a standard esb hits the market web services will fall short of its true value and will simply be alot of hype. why do i need to need to use web services between java apps and take a performance hit when i can simply use the latest version of rmi between java apps. the whole purpose of web services to simply to reuse object model across applications. i think web services still has alot of maturing especially when it comes to .net and java interoperability. any comments?
|
hsheil
Unregistered
|
|
Hi
yes you are right, I don't expect my taxonomy to address accessing Microsoft MSMQ directly. I would expect to address it through a web service or through a bridge framework that exposed the MSMQ to me as a JMS queue (I assumed you meant JNI and Jini in your post too..).
>>i think web services still has alot of maturing especially when it comes to .net and java interoperability. any comments?
I agree, not just for .NET and Java interop, but more generally as the assumed default SOA implementation.
Regards
Humphrey
|
|
0 registered and 1 anonymous users are browsing this forum.
Moderator:
Print Topic
|
Forum Permissions
You cannot start new topics
You cannot reply to topics
HTML is disabled
UBBCode is enabled
|
Rating:
Topic views: 4027
|
|
|
|
|
|
Powered by UBB.threads™ 6.5.5
Previous
Index
Next
Threaded
Edit
Reply
Quote
