Home » Archived » Service Oriented Architecture Tools Platform (STP) » [stp-newsgroup] classes exclusion for runtime version
| [stp-newsgroup] classes exclusion for runtime version [message #373991] |
Mon, 08 May 2006 16:05  |
 keanu
Messages: 49
Registered: July 2009 |
Member |
|
|
This is a multipart message in MIME format.
--=_alternative 0058657449257168_=
Content-Type: text/plain; charset="US-ASCII"
Hi, Antony
I have some questions about runtime only version of b2j
I have found some mismatches.
There are some classes that import B2JPlugin.
However, B2JPlugin is excluded in the runtime version.
If the classes are loaded or called, error will be occurred.
The error will be like "ClassNotDefFoundError" or something like that.
Examples of the classes will be as follows:
-
org.eclipse.stp.b2j.core.jengine.internal.extensions.session transport.tcpip.TCPIPTransportProvider
- org.eclipse.stp.b2j.core.misc.internal.Debugger
- org.eclipse.stp.b2j.core.publicapi.B2JPlatform
- org.eclipse.stp.b2j.core.publicapi.engine.WorkBenchBPELEngin e
- org.eclipse.stp.b2j.core.publicapi.jcompiler.WorkbenchJDTJav aCompiler
Also there are some classes that refer some classes not in the jar files.
So my question is...the classes can be removable? or are they still
needed?
Thank you,
*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
Paik, YoungSang (Keanu)
Advanced Mobile Solution Technology Team in Ubiquitous Computing Lab (UCL)
IBM, Korea
Tel: (822)3781-7509, (8211)898-7509 Email: yspaik@kr.ibm.com
Address : The MMAA Bldg 467-12 Dogok-dong. Gangnam-gu, Seoul, Korea
--=_alternative 0058657449257168_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="Courier New">Hi, Antony</font>
<br>
<br><font size=2 face="Courier New">I have some questions about runtime
only version of b2j</font>
<br><font size=2 face="Courier New">I have found some mismatches.</font>
<br>
<br><font size=2 face="Courier New">There are some classes that import
B2JPlugin.</font>
<br><font size=2 face="Courier New">However, B2JPlugin is excluded in the
runtime version.</font>
<br><font size=2 face="Courier New">If the classes are loaded or called,
error will be occurred. </font>
<br><font size=2 face="Courier New">The error will be like "ClassNotDefFoundError"
or something like that.</font>
<br>
<br><font size=2 face="Courier New">Examples of the classes will be as
follows:</font>
<br><font size=2 face="Courier New">- org.eclipse.stp.b2j.core.jengine.internal.extensions.session transport.tcpip.TCPIPTransportProvider </font>
<br><font size=2 face="Courier New">- org.eclipse.stp.b2j.core.misc.internal.Debugger</font>
<br><font size=2 face="Courier New">- org.eclipse.stp.b2j.core.publicapi.B2JPlatform</font>
<br><font size=2 face="Courier New">- org.eclipse.stp.b2j.core.publicapi.engine.WorkBenchBPELEngin e </font>
<br><font size=2 face="Courier New">- org.eclipse.stp.b2j.core.publicapi.jcompiler.WorkbenchJDTJav aCompiler </font>
<br>
<br><font size=2 face="Courier New">Also there are some classes that refer
some classes not in the jar files.</font>
<br>
<br><font size=2 face="Courier New">So my question is...the classes can
be removable? or are they still needed?</font>
<br>
<br><font size=2 face="Courier New">Thank you, </font>
<br><font size=2 face="sans-serif">*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ <br>
Paik, YoungSang (Keanu)<br>
Advanced Mobile Solution Technology Team in Ubiquitous Computing Lab (UCL)<br>
IBM, Korea<br>
<br>
Tel: (822)3781-7509, (8211)898-7509 Email: yspaik@kr.ibm.com<br>
Address : The MMAA Bldg 467-12 Dogok-dong. Gangnam-gu, Seoul, Korea</font>
--=_alternative 0058657449257168_=--
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #373992 is a reply to message #373991] |
Wed, 10 May 2006 14:18  |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi,
Some of those classes are required and I think some aren't. Are you
actually getting a NoClassDefFoundError or are you just anticipating one?
I know that some of the classes in the current runtime distro of B2J do
import the B2JPlugin but they don't use it in any live code (and so it
doesn't get loaded by the standard Sun JVM). This may not work in other
JVMs, I think in my previous experience it might break in an IBM JVM but
I'm not sure.
The current runtime distro is really a proof of concept. I am currently
looking into removing dependencies on XML libraries and JSSE libraries -
that might take a while and I'll need to get that sorted and working
before I can look at the runtime distro code again. If possible, you
could for now, run with the full B2J jar (I'm assuming your in a
development phase?) and I'll look into those class imports later.
cheers
Antony
YoungSang Paik wrote:
>
> Hi, Antony
>
> I have some questions about runtime only version of b2j
> I have found some mismatches.
>
> There are some classes that import B2JPlugin.
> However, B2JPlugin is excluded in the runtime version.
> If the classes are loaded or called, error will be occurred.
> The error will be like "ClassNotDefFoundError" or something like that.
>
> Examples of the classes will be as follows:
> -
> org.eclipse.stp.b2j.core.jengine.internal.extensions.session transport.tcpip.TCPIPTransportProvider
>
> - org.eclipse.stp.b2j.core.misc.internal.Debugger
> - org.eclipse.stp.b2j.core.publicapi.B2JPlatform
> - org.eclipse.stp.b2j.core.publicapi.engine.WorkBenchBPELEngin e
> - org.eclipse.stp.b2j.core.publicapi.jcompiler.WorkbenchJDTJav aCompiler
>
> Also there are some classes that refer some classes not in the jar files.
>
> So my question is...the classes can be removable? or are they still needed?
>
> Thank you,
> *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
> Paik, YoungSang (Keanu)
> Advanced Mobile Solution Technology Team in Ubiquitous Computing Lab (UCL)
> IBM, Korea
>
> Tel: (822)3781-7509, (8211)898-7509 Email: yspaik@kr.ibm.com
> Address : The MMAA Bldg 467-12 Dogok-dong. Gangnam-gu, Seoul, Korea
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #373993 is a reply to message #373992] |
Wed, 10 May 2006 16:46 |
keanu
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi, Antony
> Some of those classes are required and I think some aren't. Are you
> actually getting a NoClassDefFoundError or are you just anticipating one?
> I know that some of the classes in the current runtime distro of B2J do
> import the B2JPlugin but they don't use it in any live code (and so it
> doesn't get loaded by the standard Sun JVM).
I have run the distro version, and it still works fine with test bpel
scripts. I agree with your opinion. By chance, I extract the jar file,
decompiled the classes in it and tried to recompile them to find out they
can't be recompiled alone. I believe the classes will not be loaded when
SOAPDeamon during runtime. So I was curious why you remain those classes
that are not actually used in runtime. You said below that it was a proof
of concept, so now I understand.
> This may not work in other
> JVMs, I think in my previous experience it might break in an IBM JVM but
> I'm not sure.
Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
my version is
- java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
Only exception I have noticed in b2j is java.io.EOFException with the test
bpel script when I tested with distributed engines. (It is a endurable bug
for now. I know b2j is still developing phase.) But I have not noticed any
"error" messages from VM, not the exception messages from program, during
the test run.
I know some jvm experts here so if some weird messages that are not shown
with Sun VM are detected, I'll let the guys know and do appropriate action.
> The current runtime distro is really a proof of concept. I am currently
> looking into removing dependencies on XML libraries and JSSE libraries -
> that might take a while and I'll need to get that sorted and working
> before I can look at the runtime distro code again. If possible, you
> could for now, run with the full B2J jar (I'm assuming your in a
> development phase?) and I'll look into those class imports later.
Oh, I see. Yes, I am temporarily doing with the full B2J jar on a common
PC. I am transitting from design phase to development phase. Feasibility
is the main activity. Right. Sure, I will wait.
I really appreciate you effort.
Best regards,
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #373994 is a reply to message #373993] |
Thu, 11 May 2006 08:56 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi Keanu,
>> This may not work in other JVMs, I think in my previous experience it
>> might break in an IBM JVM but I'm not sure.
>
> Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
> my version is
> - java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
This was just me remembering an issue from a long time ago. I think
that once upon a time I saw some very subtle difference to do with
classloading but like I say I can't remember exactly what the deal was
(it was complicated). It occurred to me that if you were having
NoClassDefErrors thrown then it could be this issue again but if it
works fine for you on an IBM JVM then I expect it was a different issue.
> Only exception I have noticed in b2j is java.io.EOFException with the
> test bpel script when I tested with distributed engines. (It is a
> endurable bug for now. I know b2j is still developing phase.) But I have
> not noticed any "error" messages from VM, not the exception messages
> from program, during the test run.
That's not so good. Can you tell me what script it is that fails and
email me the EOFException stacktrace please?
Does it only occur with the distributed engine?
> Oh, I see. Yes, I am temporarily doing with the full B2J jar on a common
> PC. I am transitting from design phase to development phase. Feasibility
> is the main activity. Right. Sure, I will wait.
> I really appreciate you effort.
No problem, I am making progress with the conversion to the B2J XML
parser and it seems like it will be feasible to make B2J use it all over
(B2J has turned out to be quite a thorough test of my XML parser and
thrown up a variety of bugs). It adds a total of 16.5K to the jar
(compressed) and would mean (i think) that the only requirement would be
for JSSE libraries, which I should be able to remove just by using
reflection and catching the ClassNotFoundException. These changes (plus
perhaps one or two other ones I expect I have missed) should make B2J
able to run with only 1.3 JVM libraries. Once thats done I will try
running on a Java ME JVM.
thanks
Antony
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #373995 is a reply to message #373994] |
Mon, 15 May 2006 11:44 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi Keanu,
I have converted B2J to use it's own XML parser, got the HTTP
implementation to load JSSE via reflection and removed all 1.4 JVM
library dependencies from B2J core (there were a few odd extra
references such as java.net.URI).
The end result is that the whole of B2J core (including the compilation
stages - given that javac or some other compiler is present) can now run
using:
- IBM WEME 6.1 lnx-x86-ppro10 (which I believe is CDC/FP 1.0?)
- Sun CVM CDC/FP 1.1
Given that it runs on the above IBM WEME JVM it should also run OK on
Sun CVM CDC/FP 1.0 but I haven't been able to build that JVM yet.
I've been able to run almost all of the example BPEL files. In
particular on both JVMs I have successfully run
- test_xpath.bpel
- test_soapserver_pick.bpel
- test_messaging.bpel
I think these constitute a reasonable all-round test. They include use
of HTTP/SOAP, XPATH and heavy threading and synchronisation.
Including the new XML parser and all changes the full core JAR stands at
about 745KB. The runtime only JAR stands at 442KB (but this still
includes the distributed engine).
I plan to do some more thorough testing as one or two of the example
files fail (for reasons which may or may be related to recent changes)
but I don't see any real reason why these changes couldn't go into the
B2J main stream. They don't in any way degrade the performance of B2J
and they make it more flexible in it's requirements.
Are these the right JVMs and CDC/FP specifications you were hoping for?
thanks
Antony
Antony Miguel wrote:
> Hi Keanu,
>
>>> This may not work in other JVMs, I think in my previous experience
>>> it might break in an IBM JVM but I'm not sure.
>>
>>
>> Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
>> my version is
>> - java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
>
>
> This was just me remembering an issue from a long time ago. I think
> that once upon a time I saw some very subtle difference to do with
> classloading but like I say I can't remember exactly what the deal was
> (it was complicated). It occurred to me that if you were having
> NoClassDefErrors thrown then it could be this issue again but if it
> works fine for you on an IBM JVM then I expect it was a different issue.
>
>> Only exception I have noticed in b2j is java.io.EOFException with the
>> test bpel script when I tested with distributed engines. (It is a
>> endurable bug for now. I know b2j is still developing phase.) But I
>> have not noticed any "error" messages from VM, not the exception
>> messages from program, during the test run.
>
>
> That's not so good. Can you tell me what script it is that fails and
> email me the EOFException stacktrace please?
>
> Does it only occur with the distributed engine?
>
>> Oh, I see. Yes, I am temporarily doing with the full B2J jar on a
>> common PC. I am transitting from design phase to development phase.
>> Feasibility is the main activity. Right. Sure, I will wait.
>> I really appreciate you effort.
>
>
> No problem, I am making progress with the conversion to the B2J XML
> parser and it seems like it will be feasible to make B2J use it all over
> (B2J has turned out to be quite a thorough test of my XML parser and
> thrown up a variety of bugs). It adds a total of 16.5K to the jar
> (compressed) and would mean (i think) that the only requirement would be
> for JSSE libraries, which I should be able to remove just by using
> reflection and catching the ClassNotFoundException. These changes (plus
> perhaps one or two other ones I expect I have missed) should make B2J
> able to run with only 1.3 JVM libraries. Once thats done I will try
> running on a Java ME JVM.
>
> thanks
>
> Antony
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #373996 is a reply to message #373995] |
Mon, 15 May 2006 17:24 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi Keanu,
I've written one test class that generates an engine program and saves
it to disk, and another test class that uses just the local engine to
run the compiled program (these would represent your client side BPEL
compilation step and your embedded device BPEL execution step).
I've used these test classes to chop out bits of unused code from the
runtime only JAR including the distributed engine and make sure the
runtime only test program can still run BPEL using only the cut-down JAR.
The resulting runtime only JAR which is still able to run the
precompiled BPEL files I mentioned below (test_xpath, test_messaging,
test_soapserver_pick) is 304KB. This should need no extra libraries to
run on CDC/FP 1.0 or Java 1.3.
cheers
Antony
Antony Miguel wrote:
> Hi Keanu,
>
> I have converted B2J to use it's own XML parser, got the HTTP
> implementation to load JSSE via reflection and removed all 1.4 JVM
> library dependencies from B2J core (there were a few odd extra
> references such as java.net.URI).
>
> The end result is that the whole of B2J core (including the compilation
> stages - given that javac or some other compiler is present) can now run
> using:
>
> - IBM WEME 6.1 lnx-x86-ppro10 (which I believe is CDC/FP 1.0?)
> - Sun CVM CDC/FP 1.1
>
> Given that it runs on the above IBM WEME JVM it should also run OK on
> Sun CVM CDC/FP 1.0 but I haven't been able to build that JVM yet.
>
> I've been able to run almost all of the example BPEL files. In
> particular on both JVMs I have successfully run
>
> - test_xpath.bpel
> - test_soapserver_pick.bpel
> - test_messaging.bpel
>
> I think these constitute a reasonable all-round test. They include use
> of HTTP/SOAP, XPATH and heavy threading and synchronisation.
>
> Including the new XML parser and all changes the full core JAR stands at
> about 745KB. The runtime only JAR stands at 442KB (but this still
> includes the distributed engine).
>
> I plan to do some more thorough testing as one or two of the example
> files fail (for reasons which may or may be related to recent changes)
> but I don't see any real reason why these changes couldn't go into the
> B2J main stream. They don't in any way degrade the performance of B2J
> and they make it more flexible in it's requirements.
>
> Are these the right JVMs and CDC/FP specifications you were hoping for?
>
> thanks
>
> Antony
>
> Antony Miguel wrote:
>
>> Hi Keanu,
>>
>>>> This may not work in other JVMs, I think in my previous experience
>>>> it might break in an IBM JVM but I'm not sure.
>>>
>>>
>>>
>>> Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
>>> my version is
>>> - java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
>>
>>
>>
>> This was just me remembering an issue from a long time ago. I think
>> that once upon a time I saw some very subtle difference to do with
>> classloading but like I say I can't remember exactly what the deal was
>> (it was complicated). It occurred to me that if you were having
>> NoClassDefErrors thrown then it could be this issue again but if it
>> works fine for you on an IBM JVM then I expect it was a different issue.
>>
>>> Only exception I have noticed in b2j is java.io.EOFException with the
>>> test bpel script when I tested with distributed engines. (It is a
>>> endurable bug for now. I know b2j is still developing phase.) But I
>>> have not noticed any "error" messages from VM, not the exception
>>> messages from program, during the test run.
>>
>>
>>
>> That's not so good. Can you tell me what script it is that fails and
>> email me the EOFException stacktrace please?
>>
>> Does it only occur with the distributed engine?
>>
>>> Oh, I see. Yes, I am temporarily doing with the full B2J jar on a
>>> common PC. I am transitting from design phase to development phase.
>>> Feasibility is the main activity. Right. Sure, I will wait.
>>> I really appreciate you effort.
>>
>>
>>
>> No problem, I am making progress with the conversion to the B2J XML
>> parser and it seems like it will be feasible to make B2J use it all
>> over (B2J has turned out to be quite a thorough test of my XML parser
>> and thrown up a variety of bugs). It adds a total of 16.5K to the jar
>> (compressed) and would mean (i think) that the only requirement would
>> be for JSSE libraries, which I should be able to remove just by using
>> reflection and catching the ClassNotFoundException. These changes
>> (plus perhaps one or two other ones I expect I have missed) should
>> make B2J able to run with only 1.3 JVM libraries. Once thats done I
>> will try running on a Java ME JVM.
>>
>> thanks
>>
>> Antony
|
|
| | |
| Re: [stp-newsgroup] classes exclusion for runtime version [message #580560 is a reply to message #373991] |
Wed, 10 May 2006 14:18 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi,
Some of those classes are required and I think some aren't. Are you
actually getting a NoClassDefFoundError or are you just anticipating one?
I know that some of the classes in the current runtime distro of B2J do
import the B2JPlugin but they don't use it in any live code (and so it
doesn't get loaded by the standard Sun JVM). This may not work in other
JVMs, I think in my previous experience it might break in an IBM JVM but
I'm not sure.
The current runtime distro is really a proof of concept. I am currently
looking into removing dependencies on XML libraries and JSSE libraries -
that might take a while and I'll need to get that sorted and working
before I can look at the runtime distro code again. If possible, you
could for now, run with the full B2J jar (I'm assuming your in a
development phase?) and I'll look into those class imports later.
cheers
Antony
YoungSang Paik wrote:
>
> Hi, Antony
>
> I have some questions about runtime only version of b2j
> I have found some mismatches.
>
> There are some classes that import B2JPlugin.
> However, B2JPlugin is excluded in the runtime version.
> If the classes are loaded or called, error will be occurred.
> The error will be like "ClassNotDefFoundError" or something like that.
>
> Examples of the classes will be as follows:
> -
> org.eclipse.stp.b2j.core.jengine.internal.extensions.session transport.tcpip.TCPIPTransportProvider
>
> - org.eclipse.stp.b2j.core.misc.internal.Debugger
> - org.eclipse.stp.b2j.core.publicapi.B2JPlatform
> - org.eclipse.stp.b2j.core.publicapi.engine.WorkBenchBPELEngin e
> - org.eclipse.stp.b2j.core.publicapi.jcompiler.WorkbenchJDTJav aCompiler
>
> Also there are some classes that refer some classes not in the jar files.
>
> So my question is...the classes can be removable? or are they still needed?
>
> Thank you,
> *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+
> Paik, YoungSang (Keanu)
> Advanced Mobile Solution Technology Team in Ubiquitous Computing Lab (UCL)
> IBM, Korea
>
> Tel: (822)3781-7509, (8211)898-7509 Email: yspaik@kr.ibm.com
> Address : The MMAA Bldg 467-12 Dogok-dong. Gangnam-gu, Seoul, Korea
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #580584 is a reply to message #373992] |
Wed, 10 May 2006 16:46 |
keanu
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi, Antony
> Some of those classes are required and I think some aren't. Are you
> actually getting a NoClassDefFoundError or are you just anticipating one?
> I know that some of the classes in the current runtime distro of B2J do
> import the B2JPlugin but they don't use it in any live code (and so it
> doesn't get loaded by the standard Sun JVM).
I have run the distro version, and it still works fine with test bpel
scripts. I agree with your opinion. By chance, I extract the jar file,
decompiled the classes in it and tried to recompile them to find out they
can't be recompiled alone. I believe the classes will not be loaded when
SOAPDeamon during runtime. So I was curious why you remain those classes
that are not actually used in runtime. You said below that it was a proof
of concept, so now I understand.
> This may not work in other
> JVMs, I think in my previous experience it might break in an IBM JVM but
> I'm not sure.
Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
my version is
- java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
Only exception I have noticed in b2j is java.io.EOFException with the test
bpel script when I tested with distributed engines. (It is a endurable bug
for now. I know b2j is still developing phase.) But I have not noticed any
"error" messages from VM, not the exception messages from program, during
the test run.
I know some jvm experts here so if some weird messages that are not shown
with Sun VM are detected, I'll let the guys know and do appropriate action.
> The current runtime distro is really a proof of concept. I am currently
> looking into removing dependencies on XML libraries and JSSE libraries -
> that might take a while and I'll need to get that sorted and working
> before I can look at the runtime distro code again. If possible, you
> could for now, run with the full B2J jar (I'm assuming your in a
> development phase?) and I'll look into those class imports later.
Oh, I see. Yes, I am temporarily doing with the full B2J jar on a common
PC. I am transitting from design phase to development phase. Feasibility
is the main activity. Right. Sure, I will wait.
I really appreciate you effort.
Best regards,
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #580610 is a reply to message #373993] |
Thu, 11 May 2006 08:56 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi Keanu,
>> This may not work in other JVMs, I think in my previous experience it
>> might break in an IBM JVM but I'm not sure.
>
> Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
> my version is
> - java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
This was just me remembering an issue from a long time ago. I think
that once upon a time I saw some very subtle difference to do with
classloading but like I say I can't remember exactly what the deal was
(it was complicated). It occurred to me that if you were having
NoClassDefErrors thrown then it could be this issue again but if it
works fine for you on an IBM JVM then I expect it was a different issue.
> Only exception I have noticed in b2j is java.io.EOFException with the
> test bpel script when I tested with distributed engines. (It is a
> endurable bug for now. I know b2j is still developing phase.) But I have
> not noticed any "error" messages from VM, not the exception messages
> from program, during the test run.
That's not so good. Can you tell me what script it is that fails and
email me the EOFException stacktrace please?
Does it only occur with the distributed engine?
> Oh, I see. Yes, I am temporarily doing with the full B2J jar on a common
> PC. I am transitting from design phase to development phase. Feasibility
> is the main activity. Right. Sure, I will wait.
> I really appreciate you effort.
No problem, I am making progress with the conversion to the B2J XML
parser and it seems like it will be feasible to make B2J use it all over
(B2J has turned out to be quite a thorough test of my XML parser and
thrown up a variety of bugs). It adds a total of 16.5K to the jar
(compressed) and would mean (i think) that the only requirement would be
for JSSE libraries, which I should be able to remove just by using
reflection and catching the ClassNotFoundException. These changes (plus
perhaps one or two other ones I expect I have missed) should make B2J
able to run with only 1.3 JVM libraries. Once thats done I will try
running on a Java ME JVM.
thanks
Antony
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #580625 is a reply to message #373994] |
Mon, 15 May 2006 11:44 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi Keanu,
I have converted B2J to use it's own XML parser, got the HTTP
implementation to load JSSE via reflection and removed all 1.4 JVM
library dependencies from B2J core (there were a few odd extra
references such as java.net.URI).
The end result is that the whole of B2J core (including the compilation
stages - given that javac or some other compiler is present) can now run
using:
- IBM WEME 6.1 lnx-x86-ppro10 (which I believe is CDC/FP 1.0?)
- Sun CVM CDC/FP 1.1
Given that it runs on the above IBM WEME JVM it should also run OK on
Sun CVM CDC/FP 1.0 but I haven't been able to build that JVM yet.
I've been able to run almost all of the example BPEL files. In
particular on both JVMs I have successfully run
- test_xpath.bpel
- test_soapserver_pick.bpel
- test_messaging.bpel
I think these constitute a reasonable all-round test. They include use
of HTTP/SOAP, XPATH and heavy threading and synchronisation.
Including the new XML parser and all changes the full core JAR stands at
about 745KB. The runtime only JAR stands at 442KB (but this still
includes the distributed engine).
I plan to do some more thorough testing as one or two of the example
files fail (for reasons which may or may be related to recent changes)
but I don't see any real reason why these changes couldn't go into the
B2J main stream. They don't in any way degrade the performance of B2J
and they make it more flexible in it's requirements.
Are these the right JVMs and CDC/FP specifications you were hoping for?
thanks
Antony
Antony Miguel wrote:
> Hi Keanu,
>
>>> This may not work in other JVMs, I think in my previous experience
>>> it might break in an IBM JVM but I'm not sure.
>>
>>
>> Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
>> my version is
>> - java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
>
>
> This was just me remembering an issue from a long time ago. I think
> that once upon a time I saw some very subtle difference to do with
> classloading but like I say I can't remember exactly what the deal was
> (it was complicated). It occurred to me that if you were having
> NoClassDefErrors thrown then it could be this issue again but if it
> works fine for you on an IBM JVM then I expect it was a different issue.
>
>> Only exception I have noticed in b2j is java.io.EOFException with the
>> test bpel script when I tested with distributed engines. (It is a
>> endurable bug for now. I know b2j is still developing phase.) But I
>> have not noticed any "error" messages from VM, not the exception
>> messages from program, during the test run.
>
>
> That's not so good. Can you tell me what script it is that fails and
> email me the EOFException stacktrace please?
>
> Does it only occur with the distributed engine?
>
>> Oh, I see. Yes, I am temporarily doing with the full B2J jar on a
>> common PC. I am transitting from design phase to development phase.
>> Feasibility is the main activity. Right. Sure, I will wait.
>> I really appreciate you effort.
>
>
> No problem, I am making progress with the conversion to the B2J XML
> parser and it seems like it will be feasible to make B2J use it all over
> (B2J has turned out to be quite a thorough test of my XML parser and
> thrown up a variety of bugs). It adds a total of 16.5K to the jar
> (compressed) and would mean (i think) that the only requirement would be
> for JSSE libraries, which I should be able to remove just by using
> reflection and catching the ClassNotFoundException. These changes (plus
> perhaps one or two other ones I expect I have missed) should make B2J
> able to run with only 1.3 JVM libraries. Once thats done I will try
> running on a Java ME JVM.
>
> thanks
>
> Antony
|
|
|
| Re: [stp-newsgroup] classes exclusion for runtime version [message #580649 is a reply to message #373995] |
Mon, 15 May 2006 17:24 |
Antony Miguel
Messages: 49
Registered: July 2009 |
Member |
|
|
Hi Keanu,
I've written one test class that generates an engine program and saves
it to disk, and another test class that uses just the local engine to
run the compiled program (these would represent your client side BPEL
compilation step and your embedded device BPEL execution step).
I've used these test classes to chop out bits of unused code from the
runtime only JAR including the distributed engine and make sure the
runtime only test program can still run BPEL using only the cut-down JAR.
The resulting runtime only JAR which is still able to run the
precompiled BPEL files I mentioned below (test_xpath, test_messaging,
test_soapserver_pick) is 304KB. This should need no extra libraries to
run on CDC/FP 1.0 or Java 1.3.
cheers
Antony
Antony Miguel wrote:
> Hi Keanu,
>
> I have converted B2J to use it's own XML parser, got the HTTP
> implementation to load JSSE via reflection and removed all 1.4 JVM
> library dependencies from B2J core (there were a few odd extra
> references such as java.net.URI).
>
> The end result is that the whole of B2J core (including the compilation
> stages - given that javac or some other compiler is present) can now run
> using:
>
> - IBM WEME 6.1 lnx-x86-ppro10 (which I believe is CDC/FP 1.0?)
> - Sun CVM CDC/FP 1.1
>
> Given that it runs on the above IBM WEME JVM it should also run OK on
> Sun CVM CDC/FP 1.0 but I haven't been able to build that JVM yet.
>
> I've been able to run almost all of the example BPEL files. In
> particular on both JVMs I have successfully run
>
> - test_xpath.bpel
> - test_soapserver_pick.bpel
> - test_messaging.bpel
>
> I think these constitute a reasonable all-round test. They include use
> of HTTP/SOAP, XPATH and heavy threading and synchronisation.
>
> Including the new XML parser and all changes the full core JAR stands at
> about 745KB. The runtime only JAR stands at 442KB (but this still
> includes the distributed engine).
>
> I plan to do some more thorough testing as one or two of the example
> files fail (for reasons which may or may be related to recent changes)
> but I don't see any real reason why these changes couldn't go into the
> B2J main stream. They don't in any way degrade the performance of B2J
> and they make it more flexible in it's requirements.
>
> Are these the right JVMs and CDC/FP specifications you were hoping for?
>
> thanks
>
> Antony
>
> Antony Miguel wrote:
>
>> Hi Keanu,
>>
>>>> This may not work in other JVMs, I think in my previous experience
>>>> it might break in an IBM JVM but I'm not sure.
>>>
>>>
>>>
>>> Oh, Really? For me, b2j still works fine with IBM sdk v 1.4.
>>> my version is
>>> - java fullversion "J2RE 1.4.2 IBM Windows 32 build cn142-20050609
>>
>>
>>
>> This was just me remembering an issue from a long time ago. I think
>> that once upon a time I saw some very subtle difference to do with
>> classloading but like I say I can't remember exactly what the deal was
>> (it was complicated). It occurred to me that if you were having
>> NoClassDefErrors thrown then it could be this issue again but if it
>> works fine for you on an IBM JVM then I expect it was a different issue.
>>
>>> Only exception I have noticed in b2j is java.io.EOFException with the
>>> test bpel script when I tested with distributed engines. (It is a
>>> endurable bug for now. I know b2j is still developing phase.) But I
>>> have not noticed any "error" messages from VM, not the exception
>>> messages from program, during the test run.
>>
>>
>>
>> That's not so good. Can you tell me what script it is that fails and
>> email me the EOFException stacktrace please?
>>
>> Does it only occur with the distributed engine?
>>
>>> Oh, I see. Yes, I am temporarily doing with the full B2J jar on a
>>> common PC. I am transitting from design phase to development phase.
>>> Feasibility is the main activity. Right. Sure, I will wait.
>>> I really appreciate you effort.
>>
>>
>>
>> No problem, I am making progress with the conversion to the B2J XML
>> parser and it seems like it will be feasible to make B2J use it all
>> over (B2J has turned out to be quite a thorough test of my XML parser
>> and thrown up a variety of bugs). It adds a total of 16.5K to the jar
>> (compressed) and would mean (i think) that the only requirement would
>> be for JSSE libraries, which I should be able to remove just by using
>> reflection and catching the ClassNotFoundException. These changes
>> (plus perhaps one or two other ones I expect I have missed) should
>> make B2J able to run with only 1.3 JVM libraries. Once thats done I
>> will try running on a Java ME JVM.
>>
>> thanks
>>
>> Antony
|
|
| | |
Goto Forum:
Current Time: Fri Apr 19 22:31:00 GMT 2024
Powered by FUDForum. Page generated in 0.04998 seconds |
] 
Search
Help
Register
Login
Home
