Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Strange weaving message at startup
Strange weaving message at startup [message #1010150] Sat, 16 February 2013 17:49 Go to next message
jm collin is currently offline jm collinFriend
Messages: 7
Registered: February 2013
Junior Member
Hello,

I'm using EclipseLink 2.4.0 with MongoDB 2.2 in a JBoss 7.1.1 application server.
At deployement I always see this message :
18:41:23,244 INFO  [org.eclipse.persistence.weaver] (MSC service thread 1-1) Class xxx.entities.Account could not be weaved for change tracking as it is not supported by its mappings.


I wonder what it means and what is the problem with this 'simple' Entity class.
Maybe you can explain this message and help me to find if there is any consequences.

My class is the following :
@Entity
@NoSql(dataType="account", dataFormat=DataFormatType.MAPPED)
@Table(uniqueConstraints = @UniqueConstraint(columnNames = "email"))
public class Account extends JPAMongoBaseEntity {
	@Id
	@Field(name="_id")
	@GeneratedValue
	private String id;
	
	@Override
	public String getId() { return id;};
	public void setId(String id) { this.id = id;};
	
	// Must be unique (id fonc)
	@NotNull
	@Size(min = 1, max = 256)
	@Email
	@Field(name="email")
	private String email;
	
	@NotNull
	@Size(min = 3, max = 50)
	@Field(name="pseudo")
	private String pseudo;
	
	@Field(name="password")
	private String password;
	
	// the time of end of password validity (-1 => infinite validity)
	@Field(name="timeEndOfPwdValidity")
	private long timeEndOfPwdValidity;
	
	// the time of last access to compte
	@Field(name="timeLastAccess")
	private long timeLastAccess;
	
	// Account has been activated (ie the user clicks on the link to activate the account)
	@Field(name="activated")
	private boolean activated;
	// The account is enabled by admin (ie. the user can log in)
	@Field(name="enabled")
	private boolean enabled;
	
	// The account type
	@Field(name="type")
	private EnumAccountType type;
	// If account is TRIAL, this field give the date/time limit of TRIAL
	@Field(name="timeEndOfTrial")
	private long timeEndOfTrial;
	
	// Administratives informations
	@Size(min = 2, max = 50)
	@Field(name="firstName")
	private String firstName=null;
	@Size(min = 2, max = 50)
	@Field(name="lastName")
	private String lastName=null;
	@Size(min = 2, max = 50)
	@Field(name="company")
	private String company=null;
	@Size(min = 1, max = 50)
	@Field(name="branch")
	private String branch=null;
	
	// The account balance
	@Field(name="balance")
	private int balance=0;
	
	// Embedded. The list of account.id that are attached to this account
	@ElementCollection
	@Field(name="attachments")
	private List<String> attachments = new ArrayList<String>();
	
	// Relations
	// The payer account if this account's bills is payed by another payer account
	@Field(name="payerAccountId")
	private String payerAccountId=null;
}


Thank's in advance.
Re: Strange weaving message at startup [message #1014990 is a reply to message #1010150] Wed, 27 February 2013 07:25 Go to previous messageGo to next message
jm collin is currently offline jm collinFriend
Messages: 7
Registered: February 2013
Junior Member
I still have this message and strange behaviour at runtime (@OneToMany relation seems to not function correctly). Can someone explain why this message and consequences. Thank's.
Re: Strange weaving message at startup [message #1015016 is a reply to message #1014990] Wed, 27 February 2013 08:22 Go to previous messageGo to next message
Renso Lohuis is currently offline Renso LohuisFriend
Messages: 44
Registered: July 2012
Member
I don't know much about it myself, but you might find the answer in the following post:
http://www.eclipse.org/forums/index.php/m/772640/
Re: Strange weaving message at startup [message #1016227 is a reply to message #1015016] Tue, 05 March 2013 14:50 Go to previous message
James Sutherland is currently offline James SutherlandFriend
Messages: 1939
Registered: July 2009
Location: Ottawa, Canada
Senior Member

This is just a warning, it means deferred change tracking will be used (deferred is a little less efficient, but should work the same).

It occurs because attribute change tracking is not support for NoSQL ElementCollection mappings.


James : Wiki : Book : Blog : Twitter
Previous Topic:Is here the way to regulate result of query to child tables of an entity.
Next Topic:History for OneToMany relationship with JoinColumn
Goto Forum:
  


Current Time: Thu Dec 18 18:36:30 GMT 2014

Powered by FUDForum. Page generated in 0.02565 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software