Compiling applications which access referencepartitions

Question

Hi,
in our project we have two server applications (lets call them ServApp1 and
ServApp2): ServApp2 partitions are compiled, installed on an Unix box and
are configured as reference partitions to ServApp1 (which in turn is
installed on an NT box); in ServApp2 we access C wrapped libraries and the
DB while ServApp1 is basically a frontend IIOP listener.
When we use ServApp1 in interpreted mode everything works fine, but when we
try to compile it we get compile errors saying that the compiler does not
manage to find the libraries used by ServApp2.
Now, those libraries are only used by ServApp2 and their plans are not in
the supplier plan list of ServApp1; in addition, looking at the C++ classes
generated for ServApp1 we found that the code generator included code
relative to the services included in ServApp2 (even DB services).
By the way, we have the same behaviour if we try to install and compile
ServApp1 on an Unix box different from the one used by ServApp2.
Do you think this is normal or is there any particular way to avoid it we
might have overlooked?
Thanks a lot for your cooperation
Ernesto Moscatelli
SEMAGROUP Italy
PS: we use Forte' Rel. 3.0.j
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

Answer 1

Hi Ernesto,
I understand your problem, When you deploy your Fort&eacute; application you decide
the right partitioning schema, as an example Partition Server1 and Server2
and you think that you will have in Server 1 just the code useful for the
object running in that patition.
Unfortunately that is not the reality, doesn't matter if you use or not use
a reference partition when you use services from a service object.
The thing that you have to understand is the Fort&eacute; supplier plan management.
In your concrete deployment you have two partition ServApp1 & ServApp2, in
order to reference a service object in ServApp2 from ServApp1 you must have
defined the project that contains this SO as supplier plan of the caller
project in ServAPP1.
By doing that, at deployment time, Fort&eacute; wil put in your ServAPP1 partition
the definition of the project that you reference from ServAPP2 and all the
inheritance chain of supplier plan indirectly referenced by that project.
That the reason why you see all the code related to ServAPP2 in your
ServAPP1 deployment.
You can avoid that by breaking the Supplier Plan Chain appllying a Design
Pattern.
If you want more detail about the pattern you can contact me and we will be
able to speak directly in Italian.
Hope this help,
Cheers, Max.
Massimiliano Delsante
Object Technology Manager
O.T. Consulting S.r.l
Via della Previdenza Sociale N&deg; 11
42100 Reggio Emilia
Tel : [phone]
Fax : [phone]
Mobile : [phone]
www.otconsulting.com
-----Messaggio originale-----
Da: [email protected] <[email protected]>
A: [email protected] <[email protected]>
Data: venerd&igrave; 23 aprile 1999 10.54
Oggetto: Compiling applications which access reference partitions
Hi,
in our project we have two server applications (lets call them ServApp1 and
ServApp2): ServApp2 partitions are compiled, installed on an Unix box and
are configured as reference partitions to ServApp1 (which in turn is
installed on an NT box); in ServApp2 we access C wrapped libraries and the
DB while ServApp1 is basically a frontend IIOP listener.
When we use ServApp1 in interpreted mode everything works fine, but when we
try to compile it we get compile errors saying that the compiler does not
manage to find the libraries used by ServApp2.
Now, those libraries are only used by ServApp2 and their plans are not in
the supplier plan list of ServApp1; in addition, looking at the C++ classes
generated for ServApp1 we found that the code generator included code
relative to the services included in ServApp2 (even DB services).
By the way, we have the same behaviour if we try to install and compile
ServApp1 on an Unix box different from the one used by ServApp2.
Do you think this is normal or is there any particular way to avoid it we
might have overlooked?
Thanks a lot for your cooperation
Ernesto Moscatelli
SEMAGROUP Italy
PS: we use Forte' Rel. 3.0.j
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
To unsubscribe, email '[email protected]' with
'unsubscribe forte-users' as the body of the message.
Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>