[sip-comm-dev] Question regarding FMJ versus JMF in SC


#1

All,

just did an update from SVN and got quite a number of problem
messages in Eclipse. The root cause is that several classes
import net.sf.fmj.* classes. Thus my question: does SC requires
to use FMJ and discardes JMF? Or is it necessary to exclude
some classes from the Eclipse build path?

REgards,
Werner

···

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


#2

I seem to recall that FMJ is optional, and that there is no requirement for FMJ when running a "production" SC app.

FMJ is only referenced for optional classes which are only used if FMJ is enabled.

Ken

Werner Dittmann wrote:

···

All,

just did an update from SVN and got quite a number of problem
messages in Eclipse. The root cause is that several classes
import net.sf.fmj.* classes. Thus my question: does SC requires
to use FMJ and discardes JMF? Or is it necessary to exclude
some classes from the Eclipse build path?

REgards,
Werner

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

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


#3

Hmmm .... several topics:

- then I need a way to tell Eclipse to use these classes only
   if FMJ is enabled. AFAIK this would require two different
   Eclipse environments for SC because Eclipse does not have a way to
   to "conditional" compiling.

- even an "ant rebuild" fails if fmj.jar is not available, thus
   I would classify fmj as a requirement because SC has a hard coded
   dependency on some FMJ specific classes.

Regards,
Werner

Ken Larson schrieb:

···

I seem to recall that FMJ is optional, and that there is no requirement for FMJ when running a "production" SC app.

FMJ is only referenced for optional classes which are only used if FMJ is enabled.

Ken

Werner Dittmann wrote:

All,

just did an update from SVN and got quite a number of problem
messages in Eclipse. The root cause is that several classes
import net.sf.fmj.* classes. Thus my question: does SC requires
to use FMJ and discardes JMF? Or is it necessary to exclude
some classes from the Eclipse build path?

REgards,
Werner

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

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

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


#4

Hi,

I'm currently working on integrating lti-civil in sip-communicator and creating h264 codec.
Currently there are still some issues but I hope they will be cleared soon. So some problems may raise when using the video.
Integrating civil needed some classes from fmj. Currently there is a jar file in lib/installer-exclude with name fmj.jar but its not
a full fmj, its just the classes used for lti-civil which are from latest fmj CVS. Maybe its a good point to rename it to something like
fmj-lti.jar. I hope this makes sense.

Cheers
damencho

Werner Dittmann wrote:

···

All,

just did an update from SVN and got quite a number of problem
messages in Eclipse. The root cause is that several classes
import net.sf.fmj.* classes. Thus my question: does SC requires
to use FMJ and discardes JMF? Or is it necessary to exclude
some classes from the Eclipse build path?

REgards,
Werner

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

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


#5

In eclipse, you can right-click to exclude certain packages or files from compilation.

However, there is no harm in including fmj with SC if it is not "enabled"... that might be simpler.

Ken

Werner Dittmann wrote:

···

Hmmm .... several topics:

- then I need a way to tell Eclipse to use these classes only
  if FMJ is enabled. AFAIK this would require two different
  Eclipse environments for SC because Eclipse does not have a way to
  to "conditional" compiling.

- even an "ant rebuild" fails if fmj.jar is not available, thus
  I would classify fmj as a requirement because SC has a hard coded
  dependency on some FMJ specific classes.

Regards,
Werner

Ken Larson schrieb:

I seem to recall that FMJ is optional, and that there is no requirement for FMJ when running a "production" SC app.

FMJ is only referenced for optional classes which are only used if FMJ is enabled.

Ken

Werner Dittmann wrote:

All,

just did an update from SVN and got quite a number of problem
messages in Eclipse. The root cause is that several classes
import net.sf.fmj.* classes. Thus my question: does SC requires
to use FMJ and discardes JMF? Or is it necessary to exclude
some classes from the Eclipse build path?

REgards,
Werner

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

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

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

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


#6

Hey folks,

In the context of our gradual move to FMJ, we are currently working on
integrating Ken's lti-civil libs into SIP Communicator. This is why
we've added a few new dependencies to FMJ in the felix.properties files.
Apparently the eclipse .classpath got left behind.

Will fix this first thing tomorrow.

Cheers
Emil

Ken Larson wrote:

···

In eclipse, you can right-click to exclude certain packages or files
from compilation.

However, there is no harm in including fmj with SC if it is not
"enabled"... that might be simpler.

Ken

Werner Dittmann wrote:

Hmmm .... several topics:

- then I need a way to tell Eclipse to use these classes only
  if FMJ is enabled. AFAIK this would require two different
  Eclipse environments for SC because Eclipse does not have a way to
  to "conditional" compiling.

- even an "ant rebuild" fails if fmj.jar is not available, thus
  I would classify fmj as a requirement because SC has a hard coded
  dependency on some FMJ specific classes.

Regards,
Werner

Ken Larson schrieb:

I seem to recall that FMJ is optional, and that there is no
requirement for FMJ when running a "production" SC app.

FMJ is only referenced for optional classes which are only used if
FMJ is enabled.

Ken

Werner Dittmann wrote:

All,

just did an update from SVN and got quite a number of problem
messages in Eclipse. The root cause is that several classes
import net.sf.fmj.* classes. Thus my question: does SC requires
to use FMJ and discardes JMF? Or is it necessary to exclude
some classes from the Eclipse build path?

REgards,
Werner

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

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

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

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

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


#7

All,

some thoughts here: is FMJJ used only to enable lti-civil or is it used
also as full replacement to JMF, i.e. the RTP stack? Background of this is
that I then need to adapt my tests regarding ZRTP integration. Currently
I use JMF.

