Java Applet support with JFS, How?
Hi All,
I'm trying to add a java Applet to a page supplied as part of an extension Plug In built on top of JFS.
A simple applet implementation would take object name and (optionally) server side folder location, however, JFS is an application thus most of its folders are internal and can't be accessed by clients.
does anyone know how to implement it with a JFS server? where the applet object should be located on the server side and how the client should refer to it?
thanks in advance,
Itai Shimron
RCAM development team
Rational Rhapsody development team
I'm trying to add a java Applet to a page supplied as part of an extension Plug In built on top of JFS.
A simple applet implementation would take object name and (optionally) server side folder location, however, JFS is an application thus most of its folders are internal and can't be accessed by clients.
does anyone know how to implement it with a JFS server? where the applet object should be located on the server side and how the client should refer to it?
thanks in advance,
Itai Shimron
RCAM development team
Rational Rhapsody development team
3 answers
OK, I figure it out and here are the details:
1. I exported Java object into a class
2. the class was located in one on the plugIn packages so its internal location was added to the file. something like:
package com.ibm.rational.carter.publish;
3. once the client browser found the file (by using the <APPLET> tag), it couldn't resolve this package information and loading the applet failed.
I solved it by moving the java file to the root folder of the plugIn and then export it to a class. Now it didn't contain internal package information and the client browser was able to load it.
This problem has nothing to do with JFS that allows accessing existing folders under pre defined alias names.
example:
<extension>
<alias>
</alias>
thank you all who spent time trying to figure out my question. Hope my solution will help others.
regards,
Itai
1. I exported Java object into a class
2. the class was located in one on the plugIn packages so its internal location was added to the file. something like:
package com.ibm.rational.carter.publish;
3. once the client browser found the file (by using the <APPLET> tag), it couldn't resolve this package information and loading the applet failed.
I solved it by moving the java file to the root folder of the plugIn and then export it to a class. Now it didn't contain internal package information and the client browser was able to load it.
This problem has nothing to do with JFS that allows accessing existing folders under pre defined alias names.
example:
<extension>
<alias>
</alias>
thank you all who spent time trying to figure out my question. Hope my solution will help others.
regards,
Itai
Hi All, ...
OK, I figure it out and here are the details:
1. I exported Java object into a class
2. the class was located in one on the plugIn packages so its internal location was added to the file. something like:
package com.ibm.rational.carter.publish;
3. once the client browser found the file (by using the <APPLET> tag), it couldn't resolve this package information and loading the applet failed.
I solved it by moving the java file to the root folder of the plugIn and then export it to a class. Now it didn't contain internal package information and the client browser was able to load it.
This problem has nothing to do with JFS that allows accessing existing folders under pre defined alias names.
example:
<extension>
<alias>
</alias>
thank you all who spent time trying to figure out my question. Hope my solution will help others.
regards,
Itai
Hi All, ...
Thanks Itai,
I was looking for a way to make this work.
Regards
Nita
where is the root file of the plugin located
OK, I figure it out and here are the details:
1. I exported Java object into a class
2. the class was located in one on the plugIn packages so its internal location was added to the file. something like:
package com.ibm.rational.carter.publish;
3. once the client browser found the file (by using the <APPLET> tag), it couldn't resolve this package information and loading the applet failed.
I solved it by moving the java file to the root folder of the plugIn and then export it to a class. Now it didn't contain internal package information and the client browser was able to load it.
This problem has nothing to do with JFS that allows accessing existing folders under pre defined alias names.
example:
wwwwwww