persistence

My app lets the user select images and then it animates the images. It's a simple thing and I want it to run on 4.2 and onwards. It works perfectly now. The app is supposed to remember the chosen images and let these be default the next time the user runs the app - when the app is restarted. This works beautifully on my Galaxy Nexus (4.2.1) but not so well on my Galaxy S8+ (7.0). Since I love how it works on 4.2.1, it's a bit frustrating that it can't simply run the same on later platforms. This is inside onCreate() : ((ImageButton) findViewById(R.id.imagex)) .setOnClickListener(new View

I have an issue where I have a resource with a new route. When I transition to that new route I create a new object. On the form I have button to cancel, which removes that object. However, if I click a link on my navigation, say going back to the resource index, that object is there with whatever I put in the form. What's the best way of managing creating objects then moving away from the form? My routes: App.Router.map(function() { this.resource('recipes', function() { this.route('new'); this.route('show', { path: '/:recipe_id' }); }); this.resource('styles'); }); App.RecipesNewRoute = Ember

I tested my ejb jpa transactions. I use Container-managed entityManager: @PersistenceContext(unitName = "ParticularUnit") EntityManager em; Such I has got transaction PersistanceContext scope and container manages each transaction. For each instance of pooled session beans, created instance of entityManager. When I mark bean method with @TransactionAttribute(TransactionAttributeType.REQUIRED) and invoke two method within, I expected then method test1 will have another PersitenceContext, but I was surprised, because it was the same. @TransactionAttribute(TransactionAttributeType.REQUIRED)

I got the impression that if we use persistent fields, there is no need for getter methods since the entity manager references the instance variables directly. However, when I removed the getter and setter methods from an entity to have persistent fields, the values for the corresponding instance variable was not retrieved from the database! Does that mean we must have getter and setter methods even though we have persistent fields? If the entity class uses persistence, fields Persistence accesses the entity class instance variables directly at runtime. While on persistence property, there is

As suggested, we're using the following code to retrieve the user document's path NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES); NSString *documentsDirectory = [paths objectAtIndex:0]; we get the following path as as result: /var/mobile/Applications/3E3C1F45-6649-4EA3-93FD-CDB802E346EC/Documents/ In said path, we save all the user's persistent data. We encountered some problem with users who upgraded the application's version from the app-store, the persistent data is no longed read, perhaps the path is changed, maybe a new GUID is used within

I was curious what is considered the better way to manage the reading and writing of a High Score plist file. My High Score class is: @interface HighScore : NSObject <NSCoding> { NSString *name; int score; int level; int round; NSDate *date; } Now, I could do method A, add NSCoding methods: - (void) encodeWithCoder: (NSCoder *) coder { [coder encodeObject: name forKey: kHighScoreNameKey]; [coder encodeInt: score forKey: kHighScoreScoreKey]; [coder encodeInt: level forKey: kHighScoreLevelKey]; [coder encodeInt: round forKey: kHighScoreRoundKey]; [coder encodeObject: date forKey: