Hi Folks!
I didn't find much information on the topic, but I guess the first one is relative to the artifact itself, and the second is about information that get shown in the user interface (like, browse artifact). I could see that ShowArtifactAction is pretty much based on the ArchivaProjectModel. I also saw that ProjectModelToDatabaseConsumer is reponsible for processing the ArchivaProjectModel information for POM files and insert it into the database. But I did not find a straight path from the UI actions to the ProjectModelToDatabaseConsumer, as I see for ArtifactUpdateDatabaseConsumer, for example.
When does that kind of consumer get called?
Is the information contained in ArchivaProjectModel available on the database only after the ProjectModelToDatabaseConsumer gets called?
Sorry about the dummy questions, but I'm having a hard time trying to understand the system orchestration. After I get this right, I could provide some more detailed documentation on how to extend Archiva consumers, if you like.
Thanks in advance.
Felipe Roos
http://www.linkedin.com/in/feliperoosAchar desculpas para os nossos
defeitos não nos torna melhores
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
