Axis Soap over JMS to build a listener for uncommon service

[abondi]

Hi to all.
I posted yesterday a message: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=46934 and I'd like to ask if I'm proceeding the right way.

So, to resolve my problem, I should use: Apache Axis(Soap) over JMS.
The problem is that I must connect to the port 8000 to a server that doesn't use http but a proprietary protocol, which I can't modify. Moreover I can't change the way the server communicates with me.

To make it clearer, now I use it through a telnet connection writing commands and waiting for the asynchronous response. Is it possible using these technologies?

Do you have some links/examples?

Thank you, I'm really studying hard J2EE but it's so huge I'd like not to waste time moving towards something unuseful!:)

Regards,
Andrea

[adrian.brock]

You did not understand my comment.
I said Axis has SOAP over JMS that uses the correlation id/replyto processing.
Not that you should SOAP, it was an example.

Regards,
Adrian

[abondi]

Ok, I didn't understand...
uhm...
I still don't understand!:(

You're really helping me and I don't want to waste your time, but I don't see the way to resolve the problem.
I don't have access to the server machine. To define better the problem I'll write a sample telnet session I use now:

Me:
telnet 8000
...
login:****
password:****
[I write some commands for setting up the way I am working, the connection use a proprietary protocol]
SendMode
Report=true

Server:
OK

Me: [now I send a new message]
Send
Dest=391241241
Body=Hello Everybody

Server:
MsgID=1254515 [a unique ID assigned by the server]
OK

Me: [send some other messages]
Send
Dest=28709217
Body=bla foo bar

Server:
MsgID=3097519
OK

[Now I stay logged in and when the status of a message changes the server notifies me with a message preceeded by"!"]
Server:
!StatusInd
!MsgID=1254515
!Status=in queue
![other informations about the message]
!OK

Me:
Logout

And the connection finishes.

Can I manage all these StatusInd with a Message-Driven Bean and a JMS, even if the server doesn't work with Java but in this proprietary way?

Thank you and everybody who will reply for helping a J2EE newbie!

Andrea

[abondi]

Ok, I didn't understand...
uhm...
I still don't understand!:(

You're really helping me and I don't want to waste your time, but I don't see the way to resolve the problem.
I don't have access to the server machine. To define better the problem I'll write a sample telnet session I use now:

Me:
telnet server 8000
login:****
password:****
[I write some commands for setting up the way I am working, the connection use a proprietary protocol]
SendMode
Report=true

Server:
OK

Me: [now I send a new message]
Send
Dest=391241241
Body=Hello Everybody

Server:
MsgID=1254515 [a unique ID assigned by the server]
OK

Me: [send some other messages]
Send
Dest=28709217
Body=bla foo bar

Server:
MsgID=3097519
OK

[Now I stay logged in and when the status of a message changes the server notifies me with a message preceeded by"!"]
Server:
!StatusInd
!MsgID=1254515
!Status=in queue
![other informations about the message]
!OK

Me:
Logout

And the connection finishes.

Can I manage all these StatusInd with a Message-Driven Bean and a JMS, even if the server doesn't work with Java but in this proprietary way?

Thank you and everybody who will reply for helping a J2EE newbie!

Andrea

[adrian.brock]

This has nothing to do with JMS. I thought you were talking about the contents
of a JMS Message.

You'll have to write it yourself.

Regards,
Adrian

[abondi]

:(
I'm really sad because I was charmed by JMS technology. I'll try to use it in some way to solve another problem, for now I'll look for technologies I could use to solve this one.

Any suggestion?
Connectors, Sockets, anything?

I promise, this is the last time I talk about this!:)
But J2EE is so huge that I'd like at least some suggestions on what to study!

Bye, Thank you!

Andrea

[abondi]

I thought about resolving the problem with JMS because it was studied to resolve asynchronous message delivery, which is what I'm trying to achieve.

I've looked around and found a probable implementation architecture. Could you please tell me if I'm getting some concepts wrong?

1- my customer decides to send some messages he wants to send [to better understand, I'll call them SMS] through the interface I developed
2- a new JMS Message is created
3- a MDB wake up and performs the initial steps to connect throught native calls
4- new MDB wake up and, using the connection, send created SMS
5- another process use the connection to read the StatusInd and create a new JMS Message to describe the message status

My implementation doubt is that I must send a lot of SMS (around 4000 SMS in one action), so, in pass 4, should I create 4000 MDB instances? It should be a clean implementation, maybe this way I could use also correlation id/replyto headers in passage 5, but I would it waste many resources?

And, also, how can I implement the "native calls"? Is there a way to create a class that support this proprietary protocol?

And what about creating the connections with the server? Should I use java.net.socket?

Really thank you,
Andrea