Magma December 2007

magma@lists.squeakfoundation.org

12 participants
13 discussions

Magma and package universe
by Norbert Hartl 23 Dec '07

23 Dec '07

Hi, one year after trying magma the last time I give it another try. In the meantime there is package universe which seems to ease the installation of necessary parts. But I'm a little confused. I read about Keith' seaside helper. There is a another magma seaside package provided by Chris. The package from Keith is not using the one from Chris. There is Magma-Seaside and Magma-Seaside-alpha. The alpha package depends on Seaside-beta which is not available any- more. If I'm right the Seaside 2.8 was seaside-beta until it became stable, right? So what to use? thanks, Norbert

2 1

Lava SQL and JDBC driver
by Aaron Rosenzweig 23 Dec '07

23 Dec '07

Hi Brent and everyone, I'm just starting to read about Magma and the Lava SQL abstraction layer. Is there a JDBC driver for it so that it could "pretend" to be just any other relational database for WebObjects, Brio Query, and whatnot? I'm still coming to grips with new ways of thinking. Seems like this Lava SQL abstraction layer is a brilliant solution to allow more people to move to an object database but still support other departments' tools of choice for accessing the data. Thank you, -- Aaron

2 1

r41Alpha3
by Chris Muller 18 Dec '07

18 Dec '07

I've just posted r41Alpha3 to the "MagmaTester" project of SqueakSource. Most notable is the inclusion of sig's MaDictionary redesign. Thanks Igor! The test cases pass with them but I haven't done anything more at this point. Proceed with caution, just in case. Also included is a good bug fix for renaming classes. Magma was being notified of the rename, but needed to rehash two of its internal Dictionary's to ensure subsequent access is correct. There are other minor improvements.

1 0

Tutorial
by Keith Hodges 15 Dec '07

15 Dec '07

