Closed GoogleCodeExporter closed 9 years ago
This is a clear bug and will be fixed asap. For now, you can use a workaround
which will fix the problem. Instead of calling Permissions.initialize(this,
manager), call
Permissions p = new Permissions(this, manager);
this.getContext().addTransactionListener(p);
p.transactionStart(this, null);
Original comment by kimp...@gmail.com
on 7 Jan 2011 at 2:57
Thank you for your fast answer. Your workaround works perfectly.
Jachen.
Original comment by jbrechbu...@gmail.com
on 7 Jan 2011 at 4:52
I'm unable to reproduce the problem, from where does the NullPointerException
originate? The transactionStart method only sets the "instance" variable to
"this" and that is already done in the constructor, so this shouldn't be a
problem.
Original comment by kimp...@gmail.com
on 10 Jan 2011 at 6:41
Ok I understood. My version of AppFoundation is too old, this bug was
previously fixed.
My Permissions class constructor:
public Permissions(Application application, PermissionManager manager) {
if (application == null) {
throw new IllegalArgumentException("Application must be set");
}
if (manager == null) {
throw new IllegalArgumentException("PermissionManager must be set");
}
this.application = application;
pm = manager;
}
The current Permissions constructor :
public Permissions(Application application, PermissionManager manager) {
if (application == null) {
throw new IllegalArgumentException("Application must be set");
}
if (manager == null) {
throw new IllegalArgumentException("PermissionManager must be set");
}
instance.set(this);
this.application = application;
pm = manager;
}
I just have to update to the lastest version of AppFoundation.
Sorry to have you wasting your time.
Thank you for all.
Jach.
Original comment by jbrechbu...@gmail.com
on 10 Jan 2011 at 8:40
No problem :)
Original comment by kimp...@gmail.com
on 10 Jan 2011 at 10:47
Original issue reported on code.google.com by
jbrechbu...@gmail.com
on 7 Jan 2011 at 1:30