Skip to Content
0
Former Member
Jan 15, 2013 at 09:06 AM

compiler exception during deployment since 2.1.3, bapi + relation

13 Views

Hi,

I just updated SUP to 2.1.3 and can't deploy my project anymore (worked with 2.1.0). I have two MBOs BusinessPartner and Opportunities. Both MBOs are in relation. The primary key of BusinessPartner, BP_NUMBER, is mapped as an One-To-Many relation to the load parameters of Opportunities (see picture).

This relation will cause an deployment error with the following exception (see MBO Relation Log.txt):

2013-01-15 09:25:07.270 CONSOLE MMS Thread-209 [com.sybase.sup.server.Console]Note: Recompile with -Xlint:unchecked for details.

2013-01-15 09:25:07.270 CONSOLE MMS Thread-209 [com.sybase.sup.server.Console]Note: Some input files use unchecked or unsafe operations.

2013-01-15 09:25:07.270 CONSOLE MMS Thread-209 [com.sybase.sup.server.Console]^

2013-01-15 09:25:07.270 CONSOLE MMS Thread-209 [com.sybase.sup.server.Console]$tmpBU_PARTNER_5 = INPUT.BU_PARTNER;

2013-01-15 09:25:07.270 CONSOLE MMS Thread-209 [com.sybase.sup.server.Console]location: class BPCNewMobile.server.Opportunity

2013-01-15 09:25:07.270 CONSOLE MMS Thread-209 [com.sybase.sup.server.Console]symbol : variable INPUT

If I delete the relation, it will deploy. This relation did work in 2.1.0 though.

Any thoughts?

Thanks,

Christian

Attachments

relation.jpg (107.1 kB)