On Monday 03 November 2003 22:49, Hamilton Verissimo de Oliveira (Engenharia - SPO) wrote:
The png is 45k and the jar was 13k... and that was too big.
I fell your pain. Maybe the server doesn't like you at all >;-)
It doesn't matter... I have my own server... ;o)
FYI, I have taken the tact "specification by example", so I am pushing ahead creating some very simple plug-ins for Eclipse to aid in Avalon/Merlin development. But since I am not a killer programmer in general and not for Eclipse in particular, it will take a while.
If we start looking at the "end", i.e. Assembly of a Merlin app from N number of Components.
Merlin of today does not require, nor support any package format (like SAR with Phoenix), correct?
I don't have a problem with that. A complete application could be unzipped manually, which IMHO is good enough. I suggest we don't worry about it for now.
I am targetting to solve the following objectives with the Eclipse plug-in(s) at this level in the near to medium term;
* Each component is completely self-contained in a zip/tar/jar, and dropped into a "components/" directory. The plug-in will pick-up the components in each of the files in that directory. Each component can expose zero, one or many services. Further it can depend on zero, one or many services.
All this information is located in the Type Descriptor, which is (still?) <classname>.xinfo
It will build a Component Repository, a Service Repository and a Service Dependency tree in memory.
* Each of the component can have a default configuration, name <classname>.xconf. There are no schema/DTD requirement, and I think it is outside the scope to analyze source code, so is it a reasonable limitation that the default configuration contains the FULL configuration tree?
I think the benefits over-weigh the downsides. I would think most people do this anyway, since they would need configurations for test purposes.
* Profiles are something new that I have been able to miss. But it seems like a reasonable feature to support at IDE level. If there is a .xprofile available, the assembler will be given the choice to select a profile.
Issues
* I realize that I don't understand the "Overriding" feature. Need some better description than http://avalon.apache.org/merlin/starting/tutorial/config/override.html
* I am not comfortable with Maven, so the plug-in will harness Ant instead. For the time being, I think Ant will do more than well.
Maven is a baptism of fire, but in the end, it works very well. Any ANT target can be used in Maven, so it will work in both places.
* The following entries in distributed Type Descriptors have been found that I don't fully understand;
<extension>
<attributes>in <dependency>
<stage> & <lifestyle> is this experimental?
<logger>
Extension and Stage are for Lifecycle extensions, and Stephen and I have been all around the mulberry bush on this one. In the end, assume it works, and try not to read too much into it.
I believe Stage refers to the interface that a component uses that demands an extension handler. And Extension would be the handler itself.
* Maybe it is because it is late and I'm very tired, but right now I don't grasp "config.xml targets".
Start with what you know. The rest will follow.
I need to go and sleep. Cheers Niclas
No sleep allowed ;P
Seriously, rest up.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
