Add New OperationSet

Hello all,

first I want to say nice job to all the Sip-Communicator
Team, I'm an
every day SipCom user and I just love it !

So, here's my problem. I'm starting to develop a new plugin
which is
based on Jabber protocol. I'm playing with the Smack API in
order to
implement specific Jabber message. Currently with the
ProtocolProviderService, I can not have an access to the low
level
connection Objet in order to send and receive my custom
Jabber
messages.

Shall we create a new generic interface in order to access
to such an
object in the protocol specific implementation ? I'm
thinking on a
OperationSetConnection and a Connection interface in
net.java.sip.communicator.service.protocol .

Best regards and bravo,

Guillaume Schreiner

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi,
In ProtocolProviderService for the jabber protocol which is

ProtocolProviderServiceJabberImpl
you have XMPPConnection connection which is what you need I
think.

Guillaume Schreiner wrote:
> Hello all,
>
> first I want to say nice job to all the
Sip-Communicator Team, I'm an
> every day SipCom user and I just love it !
>
> So, here's my problem. I'm starting to develop a new
plugin which is
> based on Jabber protocol. I'm playing with the Smack
API in order to
> implement specific Jabber message. Currently with the
> ProtocolProviderService, I can not have an access to
the low level
> connection Objet in order to send and receive my custom
Jabber
> messages.
>
> Shall we create a new generic interface in order to
access to such an
> object in the protocol specific implementation ? I'm
thinking on a
> OperationSetConnection and a Connection interface in
> net.java.sip.communicator.service.protocol .
>
> Best regards and bravo,
>
> Guillaume Schreiner
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

2007/2/9, Damian Minkov <damenchodamencho.com>:
> Hi,
> In ProtocolProviderService for the jabber protocol
which is
> ProtocolProviderServiceJabberImpl
> you have XMPPConnection connection which is what you
need I think.
>

Hi Damian,

the problem is that the bundle protocol-jabber.jar doesn't
export the
package net.java.sip.communicator.impl.protocol.jabber, so I
can't get
a reference to the
ProtocolProviderServiceJabberImpl in order to cast the
ProtocolProviderService in another bundle.

In fact, this is normal behaviour because of the concept of
OSGI which
export only the services interface and not the
implementation. That's
why I though I should create a new OperationSet which
provide an
interface to the connection and the Jabber implementation
should
return a pointer to the XMPPConnection.

WDYT ?

Guillaume Schreiner

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello Guillaume,

Thanks for the nice words!

This has been a question that I've been asking myself for
some time now.
What mechanism should we have so that volunteers could not
only
implement new protocols but also be able to extend existing
implementations?

I am afraid that there's no way we could do this
independently of the 
underlying implementation since that's what you'd be
interacting with 
when adding extra functionality to an existing protocol
provider. So 
we'll have to find specific ways of doing so for every
provider 
implementation.

This means that we'll have to think of a jabber/smack
specific interface 
that is exported by the jabber implementation and that would
allow you 
to get access to everything you need (such as the
XMPPConnection).

Would you want to take a hack on such an interface and send
it to the list?

Emil




Guillaume Schreiner wrote:
> 2007/2/9, Damian Minkov <damenchodamencho.com>:
>> Hi,
>> In ProtocolProviderService for the jabber protocol
which is
>> ProtocolProviderServiceJabberImpl
>> you have XMPPConnection connection which is what
you need I think.
>>
> 
> Hi Damian,
> 
> the problem is that the bundle protocol-jabber.jar
doesn't export the
> package net.java.sip.communicator.impl.protocol.jabber,
so I can't get
> a reference to the
> ProtocolProviderServiceJabberImpl in order to cast the
> ProtocolProviderService in another bundle.
> 
> In fact, this is normal behaviour because of the
concept of OSGI which
> export only the services interface and not the
implementation. That's
> why I though I should create a new OperationSet which
provide an
> interface to the connection and the Jabber
implementation should
> return a pointer to the XMPPConnection.
> 
> WDYT ?
> 
> Guillaume Schreiner
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net