Sounds o.k.

Best regards,

Thomas

Thomas Schaeck
PvC Portal Architect
Pervasive Computing Division
Phone: +49-(0)7031-16-3479   Mobile: +49-(0)171-6928407   e-mail:
[EMAIL PROTECTED]   Fax: +49-(0)7031-16-4888
Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Germany


Ilias Tranganidas <[EMAIL PROTECTED]> on 01.09.2000 09:43:59

Please respond to Ilias Tranganidas <[EMAIL PROTECTED]>

To:   Thomas Schaeck/Germany/IBM@IBMDE
cc:
Subject:  ��: [OCF] Applet distribution




Hi Thomas,
Correct me if I am wrong.
1. The OCF jar files should be installed manually in the appropriate
directories.
2. I am using the PassThruCardService do I need to include it in the jar
file too? My guess is not since it is included in the above mentioned jar
files.

Thanks for the fast response.

Regards,
Ilias

-----������ ������-----
���: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
��������: ���������, 1 ����������� 2000 9:54 ��
����:     Ilias Tranganidas
����:     Re: [OCF] Applet distribution



We implemented several projects were OCF was used by applets running in the
Netscape Browser. You should install the OCF classes, property files and
DLLs in the appropriate browser directories as you described. I recommend
that you bundle the card services you are using with the applet jar file
(which must be signed of course). If you have to fix something in the card
services, you can deploy the fix by simply changing the jar file on the
server.

Best regards,

Thomas

Thomas Schaeck
PvC Portal Architect
Pervasive Computing Division
Phone: +49-(0)7031-16-3479   Mobile: +49-(0)171-6928407   e-mail:
[EMAIL PROTECTED]   Fax: +49-(0)7031-16-4888
Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
Boeblingen, Germany


Ilias Tranganidas <[EMAIL PROTECTED]> on 01.09.2000 08:45:46

Please respond to Ilias Tranganidas <[EMAIL PROTECTED]>

To:   "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
cc:    (bcc: Thomas Schaeck/Germany/IBM)
Subject:  [OCF]  Applet distribution




Hi all,
I have managed to create an applet that works fine on my computer. In my
particular setup I have Java and OCF installed (obviously) and the reader
uses the PC/SC stack plus a dll of its own.

My question is the following:
Since the setup I just described might be very different than the setup of
the average user what steps should I take to ensure that the user's setup
is ready for the task? I will try making a list but I am not sure it is
correct.
1. Setup the particular reader using the manufacturer's installation
procedure so that you get any dlls that are needed. In my case (Towitoko) a
gen_twk.dll is needed to implement the PC/SC migration interface.
2. Setup the PC/SC base components. In my case this can be done after the
first step.
3. Setup OCF in that machine??? Is this needed or should we just copy the
OCF jar files in the appropriate directories of the browser? Keep in mind
that the user may not have java installed at all!
4. Copy dlls and property files to the browser's directories e.g.
.\Netscape\communicator\Program\java\bin and ..\Netscape\Users\user1
5. Bundle the appropriate files along with your classes in the jar file
that you create??? Besides your classes what else is needed?

Obviously I am trying to benefit from the experience of someone that has
done it before. Let's see if I am lucky :)

Regards,
Ilias Tranganidas





---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
!                           [EMAIL PROTECTED]
! containing the word
!                           unsubscribe
! in the body.








---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/

! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
!                           [EMAIL PROTECTED]
! containing the word
!                           unsubscribe
! in the body.

Reply via email to