[sip-comm-dev] SipComm classpath (boot)

Hi,
I'm looking for a reference where information about SIPComm startup can be
obtained.

I've resolved issue with com.sun.media.rtp.RTPSessionMgr from Java5 JRE
which has to be replaced
by the same class from JMF.jar. Otherwise, default RTPSessionMgr always
return null for getSendStreams().
So jmf.jar has to be specified at bootclasspath, this what i found so far.

Am asking just in case, if there are more implicit requirements for
classpath or like that.

Of course, i've looked through the ide/* files which are in svn.
But they didn't tell me a lot. For example, debug.class.path is mentioned in
*.xml for NB
but as i can tell it's rather property of NB itself (i'm Eclipse user).

So debug.class.path isn't configured using those *.xml files.

···

--
Regards, Alexander

Hello Alexander,

Alexander Golubev wrote:

Hi,

I'm looking for a reference where information about SIPComm startup can
be obtained.

You can have a look at our existing startup scripts.

https://sip-communicator.dev.java.net/source/browse/checkout/sip-communicator/trunk/resources/install/debian/sip-communicator.sh.tmpl

Note the following in particular:

CLASSPATH=$LIBPATH/jdic_stub.jar:$LIBPATH/jdic-all.jar:$LIBPATH/felix.jar:$LIBPATH/bcprovider.jar:$SCDIR/sc-bundles/sc-launcher.jar:$SCDIR/sc-bundles/util.jar

You can also look for inspiration in our build.xml "run" target although
that one would probably look more convoluted than the shell script.

I've resolved issue with com.sun.media.rtp.RTPSessionMgr from Java5 JRE
which has to be replaced
by the same class from JMF.jar. Otherwise, default RTPSessionMgr always
return null for getSendStreams().

I am not sure I understand this. Is there really an RTPSessionMgr in the
J5 JRE?

So jmf.jar has to be specified at bootclasspath, this what i found so far.

As you can see in the above declaration of the CLASSPATH variable,
there's no need to include jmf.jar. The reason for this is the fact that
we include it inside the media.jar bundle.

Hope this helps

Emil

···

Am asking just in case, if there are more implicit requirements for
classpath or like that.

Of course, i've looked through the ide/* files which are in svn.
But they didn't tell me a lot. For example, debug.class.path is
mentioned in *.xml for NB
but as i can tell it's rather property of NB itself (i'm Eclipse user).

So debug.class.path isn't configured using those *.xml files.

--
Regards,
Alexander

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

Hi Emil,
Thanks for the explanation.

The script information is the same i was able to get from running
SIP-Comm java process when inspected its arguments.

As for RTPSessionMgr inside of JRE - i was wrong and have just realized
that.

Some times ago i was making research for codecs and installed JMStudio
which
probably added jmf.jar under my JAVA_JRE/lib/ext. That's why i was
experiencing
that kind of problem.

···

2009/5/18 Emil Ivov <emcho@sip-communicator.org>

Hello Alexander,

Alexander Golubev wrote:
> Hi,
>
> I'm looking for a reference where information about SIPComm startup can
> be obtained.

You can have a look at our existing startup scripts.

https://sip-communicator.dev.java.net/source/browse/checkout/sip-communicator/trunk/resources/install/debian/sip-communicator.sh.tmpl

Note the following in particular:

CLASSPATH=$LIBPATH/jdic_stub.jar:$LIBPATH/jdic-all.jar:$LIBPATH/felix.jar:$LIBPATH/bcprovider.jar:$SCDIR/sc-bundles/sc-launcher.jar:$SCDIR/sc-bundles/util.jar

You can also look for inspiration in our build.xml "run" target although
that one would probably look more convoluted than the shell script.

>
> I've resolved issue with com.sun.media.rtp.RTPSessionMgr from Java5 JRE
> which has to be replaced
> by the same class from JMF.jar. Otherwise, default RTPSessionMgr always
> return null for getSendStreams().

I am not sure I understand this. Is there really an RTPSessionMgr in the
J5 JRE?

> So jmf.jar has to be specified at bootclasspath, this what i found so
far.

As you can see in the above declaration of the CLASSPATH variable,
there's no need to include jmf.jar. The reason for this is the fact that
we include it inside the media.jar bundle.

Hope this helps

Emil

> Am asking just in case, if there are more implicit requirements for
> classpath or like that.
>
> Of course, i've looked through the ide/* files which are in svn.
> But they didn't tell me a lot. For example, debug.class.path is
> mentioned in *.xml for NB
> but as i can tell it's rather property of NB itself (i'm Eclipse user).
>
> So debug.class.path isn't configured using those *.xml files.
>
> --
> Regards,
> Alexander
>

--
Emil Ivov, Ph.D. 30a rue de la Patrie
Project Lead 67300 Schiltigheim
SIP Communicator
emcho@sip-communicator.org FAX: +33.1.77.62.47.31
http://sip-communicator.org PHONE: +33.1.77.62.43.30

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

--
Александр.