My proposal would be to use FMJ as full replacement if SC has a hard
dependency on FMJ. Otherwise we may face some problems because FMJ implements
the same packages as JMF.

Regards,
Werner

Emil Ivov schrieb:

Hey folks,

In the context of our gradual move to FMJ, we are currently working on
integrating Ken's lti-civil libs into SIP Communicator. This is why
we've added a few new dependencies to FMJ in the felix.properties files.
Apparently the eclipse .classpath got left behind.

Will fix this first thing tomorrow.

Cheers
Emil

Ken Larson wrote:

In eclipse, you can right-click to exclude certain packages or files from compilation.

However, there is no harm in including fmj with SC if it is not "enabled"... that might be simpler.

Ken

Werner Dittmann wrote:

Hmmm .... several topics:

- then I need a way to tell Eclipse to use these classes only
  if FMJ is enabled. AFAIK this would require two different
  Eclipse environments for SC because Eclipse does not have a way to
  to "conditional" compiling.

- even an "ant rebuild" fails if fmj.jar is not available, thus
  I would classify fmj as a requirement because SC has a hard coded
  dependency on some FMJ specific classes.

Regards,
Werner

<SNI --- SNAP >

···

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


#8

The classes where FMJ implements the same ones as JMF, those are generally compatible (not including any "stub" testing versions of sun internal classes which should not be included in the FMJ jar used by SC anyway). The main thing which determines the actual functionality of FMJ vs JMF are the plug-in codecs, handlers, etc - and these have net.sf.fmj and com.sun and com.ibm packages, so they don't overlap in namespace.

I guess what I'm saying is it is possible to choose one of JMF or FMJ for the JMF public API/infrastructure (javax.media.*), and separately figure out what codecs and handlers you are going to use (determined by the FMJ/JMF registry and/or defaults).

My recommendation is to include FMJ as a dependency, and make it explicit/clear which classpath order is being used (FMJ first or JMF first), and to make it clear what JMF/FMJ registry settings are used. Then use whatever is needed or 100% compatible from FMJ, and use JMF for the rest.

Ken

Werner Dittmann wrote:

···

All,

some thoughts here: is FMJJ used only to enable lti-civil or is it used
also as full replacement to JMF, i.e. the RTP stack? Background of this is
that I then need to adapt my tests regarding ZRTP integration. Currently
I use JMF.

My proposal would be to use FMJ as full replacement if SC has a hard
dependency on FMJ. Otherwise we may face some problems because FMJ implements
the same packages as JMF.

Regards,
Werner

Emil Ivov schrieb:

Hey folks,

In the context of our gradual move to FMJ, we are currently working on
integrating Ken's lti-civil libs into SIP Communicator. This is why
we've added a few new dependencies to FMJ in the felix.properties files.
Apparently the eclipse .classpath got left behind.

Will fix this first thing tomorrow.

Cheers
Emil

Ken Larson wrote:

In eclipse, you can right-click to exclude certain packages or files from compilation.

However, there is no harm in including fmj with SC if it is not "enabled"... that might be simpler.

Ken

Werner Dittmann wrote:

Hmmm .... several topics:

- then I need a way to tell Eclipse to use these classes only
  if FMJ is enabled. AFAIK this would require two different
  Eclipse environments for SC because Eclipse does not have a way to
  to "conditional" compiling.

- even an "ant rebuild" fails if fmj.jar is not available, thus
  I would classify fmj as a requirement because SC has a hard coded
  dependency on some FMJ specific classes.

Regards,
Werner

<SNI --- SNAP >

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

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


#9

Hey all,

Ken Larson wrote:

My recommendation is to include FMJ as a dependency, and make it
explicit/clear which classpath order is being used (FMJ first or JMF
first), and to make it clear what JMF/FMJ registry settings are used.
Then use whatever is needed or 100% compatible from FMJ, and use JMF for
the rest.

Yes, that's the plan. It'll probably take us some more time before we
get there completely but we will eventually.

Cheers
Emil

···

Ken

Werner Dittmann wrote:

All,

some thoughts here: is FMJJ used only to enable lti-civil or is it used
also as full replacement to JMF, i.e. the RTP stack? Background of
this is
that I then need to adapt my tests regarding ZRTP integration. Currently
I use JMF.

My proposal would be to use FMJ as full replacement if SC has a hard
dependency on FMJ. Otherwise we may face some problems because FMJ
implements
the same packages as JMF.

Regards,
Werner

Emil Ivov schrieb:

Hey folks,

In the context of our gradual move to FMJ, we are currently working on
integrating Ken's lti-civil libs into SIP Communicator. This is why
we've added a few new dependencies to FMJ in the felix.properties files.
Apparently the eclipse .classpath got left behind.

Will fix this first thing tomorrow.

Cheers
Emil

Ken Larson wrote:

In eclipse, you can right-click to exclude certain packages or files
from compilation.

However, there is no harm in including fmj with SC if it is not
"enabled"... that might be simpler.

Ken

Werner Dittmann wrote:

Hmmm .... several topics:

- then I need a way to tell Eclipse to use these classes only
  if FMJ is enabled. AFAIK this would require two different
  Eclipse environments for SC because Eclipse does not have a way to
  to "conditional" compiling.

- even an "ant rebuild" fails if fmj.jar is not available, thus
  I would classify fmj as a requirement because SC has a hard coded
  dependency on some FMJ specific classes.

Regards,
Werner

<SNI --- SNAP >

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

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

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