There have been calls for a Magma tutorial to go into the Seaside tutorial in the persistency chapter. This chapter already includes Glorp and GOODS. Just in case someone is already, or thinking of doing this, I have already written such a mini tutorial. In order to make Magma even easier to use, I have begun rewriting "Magma seaside" to take advantage of my new Seaside Session Helpers interface, which I released yesterday. The idea being that you can now use Magma, without a specialized Seaside Session class. This should make it easier for users to adopt Magma for their existing applications. I am a little unsure as to how you are supposed to obtain an exact match of a unique item from the database. This is how I would do it (althought I know MagmaCollections dont actually implement #firstOrNil) ^ (self users where: [ :each | each email = anEmail ]) firstOrNil Is there a better way to obtain a unique value? cheers Keith p.s. the wiki page that I refer to on MagmaCollections is a bit out of date. ---- so far... *Saving all data in an object-oriented database: Magma* Another option to make your data persistent is to use an object-oriented database like Magma. *Installing the Magma Database* Magma is written entirely in Squeak, so there is no need to install a separate server application. Both Magma and Seaside can run in the same image. To install (into a 3.10 based image) just execute the following. (This may take a while) Installer universes install: 'Magma seasideHelper'. * Configuring your application to use Magma* In the configuration for the 'todo' application you will need to add WAMagmaConfiguration to the configuration "ancestry". Select it from the drop down menu and click "Add". As soon as you do this, a new group of configuration options will appear. You will need to select the "WAMagma", helper class from the drop down menu. The WAMagma class provides the basic interface between Magma Sessions and Seaside Sessions. Subclasses provide specialised session management such as shared or pooled sessions. *Using Magma* Magma is very easy to use with seaside. To obtain and use a database session helper, simply send #magma to the current session. For example the code "self session magma" will work within all seaside components. To use Magma in this application in a similar manner to the way we have connected to databases in other examples we need to create an interfacing class, to which we can add our specialized querying methods. Dictionary subclass: #StMagmaDatabase instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'STTutTodoApp' StSession-#initialize super initialize. self db: (self magma rootAs: StMagmaDatabase) The tutorial application accesses the database via the #db accessor. Here we define this using the #rootAs: helper method, which does everything we need, both to initialize the database, and to provide us the interface that we want to it. To initialize our users collection we define the initialization on our root object, and we need a method to return the users from the database, to add a new user, and to find a user. StMagmaDatabase-#initialize | users | users := OrderedCollection new. self at: #users put: users. StMagmaDatabase-#users ^ self at: #users StMagmaDatabase-#addUser: newUser ^ self users add: newUser StMagmaDatabase-#findUserByEmail: anEmail ^ self users detect: [:each | each email = anEmail] ifNone:[] Notice how for basic usage we have not needed any database specific code! If our userbase is going to grow to a significant size it makes sense to re implement the above using some database features, so we introduce a MagmaCollection which you can read about in detail here: http://wiki.squeak.org/squeak/2639 initialize | users | users := MagmaCollection new. users addIndex: (MaSearchStringIndex attribute: #userName) beAscii. users addIndex: (MaSearchStringIndex attribute: #email) beAscii. self at: #users put: users StMagmaDatabase-#users ^ self at: #users StMagmaDatabase-#addUser: newUser ^ self users add: newUser StMagmaDatabase-#findUserByEmail: anEmail ^ (self users where: [ :each | each email = anEmail ]) firstOrNil ... need to explain how committing works... etc

7 29

Re: MessageNotUnderstood: MaMalformedRequestError>>repositoryController:
by Chris Muller 14 Dec '07

14 Dec '07

> I don't see yet why this is happening with this specific object. In your client, put a halt in the MaTcpRequestServerLink>>#getByteArrayResponseFor: aMaServerRequest. When it halts explore that aMaServerRequest to verify you do indeed have IFILevelCollection in there somewhere (exploring all the way down, if necessary). We need to trace back why/how you are putting this in the request, because the generic Magma Server knows nothing of IFILevelCollection's. That's why it is signaling a MalformedRequest. - Chris On Dec 14, 2007 5:09 AM, Hilaire Fernandes <hilaire(a)ofset.org> wrote: > 2007/12/14, Chris Muller <asqueaker(a)gmail.com>: > > Hi Hilaire, for whatever class you are getting "id not found" look in > > your client at this path: > > > > theMagmaSession > > link > > serializer > > classIdManager > > classesById > > > > In 'classesById' look for the id of the class the server image is > > claiming is not found. THAT is the class of the object that is > > causing the problem. > > > > Is that the IFICompetencyCollection ? What is IFICompetencyCollection ? > > Ok, in the server side I have to put a halt in the following message > to get the missing class ID, otherwise the error message in the server > is not helpful as the ID is not provided at this moment. Not sure if > you can have the ID shipped in the error message object, it will be > helpful: > > classDefinitionsForId: anInteger > ^ self > classDefinitionsForId: anInteger > ifAbsent: [self halt. MaObjectSerializationSoftwareError signal: > 'class-definition not found' ] > > Now I see my missing id is 206, and it is an IFILevelCollection, a > subclass of OrderedCollection. > This class is also present in the server image, but I guess there is > no relation. > This class is very simple, only with methods addLast: and findLevelWith: > > I don't see yet why this is happening with this specific object. > > > Regards, > > Chris > > > > On Dec 12, 2007 6:26 AM, Hilaire Fernandes <hilaire(a)ofset.org> wrote: > > > Thanks for your advices, it is helpful. > > > > > > In this place of the application I am not using read strategy. > > > In other place of the application where I am suing read strategy I don't > > > have the problem, so may be it is a problem underneath. > > > > > > In the Magma client I only have the modification to > > > StrikeFont>>maAsStorageObject so TextMorph are persisted correctly. I > > > apply this change both to client and server : > > > > > > StrikeFont>>maAsStorageObject > > > ^ DiskProxy > > > global: #StrikeFont selector: #familyName:pointSize:emphasized: > > > args: { self familyName. self pointSize. self emphasis } > > > > > > > > > Chris, I went until the MaTcp...>>submit: method, but I don't really > > > understand where to look. > > > > > > From the MaCommitPackage, the MagmaCollectionChanges looks like: > > > > > > collectionOid: 4112481 > > > changes: a Dictionary(#added->an IdentityDictionary(66543->an > > > OrderedCollection(#(250776336) #(0) #(10625597) an IFILevelCollection() > > > #(1)) ) #removed->an IdentityDictionary() ) > > > isNewCollection: false > > > collection: a MagmaCollection > > > > > > > > > The problem happens when I add an object to a MagmaCollection > > > > > > IFIDbSession commit: [pedagogicalMoments add: moment] > > > > > > In this commit, TextMorph persitency occurs. > > > I repeat this code is working when Magma is in local mode. > > > > > > > > > In the client, MagmaRepositoryController basicNew protocol > > > returns, where only IFICompetencyCollection is new (the server has the > > > same protocol size): > > > > > > {LargePositiveInteger . MaSerializedGraphBuffer . MaByteObjectBuffer . > > > MaVariableWordBuffer . MaVariableObjectBuffer . MaFixedObjectBuffer . > > > MaStorageObjectBuffer . MaVariableBuffer . > > > MaLargeCollectionSegmentRequest . MaLoadProgressRequest . > > > MaRefreshSegmentRequest . MaDownloadCodeRequest . > > > MaLoadFromReaderRequest . MaReaderTrunkRequest . > > > MaAbortTransactionRequest . MaRepositoryConnectionRequest . > > > MaWriteRequest . MagmaPathNameRequest . MaCloseRepositoryRequest . > > > MaLargeCollectionSizeRequest . MaAbstractReadRequest . > > > MaTransactionRequest . MagmaIdRequest . MaAnchorRequest . > > > MaReadRequest . MaKeyIntervalInfoRequest . MaSegmentByIndexRequest . > > > MaRepositoryDisconnectRequest . MaCommitPackage . MaBasicReadStrategy . > > > MaReadStrategy . MagmaCollectionSegment . MaRefreshViewResult . > > > MaReadResult . MagmaLargeCollectionSegment . MaCommitResult . > > > MagmaCollectionReaderSegment . MaFailedCommitResult . MagmaId . UUID . > > > MaFailedCommitResult . MagmaClientConnection . MagmaCommitConflict . > > > Fraction . MaClause . MaExpression . MaQueryTrunkClause . MaQueryTrunk . > > > MagmaSet . IFICompetencyCollection . MagmaCollection . > > > IdentityDictionary . MagmaIndexDescription . MagmaArrayChanges . > > > MagmaCollectionChanges . Association . MaChangedKeySpecification . > > > MaEnvironmentError . MaObjectSerializationUserError . > > > MaUnreadableRecoveryRecord . MagmaEquivalentObjectNotInCollection . > > > MagmaSoftwareError . MaNetworkError . MagmaSessionLost . > > > MagmaEnvironmentError . MaObjectSerializationSecurityViolation . > > > MaHashIndexUserError . MagmaUserError . MagmaInvalidIndexObject . > > > MagmaCommitError . MaClientServerUserError . MagmaCorruptionError . > > > MaSecurityViolation . MagmaGarbageCollectedObject . > > > MagmaDuplicateObjectInCollection . MaSoftwareError . MaCorruptionError . > > > MagmaInvalidOid . MaUserError . MaMalformedRequestError . > > > MaObjectSerializationSoftwareError . MaSpecialCollectionsSoftwareError} > > > > > > Le mardi 11 décembre 2007 à 23:06 -0500, Chris Muller a écrit : > > > > > > > Hi Hilaire, a the MalformedRequest error is telling you the server > > > > received a request from your client that it could not properly > > > > materialize. Specifically, it looks like your Magma client has > > > > attempted to extend the Magma #protocol ("class id not found"). Are > > > > you running a modified Magma client? > > > > > > > > It does look like the error-handling code incorrectly passes the > > > > MalformedRequestError Exception AS the request which is, of course, a > > > > bug. I will fix that, so that it kick the error back to your client > > > > as it should. > > > > > > > > But I know you are interested in the cause of the error itself. When > > > > you get this error, you should break into your client and look in teh > > > > debugger at the request it passed to the server. Look at ALL the > > > > arguments and find which object whose class is not included in this > > > > Array: > > > > > > > > MagmaRepositoryController basicNew protocol > > > > > > > > THAT is the one that is causing the problem. > > > > > > > > - Chris > > > > > > _______________________________________________ > > > Magma mailing list > > > Magma(a)lists.squeakfoundation.org > > > http://lists.squeakfoundation.org/mailman/listinfo/magma > > > > > > > > > > > -- > http://blog.ofset.org/hilaire > Smalltalkers do: [:it | All with: Class, (And love: it)] >

1 0

MessageNotUnderstood: MaMalformedRequestError>>repositoryController:
by Hilaire Fernandes 14 Dec '07

14 Dec '07

With r40, on the server side, I have this error, which I don't understand (error log enclosed) Hilaire

3 5

Deleting the database
by Keith Hodges 12 Dec '07

12 Dec '07

I am trying the following but it doesnt work for me [ self location delete ] on: MagmaDeleteWarning do: [ :ex | ex resume: true ]. Keith

2 1

[bug] MagmaCollection new asOrderedCollection
by Keith Hodges 12 Dec '07

12 Dec '07

returns an OrderedCollection( aMagmaCollection ) (fixed in magma seasideHelper) Keith

2 1

[bug] MaObjectFiler-open
by Keith Hodges 11 Dec '07

11 Dec '07

If no directory is present an InvalidDirectory error is raised. Name: Magma server-kph.235 Author: kph Time: 11 December 2007, 5:23:32 pm UUID: ccdb80d5-a80d-11dc-abc2-000a95edb42a Ancestors: Magma server-cmm.234 fix to MaObjectFiler-open Keith

1 0

Exploring once more
by Keith Hodges 10 Dec '07

10 Dec '07

Dear Chris, Long ago I was puzzled about this comment in the repository: Name: Ma proxy support-cmm.30 Author: cmm Time: 16 July 2007, 9:54:02 pm UUID: 771174c7-a9ef-a641-948b-6f2108e86d9d Ancestors: Ma proxy support-cmm.26, Ma proxy support-kph.29 - Merged Keith Hodges changes for MagmaMutatingProxy's to initially display in explorers indicated as a proxy (even though it still mutates just as soon). This is very useful for seeing how far the ReadStrategy went. Thanks Keith! Essentially you were saying that exploring, for which my submitted changes were intended, was not working. However it was working fine for me, in Gjallar (Squeak 3.8) So imagine my annoyance when I discover that in Squeak 3.10 your comment above makes sense. i.e. it does not work at all! After investigation it appears that the culprit is the preference #visualExplorer! The visual explorer's attempt to obtain an icon from the Proxy reifies the proxy before you get a chance to view it in the explorer at all. So as an initial workaround we can disable the #visualExplorer preference. I will post a proper fix to the repo. cheers Keith

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Magma December 2007