[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-users] Can't deploy when using LAZY, can deply when using EAGER
Hi Tom,

I've added the nested jar to the classpath of the static weaver (both to the -cp and to the -classpath parameter, just to be sure). No luck - I still get a corrupted jar.
By "corrupted", I mean that each folder that has .class files also has an empty entry (0K, no name). The domain classes are about twice the size, and they do implement the interfaces:
org.eclipse.persistence.internal.weaving.PersistenceWeaved,
org.eclipse.persistence.internal.descriptors.PersistenceEntity,
org.eclipse.persistence.internal.descriptors.PersistenceObject,
org.eclipse.persistence.queries.FetchGroupTracker,
org.eclipse.persistence.internal.weaving.PersistenceWeavedFetchGroups,
org.eclipse.persistence.descriptors.changetracking.ChangeTracker,
org.eclipse.persistence.internal.weaving.PersistenceWeavedChangeTracking

The domain classes are:
il/co/beeriprint/ebill/bo/BeeriprintCustomer.java
il/co/beeriprint/ebill/bo/DefaultingBeeriprintCustomer.java
il/co/beeriprint/ebill/bo/EBillEndpoint.java
il/co/beeriprint/ebill/bo/ImportRecord.java
il/co/beeriprint/ebill/bo/Passcode.java
il/co/beeriprint/ebill/bo/SendBatch.java
il/co/beeriprint/ebill/bo/StatementPartRecord.java
il/co/beeriprint/ebill/bo/StatementRecord.java
il/co/beeriprint/ebill/bpcustomer/cellcom/dataimport/compensation/CellcomEndpointKeyCR.java
il/co/beeriprint/ebill/bpcustomer/cellcom/dataimport/endpoint/CellcomEndpointKey.java
il/co/beeriprint/ebill/bpcustomer/leumicard/dataimport/compensation/EndpointKeyCR.java
il/co/beeriprint/ebill/bpcustomer/leumicard/dataimport/endpoint/LeumicardCreditCardNum.java
il/co/beeriprint/ebill/bpcustomer/leumicard/dataimport/endpoint/LeumicardEndpointKey.java
il/co/beeriprint/ebill/bpcustomer/leumicard/dataimport/endpoint/LeumicardIdNum.java
il/co/beeriprint/ebill/bpcustomer/leumicard/dataimport/endpoint/SeparateEndpointKey.java
il/co/beeriprint/ebill/bpcustomer/leumicard/dataimport/endpoint/UnifiedEndpointKey.java
il/co/beeriprint/ebill/dataimport/compensation/CompensatableReference.java
il/co/beeriprint/ebill/dataimport/compensation/EBillEndpointCR.java
il/co/beeriprint/ebill/dataimport/compensation/ImportRecordCR.java
il/co/beeriprint/ebill/dataimport/compensation/PasscodeCR.java
il/co/beeriprint/ebill/dataimport/compensation/SendBatchCR.java
il/co/beeriprint/ebill/dataimport/compensation/StatementPartRecordCR.java
il/co/beeriprint/ebill/dataimport/compensation/StatementRecordCR.java
il/co/beeriprint/ebill/email/impl/ejbmailer/dsnbehaviour/DefaultBehaviour.java
il/co/beeriprint/ebill/email/impl/ejbmailer/dsnbehaviour/DsnCodeBehaviour.java
il/co/beeriprint/ebill/email/impl/ejbmailer/dsnbehaviour/EsmtpCodeBehaviour.java
il/co/beeriprint/ebill/email/impl/ejbmailer/dsnbehaviour/SmtpCodeBehaviour.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/EJBMailerEMailMessage.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/DeliveryFailure.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/Expired.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/PermanentFailure.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/Queued.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/ServiceMessageQueued.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/StatementPartMessageHistoryItem.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/TransientFailure.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/history/Viewed.java
il/co/beeriprint/ebill/email/impl/ejbmailer/entity/StoredEMailMessage.java
il/co/beeriprint/ebill/email/templates/EMailResource.java
il/co/beeriprint/ebill/email/templates/EMailResourceBundle.java
il/co/beeriprint/ebill/email/templates/EMailTemplate.java
il/co/beeriprint/ebill/pdfchopshop/serverside/PdfResourceRecord.java
il/co/beeriprint/ebill/serversettings/CustomerSettingRecord.java
il/co/beeriprint/ebill/serversettings/SystemSettingRecord.java

As you can see, not the most trivial case...
I've added a new field to an entity class today (EJBMailerEMailMessage) and now the application won't deploy again, basically saying the same thing (missing _persistence_set* method) on some other class that was not in my original post. I'm stumped as I need to release a version soon, and eclipselink does solve a few problems I had before.
I know there's an Oracle dev center in Israel - do they have any specialist that can have a hands-on look at this? Obviously, the solution will be posed to the list.

Michael