You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by haleh mahbod <hm...@gmail.com> on 2007/05/29 23:40:31 UTC
Wiki Download page cleanup
Hi,
1) Would [1] be a better format & content for each download page of than
what we have today [2]?
If yes, I'll start upgrading the pages.
2) We currently use the same page to record download info for technologies.
For example, SCA Native and Java download pages are the same.
It would be cleaner if we separate the pages. For example, a Java SCA and a
Native SCA download page which gets linked to from a common
download page entry point [3]
Does this seem reasonable?
[1]
http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
[2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
[3] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
Haleh
RE: Simple use case problem
Posted by Patrick Vanhuyse <pv...@greisch.com>.
Hi Luciano,
I have attached the full code of my sample to the jira issue.
All is in it !
I now use 2 different resolvers. But it doesn't help !
Regards.
Patrick
> -----Message d'origine-----
> De : Luciano Resende [mailto:luckbr1975@gmail.com]
> Envoyé : mercredi 6 juin 2007 23:44
> À : tuscany-user@ws.apache.org
> Objet : Re: Simple use case problem
>
>
> Hi Patrick
>
> Thanks for finding a workaround for a bug in the code that process
> the contribution metadata side file, I have created a jira for it [1].
>
> Looking into the code you provided, I noticed you are using the
> same resolver while contributing both contributions, and you should be
> using two different ones....
>
> Could you also provide us with the full stack trace and the
> composite files you are using ? In the mean time, I'll try to simulate
> what I think you are doing in a test case and made it available in
> Tuscany.
>
> [1] https://issues.apache.org/jira/browse/TUSCANY-1329
>
> On 6/6/07, Patrick Vanhuyse <pv...@greisch.com> wrote:
> > Luciano,
> >
> > First try with url = "file://.../provider.jar" doesn't work because :
> >
> > In ContributionServiceImpl.java, initializeContributionMetadata
> (line 134) :
> >
> > URL[] clUrls = {sourceURL};
> > URLClassLoader cl = new URLClassLoader(clUrls);
> >
> > contributionMetadataURL =
> > cl.getResource(Contribution.SCA_CONTRIBUTION_META);
> >
> > sourceURL = "file://.../provider.jar"
> > contributionMetadataURL =
> > "file://.../consumer/target/classes/META-INF/sca-contribution.xml"
> > because of the parent class loader in cl.
> >
> > If I put a null parent class loader in the creation of cl :
> >
> > URL[] clUrls = {sourceURL};
> > URLClassLoader cl = new URLClassLoader(clUrls, null);
> >
> > contributionMetadataURL =
> > cl.getResource(Contribution.SCA_CONTRIBUTION_META);
> >
> > it finds the good sca-contribution :
> > contributionMetadataURL =
> > "jar:file://.../provider.jar!/META-INF/sca-contribution.xml"
> >
> > and it loads the ProviderComposite and the ProviderComponent in it.
> >
> > But in my test :
> >
> > // Determine my class loader and my test SCA contribution location
> > String url =
> > "file:///h:/it/logiciel_gi/sca/provider/target/provider.jar";
> >
> > ContributionService contributionService =
> > domain.getContributionService();
> > DomainCompositeHelper helper = domain.getDomainCompositeHelper();
> > ModelResolver myResolver = new
> > ModelResolverImpl(getClass().getClassLoader());
> >
> > // Contribute the SCA contribution
> > List<Contribution> contributions = new ArrayList<Contribution>(2);
> >
> > Contribution contribution = contributionService
> > .contribute("http://www.greisch.com/provider", new URL(url),
> > myResolver, false);
> > assertNotNull(contribution);
> > contributions.add(contribution);
> >
> > url = "file:///h:/it/logiciel_gi/sca/consumer/target/classes/";
> >
> > contribution = contributionService
> > .contribute("http://www.greisch.com/consumer", new URL(url),
> > myResolver, false);
> > assertNotNull(contribution);
> > contributions.add(contribution);
> >
> > for (Contribution contrib : contributions) {
> > for (Composite composite : contrib.getDeployables()) {
> > helper.addComposite(composite);
> > }
> > for (Composite composite : contrib.getDeployables()) {
> > helper.startComposite(composite);
> > }
> > }
> >
> >
> > Consumer consumer = domain.getService(Consumer.class,
> > "ConsumerComponent");
> > consumer.consume("Test");
> >
> > I get a NullPointerException when running consumer.consume("Test"). It
> > doesn't link consumer with my ProviderComponent as required in
> > Consumer.composite.
> >
> > I keep going on with all this.
> >
> > Thanks for your help.
> >
> >
> > > -----Message d'origine-----
> > > De : Luciano Resende [mailto:luckbr1975@gmail.com]
> > > Envoyé : mardi 5 juin 2007 19:49
> > > À : tuscany-user@ws.apache.org
> > > Objet : Re: Simple use case problem
> > >
> > >
> > > Patrick
> > >
> > > The contribution service package processor takes care of
> > > identifying what is the package type and creating the proper jar url
> > > for jar archives. Have you tried to pass a regular file url to the jar
> > > ? Something like :
> > >
> > > String url = "file://.../provider.jar"
> > >
> > > The contribution service iTest [1] gives an example of contributing
> > > a jar directly to the contribution service, just look for
> > > testContributeJAR.
> > >
> > > Please let me know if it works for you after you pass the
> > > simple file url.
> > >
> > >
> > > [1]
> > > https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/
> > > contribution/src/test/java/org/apache/tuscany/sca/test/contributio
> > > n/ContributionServiceTestCase.java
> > >
> > >
> > >
> > > On 6/5/07, Mike Edwards <mi...@gmail.com> wrote:
> > > > Patrick,
> > > >
> > > > One point to make here is that separate contributions are
> intended to
> > > > have different addresses, which in a simple file system equates to
> > > > different directories. If you want multiple composites in the same
> > > > directory, then you should make them part of one
> contribution, which is
> > > > allowed.
> > > >
> > > >
> > > > Yours, Mike.
> > > >
> > > > Patrick Vanhuyse wrote:
> > > > > Hi Simon,
> > > > >
> > > > > I removed sca-contibutions.xml from provider. I copied
> > > Provider.composite to
> > > > > consumer/src/main/resource. I add ProviderComposite to
> the consumer
> > > > > sca-contribution.xml. And it works.
> > > > >
> > > > > I have had a look at the code in SCADomain.newInstance(). It
> > > loads only one
> > > > > sca-contribution.xml, the first found by the class loader, I
> > > think. To solve
> > > > > this, it should look at all the sca-contribution.xml
> > > (conflict : they are
> > > > > all in the same folder) from the various jars on the
> > > classpath in place of
> > > > > using only one (depends on the ClassLoader). I don't know if
> > > it's possible
> > > > > (the class loading mechanism is a mystery to me !).
> > > Furthermore, there is
> > > > > the SCA loading mechanism used which is yet a greater mystery.
> > > > >
> > > > > I will go on with my other tests. Afterwards, if I dare, I
> > > will throw myself
> > > > > into all this loading stuff.
> > > > >
> > > > > Thanks for your help.
> > > > >
> > > > > Patrick
> > > > >
> > > > > -----Message d'origine-----
> > > > > De : Simon Laws [mailto:simonslaws@googlemail.com]
> > > > > Envoyé : mercredi 30 mai 2007 18:11
> > > > > À : tuscany-user@ws.apache.org
> > > > > Objet : Re: Simple use case problem
> > > > >
> > > > >
> > > > > Hi Patrick
> > > > >
> > > > > What is going on here is that the consumer module is not
> loading the
> > > > > provider composite. I can make this work by doing the following...
> > > > >
> > > > > 1 - Make the provider composite available to the consumer runtime
> > > > > copy the Provider.composite to
> consumer/src/main/resource
> > > > > 2 - Make the ProviderComposite deployable
> > > > > add the ProviderComposite to the consumer
> > > > > sca-contributions.xmlfile
> > > > >
> > > > > Now I kind of expected to have to do 2 so that the runtime
> > > knows that the
> > > > > composite exists and should be deployed.
> > > > >
> > > > > However I don't know how to get round 1. I would like to be
> > > able to specify
> > > > > a jar to load alongside the consumer composite that is
> > > loaded. However I
> > > > > took a look at the code and there seems to be more work to do
> > > in making the
> > > > > runtime and contribution service flexible in this way. All help is
> > > > > gratefully received if you feel like getting your hands dirty ;-)
> > > > >
> > > > > Regards
> > > > >
> > > > > Simon
> > > > >
> > > > >
> > > > >
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende
> > > http://lresende.blogspot.com/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Simple use case problem
Posted by Luciano Resende <lu...@gmail.com>.
Hi Patrick
Thanks for finding a workaround for a bug in the code that process
the contribution metadata side file, I have created a jira for it [1].
Looking into the code you provided, I noticed you are using the
same resolver while contributing both contributions, and you should be
using two different ones....
Could you also provide us with the full stack trace and the
composite files you are using ? In the mean time, I'll try to simulate
what I think you are doing in a test case and made it available in
Tuscany.
[1] https://issues.apache.org/jira/browse/TUSCANY-1329
On 6/6/07, Patrick Vanhuyse <pv...@greisch.com> wrote:
> Luciano,
>
> First try with url = "file://.../provider.jar" doesn't work because :
>
> In ContributionServiceImpl.java, initializeContributionMetadata (line 134) :
>
> URL[] clUrls = {sourceURL};
> URLClassLoader cl = new URLClassLoader(clUrls);
>
> contributionMetadataURL =
> cl.getResource(Contribution.SCA_CONTRIBUTION_META);
>
> sourceURL = "file://.../provider.jar"
> contributionMetadataURL =
> "file://.../consumer/target/classes/META-INF/sca-contribution.xml"
> because of the parent class loader in cl.
>
> If I put a null parent class loader in the creation of cl :
>
> URL[] clUrls = {sourceURL};
> URLClassLoader cl = new URLClassLoader(clUrls, null);
>
> contributionMetadataURL =
> cl.getResource(Contribution.SCA_CONTRIBUTION_META);
>
> it finds the good sca-contribution :
> contributionMetadataURL =
> "jar:file://.../provider.jar!/META-INF/sca-contribution.xml"
>
> and it loads the ProviderComposite and the ProviderComponent in it.
>
> But in my test :
>
> // Determine my class loader and my test SCA contribution location
> String url =
> "file:///h:/it/logiciel_gi/sca/provider/target/provider.jar";
>
> ContributionService contributionService =
> domain.getContributionService();
> DomainCompositeHelper helper = domain.getDomainCompositeHelper();
> ModelResolver myResolver = new
> ModelResolverImpl(getClass().getClassLoader());
>
> // Contribute the SCA contribution
> List<Contribution> contributions = new ArrayList<Contribution>(2);
>
> Contribution contribution = contributionService
> .contribute("http://www.greisch.com/provider", new URL(url),
> myResolver, false);
> assertNotNull(contribution);
> contributions.add(contribution);
>
> url = "file:///h:/it/logiciel_gi/sca/consumer/target/classes/";
>
> contribution = contributionService
> .contribute("http://www.greisch.com/consumer", new URL(url),
> myResolver, false);
> assertNotNull(contribution);
> contributions.add(contribution);
>
> for (Contribution contrib : contributions) {
> for (Composite composite : contrib.getDeployables()) {
> helper.addComposite(composite);
> }
> for (Composite composite : contrib.getDeployables()) {
> helper.startComposite(composite);
> }
> }
>
>
> Consumer consumer = domain.getService(Consumer.class,
> "ConsumerComponent");
> consumer.consume("Test");
>
> I get a NullPointerException when running consumer.consume("Test"). It
> doesn't link consumer with my ProviderComponent as required in
> Consumer.composite.
>
> I keep going on with all this.
>
> Thanks for your help.
>
>
> > -----Message d'origine-----
> > De : Luciano Resende [mailto:luckbr1975@gmail.com]
> > Envoyé : mardi 5 juin 2007 19:49
> > À : tuscany-user@ws.apache.org
> > Objet : Re: Simple use case problem
> >
> >
> > Patrick
> >
> > The contribution service package processor takes care of
> > identifying what is the package type and creating the proper jar url
> > for jar archives. Have you tried to pass a regular file url to the jar
> > ? Something like :
> >
> > String url = "file://.../provider.jar"
> >
> > The contribution service iTest [1] gives an example of contributing
> > a jar directly to the contribution service, just look for
> > testContributeJAR.
> >
> > Please let me know if it works for you after you pass the
> > simple file url.
> >
> >
> > [1]
> > https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/
> > contribution/src/test/java/org/apache/tuscany/sca/test/contributio
> > n/ContributionServiceTestCase.java
> >
> >
> >
> > On 6/5/07, Mike Edwards <mi...@gmail.com> wrote:
> > > Patrick,
> > >
> > > One point to make here is that separate contributions are intended to
> > > have different addresses, which in a simple file system equates to
> > > different directories. If you want multiple composites in the same
> > > directory, then you should make them part of one contribution, which is
> > > allowed.
> > >
> > >
> > > Yours, Mike.
> > >
> > > Patrick Vanhuyse wrote:
> > > > Hi Simon,
> > > >
> > > > I removed sca-contibutions.xml from provider. I copied
> > Provider.composite to
> > > > consumer/src/main/resource. I add ProviderComposite to the consumer
> > > > sca-contribution.xml. And it works.
> > > >
> > > > I have had a look at the code in SCADomain.newInstance(). It
> > loads only one
> > > > sca-contribution.xml, the first found by the class loader, I
> > think. To solve
> > > > this, it should look at all the sca-contribution.xml
> > (conflict : they are
> > > > all in the same folder) from the various jars on the
> > classpath in place of
> > > > using only one (depends on the ClassLoader). I don't know if
> > it's possible
> > > > (the class loading mechanism is a mystery to me !).
> > Furthermore, there is
> > > > the SCA loading mechanism used which is yet a greater mystery.
> > > >
> > > > I will go on with my other tests. Afterwards, if I dare, I
> > will throw myself
> > > > into all this loading stuff.
> > > >
> > > > Thanks for your help.
> > > >
> > > > Patrick
> > > >
> > > > -----Message d'origine-----
> > > > De : Simon Laws [mailto:simonslaws@googlemail.com]
> > > > Envoyé : mercredi 30 mai 2007 18:11
> > > > À : tuscany-user@ws.apache.org
> > > > Objet : Re: Simple use case problem
> > > >
> > > >
> > > > Hi Patrick
> > > >
> > > > What is going on here is that the consumer module is not loading the
> > > > provider composite. I can make this work by doing the following...
> > > >
> > > > 1 - Make the provider composite available to the consumer runtime
> > > > copy the Provider.composite to consumer/src/main/resource
> > > > 2 - Make the ProviderComposite deployable
> > > > add the ProviderComposite to the consumer
> > > > sca-contributions.xmlfile
> > > >
> > > > Now I kind of expected to have to do 2 so that the runtime
> > knows that the
> > > > composite exists and should be deployed.
> > > >
> > > > However I don't know how to get round 1. I would like to be
> > able to specify
> > > > a jar to load alongside the consumer composite that is
> > loaded. However I
> > > > took a look at the code and there seems to be more work to do
> > in making the
> > > > runtime and contribution service flexible in this way. All help is
> > > > gratefully received if you feel like getting your hands dirty ;-)
> > > >
> > > > Regards
> > > >
> > > > Simon
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
RE: Simple use case problem
Posted by Patrick Vanhuyse <pv...@greisch.com>.
Luciano,
First try with url = "file://.../provider.jar" doesn't work because :
In ContributionServiceImpl.java, initializeContributionMetadata (line 134) :
URL[] clUrls = {sourceURL};
URLClassLoader cl = new URLClassLoader(clUrls);
contributionMetadataURL =
cl.getResource(Contribution.SCA_CONTRIBUTION_META);
sourceURL = "file://.../provider.jar"
contributionMetadataURL =
"file://.../consumer/target/classes/META-INF/sca-contribution.xml"
because of the parent class loader in cl.
If I put a null parent class loader in the creation of cl :
URL[] clUrls = {sourceURL};
URLClassLoader cl = new URLClassLoader(clUrls, null);
contributionMetadataURL =
cl.getResource(Contribution.SCA_CONTRIBUTION_META);
it finds the good sca-contribution :
contributionMetadataURL =
"jar:file://.../provider.jar!/META-INF/sca-contribution.xml"
and it loads the ProviderComposite and the ProviderComponent in it.
But in my test :
// Determine my class loader and my test SCA contribution location
String url =
"file:///h:/it/logiciel_gi/sca/provider/target/provider.jar";
ContributionService contributionService =
domain.getContributionService();
DomainCompositeHelper helper = domain.getDomainCompositeHelper();
ModelResolver myResolver = new
ModelResolverImpl(getClass().getClassLoader());
// Contribute the SCA contribution
List<Contribution> contributions = new ArrayList<Contribution>(2);
Contribution contribution = contributionService
.contribute("http://www.greisch.com/provider", new URL(url),
myResolver, false);
assertNotNull(contribution);
contributions.add(contribution);
url = "file:///h:/it/logiciel_gi/sca/consumer/target/classes/";
contribution = contributionService
.contribute("http://www.greisch.com/consumer", new URL(url),
myResolver, false);
assertNotNull(contribution);
contributions.add(contribution);
for (Contribution contrib : contributions) {
for (Composite composite : contrib.getDeployables()) {
helper.addComposite(composite);
}
for (Composite composite : contrib.getDeployables()) {
helper.startComposite(composite);
}
}
Consumer consumer = domain.getService(Consumer.class,
"ConsumerComponent");
consumer.consume("Test");
I get a NullPointerException when running consumer.consume("Test"). It
doesn't link consumer with my ProviderComponent as required in
Consumer.composite.
I keep going on with all this.
Thanks for your help.
> -----Message d'origine-----
> De : Luciano Resende [mailto:luckbr1975@gmail.com]
> Envoyé : mardi 5 juin 2007 19:49
> À : tuscany-user@ws.apache.org
> Objet : Re: Simple use case problem
>
>
> Patrick
>
> The contribution service package processor takes care of
> identifying what is the package type and creating the proper jar url
> for jar archives. Have you tried to pass a regular file url to the jar
> ? Something like :
>
> String url = "file://.../provider.jar"
>
> The contribution service iTest [1] gives an example of contributing
> a jar directly to the contribution service, just look for
> testContributeJAR.
>
> Please let me know if it works for you after you pass the
> simple file url.
>
>
> [1]
> https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/
> contribution/src/test/java/org/apache/tuscany/sca/test/contributio
> n/ContributionServiceTestCase.java
>
>
>
> On 6/5/07, Mike Edwards <mi...@gmail.com> wrote:
> > Patrick,
> >
> > One point to make here is that separate contributions are intended to
> > have different addresses, which in a simple file system equates to
> > different directories. If you want multiple composites in the same
> > directory, then you should make them part of one contribution, which is
> > allowed.
> >
> >
> > Yours, Mike.
> >
> > Patrick Vanhuyse wrote:
> > > Hi Simon,
> > >
> > > I removed sca-contibutions.xml from provider. I copied
> Provider.composite to
> > > consumer/src/main/resource. I add ProviderComposite to the consumer
> > > sca-contribution.xml. And it works.
> > >
> > > I have had a look at the code in SCADomain.newInstance(). It
> loads only one
> > > sca-contribution.xml, the first found by the class loader, I
> think. To solve
> > > this, it should look at all the sca-contribution.xml
> (conflict : they are
> > > all in the same folder) from the various jars on the
> classpath in place of
> > > using only one (depends on the ClassLoader). I don't know if
> it's possible
> > > (the class loading mechanism is a mystery to me !).
> Furthermore, there is
> > > the SCA loading mechanism used which is yet a greater mystery.
> > >
> > > I will go on with my other tests. Afterwards, if I dare, I
> will throw myself
> > > into all this loading stuff.
> > >
> > > Thanks for your help.
> > >
> > > Patrick
> > >
> > > -----Message d'origine-----
> > > De : Simon Laws [mailto:simonslaws@googlemail.com]
> > > Envoyé : mercredi 30 mai 2007 18:11
> > > À : tuscany-user@ws.apache.org
> > > Objet : Re: Simple use case problem
> > >
> > >
> > > Hi Patrick
> > >
> > > What is going on here is that the consumer module is not loading the
> > > provider composite. I can make this work by doing the following...
> > >
> > > 1 - Make the provider composite available to the consumer runtime
> > > copy the Provider.composite to consumer/src/main/resource
> > > 2 - Make the ProviderComposite deployable
> > > add the ProviderComposite to the consumer
> > > sca-contributions.xmlfile
> > >
> > > Now I kind of expected to have to do 2 so that the runtime
> knows that the
> > > composite exists and should be deployed.
> > >
> > > However I don't know how to get round 1. I would like to be
> able to specify
> > > a jar to load alongside the consumer composite that is
> loaded. However I
> > > took a look at the code and there seems to be more work to do
> in making the
> > > runtime and contribution service flexible in this way. All help is
> > > gratefully received if you feel like getting your hands dirty ;-)
> > >
> > > Regards
> > >
> > > Simon
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Simple use case problem
Posted by Luciano Resende <lu...@gmail.com>.
Patrick
The contribution service package processor takes care of
identifying what is the package type and creating the proper jar url
for jar archives. Have you tried to pass a regular file url to the jar
? Something like :
String url = "file://.../provider.jar"
The contribution service iTest [1] gives an example of contributing
a jar directly to the contribution service, just look for
testContributeJAR.
Please let me know if it works for you after you pass the simple file url.
[1] https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/contribution/src/test/java/org/apache/tuscany/sca/test/contribution/ContributionServiceTestCase.java
On 6/5/07, Mike Edwards <mi...@gmail.com> wrote:
> Patrick,
>
> One point to make here is that separate contributions are intended to
> have different addresses, which in a simple file system equates to
> different directories. If you want multiple composites in the same
> directory, then you should make them part of one contribution, which is
> allowed.
>
>
> Yours, Mike.
>
> Patrick Vanhuyse wrote:
> > Hi Simon,
> >
> > I removed sca-contibutions.xml from provider. I copied Provider.composite to
> > consumer/src/main/resource. I add ProviderComposite to the consumer
> > sca-contribution.xml. And it works.
> >
> > I have had a look at the code in SCADomain.newInstance(). It loads only one
> > sca-contribution.xml, the first found by the class loader, I think. To solve
> > this, it should look at all the sca-contribution.xml (conflict : they are
> > all in the same folder) from the various jars on the classpath in place of
> > using only one (depends on the ClassLoader). I don't know if it's possible
> > (the class loading mechanism is a mystery to me !). Furthermore, there is
> > the SCA loading mechanism used which is yet a greater mystery.
> >
> > I will go on with my other tests. Afterwards, if I dare, I will throw myself
> > into all this loading stuff.
> >
> > Thanks for your help.
> >
> > Patrick
> >
> > -----Message d'origine-----
> > De : Simon Laws [mailto:simonslaws@googlemail.com]
> > Envoyé : mercredi 30 mai 2007 18:11
> > À : tuscany-user@ws.apache.org
> > Objet : Re: Simple use case problem
> >
> >
> > Hi Patrick
> >
> > What is going on here is that the consumer module is not loading the
> > provider composite. I can make this work by doing the following...
> >
> > 1 - Make the provider composite available to the consumer runtime
> > copy the Provider.composite to consumer/src/main/resource
> > 2 - Make the ProviderComposite deployable
> > add the ProviderComposite to the consumer
> > sca-contributions.xmlfile
> >
> > Now I kind of expected to have to do 2 so that the runtime knows that the
> > composite exists and should be deployed.
> >
> > However I don't know how to get round 1. I would like to be able to specify
> > a jar to load alongside the consumer composite that is loaded. However I
> > took a look at the code and there seems to be more work to do in making the
> > runtime and contribution service flexible in this way. All help is
> > gratefully received if you feel like getting your hands dirty ;-)
> >
> > Regards
> >
> > Simon
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Simple use case problem
Posted by Mike Edwards <mi...@gmail.com>.
Patrick,
One point to make here is that separate contributions are intended to
have different addresses, which in a simple file system equates to
different directories. If you want multiple composites in the same
directory, then you should make them part of one contribution, which is
allowed.
Yours, Mike.
Patrick Vanhuyse wrote:
> Hi Simon,
>
> I removed sca-contibutions.xml from provider. I copied Provider.composite to
> consumer/src/main/resource. I add ProviderComposite to the consumer
> sca-contribution.xml. And it works.
>
> I have had a look at the code in SCADomain.newInstance(). It loads only one
> sca-contribution.xml, the first found by the class loader, I think. To solve
> this, it should look at all the sca-contribution.xml (conflict : they are
> all in the same folder) from the various jars on the classpath in place of
> using only one (depends on the ClassLoader). I don't know if it's possible
> (the class loading mechanism is a mystery to me !). Furthermore, there is
> the SCA loading mechanism used which is yet a greater mystery.
>
> I will go on with my other tests. Afterwards, if I dare, I will throw myself
> into all this loading stuff.
>
> Thanks for your help.
>
> Patrick
>
> -----Message d'origine-----
> De : Simon Laws [mailto:simonslaws@googlemail.com]
> Envoyé : mercredi 30 mai 2007 18:11
> À : tuscany-user@ws.apache.org
> Objet : Re: Simple use case problem
>
>
> Hi Patrick
>
> What is going on here is that the consumer module is not loading the
> provider composite. I can make this work by doing the following...
>
> 1 - Make the provider composite available to the consumer runtime
> copy the Provider.composite to consumer/src/main/resource
> 2 - Make the ProviderComposite deployable
> add the ProviderComposite to the consumer
> sca-contributions.xmlfile
>
> Now I kind of expected to have to do 2 so that the runtime knows that the
> composite exists and should be deployed.
>
> However I don't know how to get round 1. I would like to be able to specify
> a jar to load alongside the consumer composite that is loaded. However I
> took a look at the code and there seems to be more work to do in making the
> runtime and contribution service flexible in this way. All help is
> gratefully received if you feel like getting your hands dirty ;-)
>
> Regards
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
RE: Simple use case problem
Posted by Patrick Vanhuyse <pv...@greisch.com>.
Hi Jean-Sebastien,
When I try to load a contributions using
Contribution contribution =
contributionService.contribute("http://test/contribution", new URL(url),
myResolver, false);
with the url pointing to a jar ("jar:file://.../provider.jar!/"), I get the
following error :
Running consumer.ConsumerEmbeddedTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.11 sec <<<
FAILURE!
testDomain(consumer.ConsumerEmbeddedTestCase) Time elapsed: 0.079 sec <<<
ERROR!
java.io.IOException: no entry name specified
at
sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.ja
va:112)
at java.net.URL.openStream(URL.java:1007)
at
org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.add
Contribution(ContributionServiceI
mpl.java:237)
at
org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.con
tribute(ContributionServiceImpl.j
ava:119)
at
consumer.ConsumerEmbeddedTestCase.testDomain(ConsumerEmbeddedTestCase.java:5
8)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35
)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62
)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Ab
stractDirectoryTestSuite.java:138
)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractD
irectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireB
ooter.java:290)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818
)
When I remove the "!/" at the end, I have an error saying that "!/" is
missing !
If I try with a file in the jar, I get a
org.apache.tuscany.sca.contribution.service.UnsupportedContentTypeException.
Any idea ?
Thanks.
Patrick
> -----Message d'origine-----
> De : Jean-Sebastien Delfino [mailto:jsdelfino@apache.org]
> Envoyé : samedi 2 juin 2007 4:13
> À : tuscany-user@ws.apache.org
> Objet : Re: Simple use case problem
>
>
> Patrick Vanhuyse wrote:
> > Hi Simon,
> >
> > I removed sca-contibutions.xml from provider. I copied
> Provider.composite to
> > consumer/src/main/resource. I add ProviderComposite to the consumer
> > sca-contribution.xml. And it works.
> >
> > I have had a look at the code in SCADomain.newInstance(). It
> loads only one
> > sca-contribution.xml, the first found by the class loader, I
> think. To solve
> > this, it should look at all the sca-contribution.xml (conflict
> : they are
> > all in the same folder) from the various jars on the classpath
> in place of
> > using only one (depends on the ClassLoader). I don't know if
> it's possible
> > (the class loading mechanism is a mystery to me !).
> Furthermore, there is
> > the SCA loading mechanism used which is yet a greater mystery.
> >
> > I will go on with my other tests. Afterwards, if I dare, I will
> throw myself
> > into all this loading stuff.
> >
> > Thanks for your help.
> >
> > Patrick
> >
> > -----Message d'origine-----
> > De : Simon Laws [mailto:simonslaws@googlemail.com]
> > Envoyé : mercredi 30 mai 2007 18:11
> > À : tuscany-user@ws.apache.org
> > Objet : Re: Simple use case problem
> >
> >
> > Hi Patrick
> >
> > What is going on here is that the consumer module is not loading the
> > provider composite. I can make this work by doing the following...
> >
> > 1 - Make the provider composite available to the consumer runtime
> > copy the Provider.composite to consumer/src/main/resource
> > 2 - Make the ProviderComposite deployable
> > add the ProviderComposite to the consumer
> > sca-contributions.xmlfile
> >
> > Now I kind of expected to have to do 2 so that the runtime
> knows that the
> > composite exists and should be deployed.
> >
> > However I don't know how to get round 1. I would like to be
> able to specify
> > a jar to load alongside the consumer composite that is loaded.
> However I
> > took a look at the code and there seems to be more work to do
> in making the
> > runtime and contribution service flexible in this way. All help is
> > gratefully received if you feel like getting your hands dirty ;-)
> >
> > Regards
> >
> > Simon
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-user-help@ws.apache.org
> >
> >
> >
>
> Hi,
>
> DefaultSCADomain is a minimal domain bootstrap utility initially
> designed to work with a single SCA contribution (one JAR or folder).
>
> If you want to try, you should be able to add multiple contributions to
> a domain using EmbeddedSCADomain instead of DefaultSCADomain.
> EmbeddedSCADomain is a more flexible domain bootstrap class that allows
> you to add/remove contributions, add/remove composites to the domain,
> and start/stop components contained in these composites. The
> EmbeddedSCADomainTestCase [1] test case shows how to use
> EmbeddedSCADomain, to create a domain, populate it and use it.
>
> [1]
> http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules
> /host-embedded/src/test/java/org/apache/tuscany/sca/host/embedded/
> impl/EmbeddedSCADomainTestCase.java
>
> Line 62:
> Contribution contribution =
> contributionService.contribute("http://test/contribution", new URL(url),
> myResolver, false);
> adds a contribution, the URL can point to a contribution folder or JAR.
>
> Maybe you can try to add multiple contributions this way? let me know
> how it goes... Thanks.
>
> Hope this helps.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Simple use case problem
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Patrick Vanhuyse wrote:
> Hi Simon,
>
> I removed sca-contibutions.xml from provider. I copied Provider.composite to
> consumer/src/main/resource. I add ProviderComposite to the consumer
> sca-contribution.xml. And it works.
>
> I have had a look at the code in SCADomain.newInstance(). It loads only one
> sca-contribution.xml, the first found by the class loader, I think. To solve
> this, it should look at all the sca-contribution.xml (conflict : they are
> all in the same folder) from the various jars on the classpath in place of
> using only one (depends on the ClassLoader). I don't know if it's possible
> (the class loading mechanism is a mystery to me !). Furthermore, there is
> the SCA loading mechanism used which is yet a greater mystery.
>
> I will go on with my other tests. Afterwards, if I dare, I will throw myself
> into all this loading stuff.
>
> Thanks for your help.
>
> Patrick
>
> -----Message d'origine-----
> De : Simon Laws [mailto:simonslaws@googlemail.com]
> Envoyé : mercredi 30 mai 2007 18:11
> À : tuscany-user@ws.apache.org
> Objet : Re: Simple use case problem
>
>
> Hi Patrick
>
> What is going on here is that the consumer module is not loading the
> provider composite. I can make this work by doing the following...
>
> 1 - Make the provider composite available to the consumer runtime
> copy the Provider.composite to consumer/src/main/resource
> 2 - Make the ProviderComposite deployable
> add the ProviderComposite to the consumer
> sca-contributions.xmlfile
>
> Now I kind of expected to have to do 2 so that the runtime knows that the
> composite exists and should be deployed.
>
> However I don't know how to get round 1. I would like to be able to specify
> a jar to load alongside the consumer composite that is loaded. However I
> took a look at the code and there seems to be more work to do in making the
> runtime and contribution service flexible in this way. All help is
> gratefully received if you feel like getting your hands dirty ;-)
>
> Regards
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-user-help@ws.apache.org
>
>
>
Hi,
DefaultSCADomain is a minimal domain bootstrap utility initially
designed to work with a single SCA contribution (one JAR or folder).
If you want to try, you should be able to add multiple contributions to
a domain using EmbeddedSCADomain instead of DefaultSCADomain.
EmbeddedSCADomain is a more flexible domain bootstrap class that allows
you to add/remove contributions, add/remove composites to the domain,
and start/stop components contained in these composites. The
EmbeddedSCADomainTestCase [1] test case shows how to use
EmbeddedSCADomain, to create a domain, populate it and use it.
[1]
http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/host-embedded/src/test/java/org/apache/tuscany/sca/host/embedded/impl/EmbeddedSCADomainTestCase.java
Line 62:
Contribution contribution =
contributionService.contribute("http://test/contribution", new URL(url),
myResolver, false);
adds a contribution, the URL can point to a contribution folder or JAR.
Maybe you can try to add multiple contributions this way? let me know
how it goes... Thanks.
Hope this helps.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
RE: Simple use case problem
Posted by Patrick Vanhuyse <pv...@greisch.com>.
Hi Simon,
I removed sca-contibutions.xml from provider. I copied Provider.composite to
consumer/src/main/resource. I add ProviderComposite to the consumer
sca-contribution.xml. And it works.
I have had a look at the code in SCADomain.newInstance(). It loads only one
sca-contribution.xml, the first found by the class loader, I think. To solve
this, it should look at all the sca-contribution.xml (conflict : they are
all in the same folder) from the various jars on the classpath in place of
using only one (depends on the ClassLoader). I don't know if it's possible
(the class loading mechanism is a mystery to me !). Furthermore, there is
the SCA loading mechanism used which is yet a greater mystery.
I will go on with my other tests. Afterwards, if I dare, I will throw myself
into all this loading stuff.
Thanks for your help.
Patrick
-----Message d'origine-----
De : Simon Laws [mailto:simonslaws@googlemail.com]
Envoyé : mercredi 30 mai 2007 18:11
À : tuscany-user@ws.apache.org
Objet : Re: Simple use case problem
Hi Patrick
What is going on here is that the consumer module is not loading the
provider composite. I can make this work by doing the following...
1 - Make the provider composite available to the consumer runtime
copy the Provider.composite to consumer/src/main/resource
2 - Make the ProviderComposite deployable
add the ProviderComposite to the consumer
sca-contributions.xmlfile
Now I kind of expected to have to do 2 so that the runtime knows that the
composite exists and should be deployed.
However I don't know how to get round 1. I would like to be able to specify
a jar to load alongside the consumer composite that is loaded. However I
took a look at the code and there seems to be more work to do in making the
runtime and contribution service flexible in this way. All help is
gratefully received if you feel like getting your hands dirty ;-)
Regards
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Simple use case problem
Posted by Simon Laws <si...@googlemail.com>.
Hi Patrick
What is going on here is that the consumer module is not loading the
provider composite. I can make this work by doing the following...
1 - Make the provider composite available to the consumer runtime
copy the Provider.composite to consumer/src/main/resource
2 - Make the ProviderComposite deployable
add the ProviderComposite to the consumer sca-contributions.xmlfile
Now I kind of expected to have to do 2 so that the runtime knows that the
composite exists and should be deployed.
However I don't know how to get round 1. I would like to be able to specify
a jar to load alongside the consumer composite that is loaded. However I
took a look at the code and there seems to be more work to do in making the
runtime and contribution service flexible in this way. All help is
gratefully received if you feel like getting your hands dirty ;-)
Regards
Simon
RE: Simple use case problem
Posted by Patrick Vanhuyse <pv...@greisch.com>.
Hi Simon,
It's in the same VM.
I have sent the full code (a 29K ZIP file) to your e-mail.
Thanks
Patrick
-----Message d'origine-----
De : Simon Laws [mailto:simonslaws@googlemail.com]
Envoyé : mercredi 30 mai 2007 15:06
À : tuscany-user@ws.apache.org
Objet : Re: Simple use case problem
Hi Patrick and welcome
So it sounds like you have two composites in separate Jar files.
Are these composites both being contributed to a Tuscany runtime in the same
VM? I believe this should work but I've not tried it. I can have a look for
you if you give me a little more detail.
If you are trying to run the composites on separate VMs then our cross VM
domain support is not checked into head yet. Just working on it at the
moment.
Regards
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Simple use case problem
Posted by Simon Laws <si...@googlemail.com>.
Hi Patrick and welcome
So it sounds like you have two composites in separate Jar files.
Are these composites both being contributed to a Tuscany runtime in the same
VM? I believe this should work but I've not tried it. I can have a look for
you if you give me a little more detail.
If you are trying to run the composites on separate VMs then our cross VM
domain support is not checked into head yet. Just working on it at the
moment.
Regards
Simon
Re: Wiki Download page cleanup
Posted by Venkata Krishnan <fo...@gmail.com>.
Hi Haleh, yes it seems so :). Let me look up and then post back.. thanks.
- Venkat
On 6/1/07, haleh mahbod <hm...@gmail.com> wrote:
>
> Hi Venkat,
>
> It looks like we posted a response to Ant's message at the same time and
> missed each other's email and my changes show up on the site. Is the flow
> of
> information OK?
>
> Basically the old releases page linked to from the .90 page would be the
> page that you have suggested.
> Haleh
>
> On 5/31/07, Hernan Cunico <hc...@gmail.com> wrote:
> >
> > Done!
> >
> > Cheers!
> > Hernan
> >
> > Hernan Cunico wrote:
> > > I'll run a manual autoexport to fix it.
> > > You should see the changes in about 2 mins
> > >
> > > Cheers!
> > > Hernan
> > >
> > > Luciano Resende wrote:
> > >> Why it shows in [1] and not in [2] ?
> > >>
> > >> [1] http://cwiki.apache.org/TUSCANY/home.html
> > >> [2] http://cwiki.apache.org/TUSCANY/
> > >>
> > >>
> > >> On 5/31/07, Venkata Krishnan <fo...@gmail.com> wrote:
> > >>> I've changed the home page to include a box highlighting the latest
> > >>> releases. Let me know if it seems ok
> > >>>
> > >>> - Venkat
> > >>>
> > >>> On 5/31/07, haleh mahbod <hm...@gmail.com> wrote:
> > >>> >
> > >>> > I made the following updates:
> > >>> > Tuscany Download page, 'SCA Java' is linked to [1]
> > >>> > on [1], Other release DOWNLOAD is linked to the old Java SCA
> > >>> Download page
> > >>> > (old releases)
> > >>> >
> > >>> > To do:
> > >>> > [1] could be renamed to SCA Java Latest Release. This page could
> > >>> always
> > >>> > hold
> > >>> > info about the latest release.
> > >>> > [2] could be renamed to SCA Java previous Releases.
> > >>> > [2] needs to be updated to the format that we discussed earlier on
> > >>> this
> > >>> > thread
> > >>> >
> > >>> > If this looks OK, I go ahead and make the changes for the 'to do'
> > >>> list.
> > >>> >
> > >>> >
> > >>> > [1]
> > >>> >
> > >>> >
> > >>>
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> > >>>
> > >>> > [2]
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > >>> >
> > >>> >
> > >>> > On 5/31/07, ant elder <an...@gmail.com> wrote:
> > >>> > >
> > >>> > > Ok, I've added a new download page for the SCA Java 0.90 release
> > >>> which
> > >>> > > hopefully isn't to far away from whats been talked about:
> > >>> > >
> > >>> > >
> > >>> > >
> > >>> >
> > >>>
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> > >>>
> > >>> > >
> > >>> > > Its not linked to from anywhere yet as I'm not sure after all
> this
> > >>> > > discussion where to put it. The main things I think would be
> good
> > >>> are to
> > >>> > > not
> > >>> > > have to click through many links to get to the actual download
> > >>> link for
> > >>> > a
> > >>> > > latest release and for it to be quite obvious what the current
> > >>> latest
> > >>> > > release is of something and its not obscured that with lots of
> old
> > >>> > > download
> > >>> > > links.
> > >>> > >
> > >>> > > I wondered if the download page pointed to from the "General"
> > >>> menu box
> > >>> > > could
> > >>> > > be expanded to have links to each of the current download pages
> > >>> (the
> > >>> > > above
> > >>> > > SCA+Java+0.90-incubating etc) and at the bottom another link to
> a
> > >>> page
> > >>> > > with
> > >>> > > all the old downloads?
> > >>> > >
> > >>> > > ...ant
> > >>> > >
> > >>> > > On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
> > >>> > > >
> > >>> > > > Hi
> > >>> > > >
> > >>> > > > What we are attempting to do now it really far better than
> > >>> cluttering
> > >>> > > all
> > >>> > > > the downloads together on one page. Here is what I think
> about
> > >>> this
> > >>> > > >
> > >>> > > > - for every Release (SCA / SDO / DAS) have a separate page
> > >>> whose first
> > >>> > > > section talks about what comprises of that release (including
> > spec
> > >>> > > levels
> > >>> > > > etc.) and then have a next section that is titled 'Downloads'.
> > >>> > > > - then have a single page titled 'Releases' where we list all
> > the
> > >>> > > releases
> > >>> > > > and each entry is a link to the separate Release page. Here
> > >>> again we
> > >>> > > > could
> > >>> > > > choose to have SCA Releases, SDO Releases, DAS Releases on
> > >>> diff. pages
> > >>> > > or
> > >>> > > > just have all in one under diff sections.
> > >>> > > > - Finally from the global home page and the home page of the
> > >>> > subprojects
> > >>> > > > have a menu item 'Releases' that will point to the 'Releases'
> > >>> page.
> > >>> > > >
> > >>> > > > This way, with every release we simply have to go an make the
> > >>> specific
> > >>> > > > release page and add a link to the Releases page. I had
> > >>> created a
> > >>> > > > Release
> > >>> > > > page for the recent SDO Release without the Downloads section
> > >>> > > > though. Here
> > >>> > > > it is just for people to get an idea of what I mean
> > >>> > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
> > >>>
> > >>> > > >
> > >>> > > > When creating these Release pages my request is that we
> > >>> maintain the
> > >>> > > page
> > >>> > > > hierarchies. For example the release page for the SCA
> 0.90release
> > >>> > > should
> > >>> > > > be
> > >>> > > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90
> > >>> Release.
> > >>> > > >
> > >>> > > > By the way there is a SCA Java and a SCA Java Subproject page
> -
> > >>> can we
> > >>> > > > merge
> > >>> > > > these two into one.
> > >>> > > >
> > >>> > > > Thanks
> > >>> > > >
> > >>> > > > - Venkat
> > >>> > > >
> > >>> > > > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> > >>> > > > >
> > >>> > > > > I am including tuscany-users to get their opinion if
> > interested.
> > >>> > > > >
> > >>> > > > > Here are my thoughts influenced by your comments :)
> > >>> > > > > - Separate the download information for latest release from
> > >>> the old
> > >>> > > > > releases.
> > >>> > > > > - Having the text of the change file/read me on the front
> > >>> page of
> > >>> > the
> > >>> > > > > download page is good. This makes it easier to identify what
> > >>> is in
> > >>> > the
> > >>> > > > new
> > >>> > > > > release. So, added a section called 'what's new in this
> > >>> release'.
> > >>> > > > > - It is good to have download information for at least the
> > >>> back 2
> > >>> > > > > releases.
> > >>> > > > >
> > >>> > > > > - It is useful to know what level of spec is supported by
> each
> > >>> > > release.
> > >>> > > > > For
> > >>> > > > > example, for SCA there are several specs. A release can be
> at
> > >>> > Assembly
> > >>> > > > > 1.0level and an older version of Client spec.
> > >>> > > > > - Having a page that takes user to all the downloads[2] is
> > >>> good.
> > >>> > > > > - Having a download page per subproject is good since the
> > >>> audience
> > >>> > > for
> > >>> > > > > each
> > >>> > > > > download page may be different. For example, someone using
> > >>> SDO may
> > >>> > not
> > >>> > > > > necessarily want to download SCA.
> > >>> > > > >
> > >>> > > > > Here is an attempt for a sample download page which
> > incorporates
> > >>> > your
> > >>> > > > > feedback [1]
> > >>> > > > > User will reach[1] from [2] (not linked yet)
> > >>> > > > >
> > >>> > > > > [1]
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > >>>
> > >>> > > > > [2]
> > >>> > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > >>> > > > >
> > >>> > > > > Does it look OK?
> > >>> > > > >
> > >>> > > > >
> > >>> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > >>> > > > > >
> > >>> > > > > > The idea of a single download page sounds good, but if we
> > are
> > >>> > > thinking
> > >>> > > > > > about tracking page visitors to correlate to the number of
> > >>> > > downloads,
> > >>> > > > > > we won't be able to identify if the person is visiting the
> > >>> page to
> > >>> > > > > > download SCA, SDO or DAS.
> > >>> > > > > >
> > >>> > > > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > >>> > > > > > > I agree it would be good to not duplicate things for
> each
> > >>> > > > downloadable
> > >>> > > > > > > artifact associated with a release. Not sure it really
> > >>> needs the
> > >>> > > day
> > >>> > > > > of
> > >>> > > > > > the
> > >>> > > > > > > release or the assembly spec info either.
> > >>> > > > > > >
> > >>> > > > > > > And +1 to having old release downloads on a separate
> > >>> page. I'm
> > >>> > not
> > >>> > > > > sure
> > >>> > > > > > if
> > >>> > > > > > > this is the proposal but could there be a single
> download
> > >>> page
> > >>> > > that
> > >>> > > > > has
> > >>> > > > > > the
> > >>> > > > > > > current latest release of each of SCA, SDO and DAS?
> > >>> > > > > > >
> > >>> > > > > > > ...ant
> > >>> > > > > > >
> > >>> > > > > > > On 5/29/07, Luciano Resende <lu...@gmail.com>
> wrote:
> > >>> > > > > > > >
> > >>> > > > > > > > My understanding is that you moved the release name
> and
> > >>> date
> > >>> > > from
> > >>> > > > > the
> > >>> > > > > > > > "download section" to the "download table". If they
> are
> > >>> > always
> > >>> > > > same
> > >>> > > > > > > > for a group of downloads, won't it take space from the
> > >>> page by
> > >>> > > > > > > > repeating it on each table row ?
> > >>> > > > > > > >
> > >>> > > > > > > > Also, do we want to keep all past releases available
> on
> > >>> the
> > >>> > main
> > >>> > > > > > > > download page ? Maybe we could have an separate
> archive
> > >>> page,
> > >>> > > and
> > >>> > > > > only
> > >>> > > > > > > > the latest release available in the main download
> page,
> > >>> this
> > >>> > > would
> > >>> > > > > > > > encourage people to always use the latest stable stuff
> ?
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > >>> > > > > > > > > Hi,
> > >>> > > > > > > > >
> > >>> > > > > > > > > 1) Would [1] be a better format & content for each
> > >>> download
> > >>> > > > page
> > >>> > > > > > > > of than
> > >>> > > > > > > > > what we have today [2]?
> > >>> > > > > > > > > If yes, I'll start upgrading the pages.
> > >>> > > > > > > > >
> > >>> > > > > > > > > 2) We currently use the same page to record download
> > >>> info
> > >>> > for
> > >>> > > > > > > > technologies.
> > >>> > > > > > > > > For example, SCA Native and Java download pages are
> > the
> > >>> > same.
> > >>> > > > > > > > > It would be cleaner if we separate the pages. For
> > >>> example, a
> > >>> > > > Java
> > >>> > > > > > SCA
> > >>> > > > > > > > and a
> > >>> > > > > > > > > Native SCA download page which gets linked to from a
> > >>> common
> > >>> > > > > > > > > download page entry point [3]
> > >>> > > > > > > > > Does this seem reasonable?
> > >>> > > > > > > > >
> > >>> > > > > > > > >
> > >>> > > > > > > > > [1]
> > >>> > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > >>>
> > >>> > > > > > > > > [2]
> > >>> > > > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > >>> > > > > > > > > [3]
> > >>> > > > > >
> > >>> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > >>> > > > > > > > >
> > >>> > > > > > > > >
> > >>> > > > > > > > > Haleh
> > >>> > > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > > > --
> > >>> > > > > > > > Luciano Resende
> > >>> > > > > > > > Apache Tuscany Committer
> > >>> > > > > > > > http://people.apache.org/~lresende
> > >>> > > > > > > > http://lresende.blogspot.com/
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > >
> > >>> >
> > ---------------------------------------------------------------------
> > >>> > > > > > > > To unsubscribe, e-mail:
> > >>> tuscany-dev-unsubscribe@ws.apache.org
> > >>> > > > > > > > For additional commands, e-mail:
> > >>> > tuscany-dev-help@ws.apache.org
> > >>> > > > > > > >
> > >>> > > > > > > >
> > >>> > > > > > >
> > >>> > > > > >
> > >>> > > > > >
> > >>> > > > > > --
> > >>> > > > > > Luciano Resende
> > >>> > > > > > Apache Tuscany Committer
> > >>> > > > > > http://people.apache.org/~lresende
> > >>> > > > > > http://lresende.blogspot.com/
> > >>> > > > > >
> > >>> > > > > >
> > >>> > >
> > >>>
> ---------------------------------------------------------------------
> > >>> > > > > > To unsubscribe, e-mail:
> > tuscany-dev-unsubscribe@ws.apache.org
> > >>> > > > > > For additional commands, e-mail:
> > >>> tuscany-dev-help@ws.apache.org
> > >>> > > > > >
> > >>> > > > > >
> > >>> > > > >
> > >>> > > >
> > >>> > >
> > >>> >
> > >>>
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
Re: Wiki Download page cleanup
Posted by haleh mahbod <hm...@gmail.com>.
Hi Venkat,
It looks like we posted a response to Ant's message at the same time and
missed each other's email and my changes show up on the site. Is the flow of
information OK?
Basically the old releases page linked to from the .90 page would be the
page that you have suggested.
Haleh
On 5/31/07, Hernan Cunico <hc...@gmail.com> wrote:
>
> Done!
>
> Cheers!
> Hernan
>
> Hernan Cunico wrote:
> > I'll run a manual autoexport to fix it.
> > You should see the changes in about 2 mins
> >
> > Cheers!
> > Hernan
> >
> > Luciano Resende wrote:
> >> Why it shows in [1] and not in [2] ?
> >>
> >> [1] http://cwiki.apache.org/TUSCANY/home.html
> >> [2] http://cwiki.apache.org/TUSCANY/
> >>
> >>
> >> On 5/31/07, Venkata Krishnan <fo...@gmail.com> wrote:
> >>> I've changed the home page to include a box highlighting the latest
> >>> releases. Let me know if it seems ok
> >>>
> >>> - Venkat
> >>>
> >>> On 5/31/07, haleh mahbod <hm...@gmail.com> wrote:
> >>> >
> >>> > I made the following updates:
> >>> > Tuscany Download page, 'SCA Java' is linked to [1]
> >>> > on [1], Other release DOWNLOAD is linked to the old Java SCA
> >>> Download page
> >>> > (old releases)
> >>> >
> >>> > To do:
> >>> > [1] could be renamed to SCA Java Latest Release. This page could
> >>> always
> >>> > hold
> >>> > info about the latest release.
> >>> > [2] could be renamed to SCA Java previous Releases.
> >>> > [2] needs to be updated to the format that we discussed earlier on
> >>> this
> >>> > thread
> >>> >
> >>> > If this looks OK, I go ahead and make the changes for the 'to do'
> >>> list.
> >>> >
> >>> >
> >>> > [1]
> >>> >
> >>> >
> >>>
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> >>>
> >>> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> >>> >
> >>> >
> >>> > On 5/31/07, ant elder <an...@gmail.com> wrote:
> >>> > >
> >>> > > Ok, I've added a new download page for the SCA Java 0.90 release
> >>> which
> >>> > > hopefully isn't to far away from whats been talked about:
> >>> > >
> >>> > >
> >>> > >
> >>> >
> >>>
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> >>>
> >>> > >
> >>> > > Its not linked to from anywhere yet as I'm not sure after all this
> >>> > > discussion where to put it. The main things I think would be good
> >>> are to
> >>> > > not
> >>> > > have to click through many links to get to the actual download
> >>> link for
> >>> > a
> >>> > > latest release and for it to be quite obvious what the current
> >>> latest
> >>> > > release is of something and its not obscured that with lots of old
> >>> > > download
> >>> > > links.
> >>> > >
> >>> > > I wondered if the download page pointed to from the "General"
> >>> menu box
> >>> > > could
> >>> > > be expanded to have links to each of the current download pages
> >>> (the
> >>> > > above
> >>> > > SCA+Java+0.90-incubating etc) and at the bottom another link to a
> >>> page
> >>> > > with
> >>> > > all the old downloads?
> >>> > >
> >>> > > ...ant
> >>> > >
> >>> > > On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
> >>> > > >
> >>> > > > Hi
> >>> > > >
> >>> > > > What we are attempting to do now it really far better than
> >>> cluttering
> >>> > > all
> >>> > > > the downloads together on one page. Here is what I think about
> >>> this
> >>> > > >
> >>> > > > - for every Release (SCA / SDO / DAS) have a separate page
> >>> whose first
> >>> > > > section talks about what comprises of that release (including
> spec
> >>> > > levels
> >>> > > > etc.) and then have a next section that is titled 'Downloads'.
> >>> > > > - then have a single page titled 'Releases' where we list all
> the
> >>> > > releases
> >>> > > > and each entry is a link to the separate Release page. Here
> >>> again we
> >>> > > > could
> >>> > > > choose to have SCA Releases, SDO Releases, DAS Releases on
> >>> diff. pages
> >>> > > or
> >>> > > > just have all in one under diff sections.
> >>> > > > - Finally from the global home page and the home page of the
> >>> > subprojects
> >>> > > > have a menu item 'Releases' that will point to the 'Releases'
> >>> page.
> >>> > > >
> >>> > > > This way, with every release we simply have to go an make the
> >>> specific
> >>> > > > release page and add a link to the Releases page. I had
> >>> created a
> >>> > > > Release
> >>> > > > page for the recent SDO Release without the Downloads section
> >>> > > > though. Here
> >>> > > > it is just for people to get an idea of what I mean
> >>> > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
> >>>
> >>> > > >
> >>> > > > When creating these Release pages my request is that we
> >>> maintain the
> >>> > > page
> >>> > > > hierarchies. For example the release page for the SCA 0.90release
> >>> > > should
> >>> > > > be
> >>> > > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90
> >>> Release.
> >>> > > >
> >>> > > > By the way there is a SCA Java and a SCA Java Subproject page -
> >>> can we
> >>> > > > merge
> >>> > > > these two into one.
> >>> > > >
> >>> > > > Thanks
> >>> > > >
> >>> > > > - Venkat
> >>> > > >
> >>> > > > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> >>> > > > >
> >>> > > > > I am including tuscany-users to get their opinion if
> interested.
> >>> > > > >
> >>> > > > > Here are my thoughts influenced by your comments :)
> >>> > > > > - Separate the download information for latest release from
> >>> the old
> >>> > > > > releases.
> >>> > > > > - Having the text of the change file/read me on the front
> >>> page of
> >>> > the
> >>> > > > > download page is good. This makes it easier to identify what
> >>> is in
> >>> > the
> >>> > > > new
> >>> > > > > release. So, added a section called 'what's new in this
> >>> release'.
> >>> > > > > - It is good to have download information for at least the
> >>> back 2
> >>> > > > > releases.
> >>> > > > >
> >>> > > > > - It is useful to know what level of spec is supported by each
> >>> > > release.
> >>> > > > > For
> >>> > > > > example, for SCA there are several specs. A release can be at
> >>> > Assembly
> >>> > > > > 1.0level and an older version of Client spec.
> >>> > > > > - Having a page that takes user to all the downloads[2] is
> >>> good.
> >>> > > > > - Having a download page per subproject is good since the
> >>> audience
> >>> > > for
> >>> > > > > each
> >>> > > > > download page may be different. For example, someone using
> >>> SDO may
> >>> > not
> >>> > > > > necessarily want to download SCA.
> >>> > > > >
> >>> > > > > Here is an attempt for a sample download page which
> incorporates
> >>> > your
> >>> > > > > feedback [1]
> >>> > > > > User will reach[1] from [2] (not linked yet)
> >>> > > > >
> >>> > > > > [1]
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> >>>
> >>> > > > > [2]
> >>> > >
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> >>> > > > >
> >>> > > > > Does it look OK?
> >>> > > > >
> >>> > > > >
> >>> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> >>> > > > > >
> >>> > > > > > The idea of a single download page sounds good, but if we
> are
> >>> > > thinking
> >>> > > > > > about tracking page visitors to correlate to the number of
> >>> > > downloads,
> >>> > > > > > we won't be able to identify if the person is visiting the
> >>> page to
> >>> > > > > > download SCA, SDO or DAS.
> >>> > > > > >
> >>> > > > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> >>> > > > > > > I agree it would be good to not duplicate things for each
> >>> > > > downloadable
> >>> > > > > > > artifact associated with a release. Not sure it really
> >>> needs the
> >>> > > day
> >>> > > > > of
> >>> > > > > > the
> >>> > > > > > > release or the assembly spec info either.
> >>> > > > > > >
> >>> > > > > > > And +1 to having old release downloads on a separate
> >>> page. I'm
> >>> > not
> >>> > > > > sure
> >>> > > > > > if
> >>> > > > > > > this is the proposal but could there be a single download
> >>> page
> >>> > > that
> >>> > > > > has
> >>> > > > > > the
> >>> > > > > > > current latest release of each of SCA, SDO and DAS?
> >>> > > > > > >
> >>> > > > > > > ...ant
> >>> > > > > > >
> >>> > > > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> >>> > > > > > > >
> >>> > > > > > > > My understanding is that you moved the release name and
> >>> date
> >>> > > from
> >>> > > > > the
> >>> > > > > > > > "download section" to the "download table". If they are
> >>> > always
> >>> > > > same
> >>> > > > > > > > for a group of downloads, won't it take space from the
> >>> page by
> >>> > > > > > > > repeating it on each table row ?
> >>> > > > > > > >
> >>> > > > > > > > Also, do we want to keep all past releases available on
> >>> the
> >>> > main
> >>> > > > > > > > download page ? Maybe we could have an separate archive
> >>> page,
> >>> > > and
> >>> > > > > only
> >>> > > > > > > > the latest release available in the main download page,
> >>> this
> >>> > > would
> >>> > > > > > > > encourage people to always use the latest stable stuff ?
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> >>> > > > > > > > > Hi,
> >>> > > > > > > > >
> >>> > > > > > > > > 1) Would [1] be a better format & content for each
> >>> download
> >>> > > > page
> >>> > > > > > > > of than
> >>> > > > > > > > > what we have today [2]?
> >>> > > > > > > > > If yes, I'll start upgrading the pages.
> >>> > > > > > > > >
> >>> > > > > > > > > 2) We currently use the same page to record download
> >>> info
> >>> > for
> >>> > > > > > > > technologies.
> >>> > > > > > > > > For example, SCA Native and Java download pages are
> the
> >>> > same.
> >>> > > > > > > > > It would be cleaner if we separate the pages. For
> >>> example, a
> >>> > > > Java
> >>> > > > > > SCA
> >>> > > > > > > > and a
> >>> > > > > > > > > Native SCA download page which gets linked to from a
> >>> common
> >>> > > > > > > > > download page entry point [3]
> >>> > > > > > > > > Does this seem reasonable?
> >>> > > > > > > > >
> >>> > > > > > > > >
> >>> > > > > > > > > [1]
> >>> > > > > > > > >
> >>> > > > > > > >
> >>> > > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> >>>
> >>> > > > > > > > > [2]
> >>> > > > >
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> >>> > > > > > > > > [3]
> >>> > > > > >
> >>> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> >>> > > > > > > > >
> >>> > > > > > > > >
> >>> > > > > > > > > Haleh
> >>> > > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > > > --
> >>> > > > > > > > Luciano Resende
> >>> > > > > > > > Apache Tuscany Committer
> >>> > > > > > > > http://people.apache.org/~lresende
> >>> > > > > > > > http://lresende.blogspot.com/
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > >
> >>> >
> ---------------------------------------------------------------------
> >>> > > > > > > > To unsubscribe, e-mail:
> >>> tuscany-dev-unsubscribe@ws.apache.org
> >>> > > > > > > > For additional commands, e-mail:
> >>> > tuscany-dev-help@ws.apache.org
> >>> > > > > > > >
> >>> > > > > > > >
> >>> > > > > > >
> >>> > > > > >
> >>> > > > > >
> >>> > > > > > --
> >>> > > > > > Luciano Resende
> >>> > > > > > Apache Tuscany Committer
> >>> > > > > > http://people.apache.org/~lresende
> >>> > > > > > http://lresende.blogspot.com/
> >>> > > > > >
> >>> > > > > >
> >>> > >
> >>> ---------------------------------------------------------------------
> >>> > > > > > To unsubscribe, e-mail:
> tuscany-dev-unsubscribe@ws.apache.org
> >>> > > > > > For additional commands, e-mail:
> >>> tuscany-dev-help@ws.apache.org
> >>> > > > > >
> >>> > > > > >
> >>> > > > >
> >>> > > >
> >>> > >
> >>> >
> >>>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Wiki Download page cleanup
Posted by Hernan Cunico <hc...@gmail.com>.
Done!
Cheers!
Hernan
Hernan Cunico wrote:
> I'll run a manual autoexport to fix it.
> You should see the changes in about 2 mins
>
> Cheers!
> Hernan
>
> Luciano Resende wrote:
>> Why it shows in [1] and not in [2] ?
>>
>> [1] http://cwiki.apache.org/TUSCANY/home.html
>> [2] http://cwiki.apache.org/TUSCANY/
>>
>>
>> On 5/31/07, Venkata Krishnan <fo...@gmail.com> wrote:
>>> I've changed the home page to include a box highlighting the latest
>>> releases. Let me know if it seems ok
>>>
>>> - Venkat
>>>
>>> On 5/31/07, haleh mahbod <hm...@gmail.com> wrote:
>>> >
>>> > I made the following updates:
>>> > Tuscany Download page, 'SCA Java' is linked to [1]
>>> > on [1], Other release DOWNLOAD is linked to the old Java SCA
>>> Download page
>>> > (old releases)
>>> >
>>> > To do:
>>> > [1] could be renamed to SCA Java Latest Release. This page could
>>> always
>>> > hold
>>> > info about the latest release.
>>> > [2] could be renamed to SCA Java previous Releases.
>>> > [2] needs to be updated to the format that we discussed earlier on
>>> this
>>> > thread
>>> >
>>> > If this looks OK, I go ahead and make the changes for the 'to do'
>>> list.
>>> >
>>> >
>>> > [1]
>>> >
>>> >
>>> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
>>>
>>> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
>>> >
>>> >
>>> > On 5/31/07, ant elder <an...@gmail.com> wrote:
>>> > >
>>> > > Ok, I've added a new download page for the SCA Java 0.90 release
>>> which
>>> > > hopefully isn't to far away from whats been talked about:
>>> > >
>>> > >
>>> > >
>>> >
>>> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
>>>
>>> > >
>>> > > Its not linked to from anywhere yet as I'm not sure after all this
>>> > > discussion where to put it. The main things I think would be good
>>> are to
>>> > > not
>>> > > have to click through many links to get to the actual download
>>> link for
>>> > a
>>> > > latest release and for it to be quite obvious what the current
>>> latest
>>> > > release is of something and its not obscured that with lots of old
>>> > > download
>>> > > links.
>>> > >
>>> > > I wondered if the download page pointed to from the "General"
>>> menu box
>>> > > could
>>> > > be expanded to have links to each of the current download pages
>>> (the
>>> > > above
>>> > > SCA+Java+0.90-incubating etc) and at the bottom another link to a
>>> page
>>> > > with
>>> > > all the old downloads?
>>> > >
>>> > > ...ant
>>> > >
>>> > > On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
>>> > > >
>>> > > > Hi
>>> > > >
>>> > > > What we are attempting to do now it really far better than
>>> cluttering
>>> > > all
>>> > > > the downloads together on one page. Here is what I think about
>>> this
>>> > > >
>>> > > > - for every Release (SCA / SDO / DAS) have a separate page
>>> whose first
>>> > > > section talks about what comprises of that release (including spec
>>> > > levels
>>> > > > etc.) and then have a next section that is titled 'Downloads'.
>>> > > > - then have a single page titled 'Releases' where we list all the
>>> > > releases
>>> > > > and each entry is a link to the separate Release page. Here
>>> again we
>>> > > > could
>>> > > > choose to have SCA Releases, SDO Releases, DAS Releases on
>>> diff. pages
>>> > > or
>>> > > > just have all in one under diff sections.
>>> > > > - Finally from the global home page and the home page of the
>>> > subprojects
>>> > > > have a menu item 'Releases' that will point to the 'Releases'
>>> page.
>>> > > >
>>> > > > This way, with every release we simply have to go an make the
>>> specific
>>> > > > release page and add a link to the Releases page. I had
>>> created a
>>> > > > Release
>>> > > > page for the recent SDO Release without the Downloads section
>>> > > > though. Here
>>> > > > it is just for people to get an idea of what I mean
>>> > > >
>>> > > >
>>> > >
>>> >
>>> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
>>>
>>> > > >
>>> > > > When creating these Release pages my request is that we
>>> maintain the
>>> > > page
>>> > > > hierarchies. For example the release page for the SCA 0.90 release
>>> > > should
>>> > > > be
>>> > > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90
>>> Release.
>>> > > >
>>> > > > By the way there is a SCA Java and a SCA Java Subproject page -
>>> can we
>>> > > > merge
>>> > > > these two into one.
>>> > > >
>>> > > > Thanks
>>> > > >
>>> > > > - Venkat
>>> > > >
>>> > > > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
>>> > > > >
>>> > > > > I am including tuscany-users to get their opinion if interested.
>>> > > > >
>>> > > > > Here are my thoughts influenced by your comments :)
>>> > > > > - Separate the download information for latest release from
>>> the old
>>> > > > > releases.
>>> > > > > - Having the text of the change file/read me on the front
>>> page of
>>> > the
>>> > > > > download page is good. This makes it easier to identify what
>>> is in
>>> > the
>>> > > > new
>>> > > > > release. So, added a section called 'what's new in this
>>> release'.
>>> > > > > - It is good to have download information for at least the
>>> back 2
>>> > > > > releases.
>>> > > > >
>>> > > > > - It is useful to know what level of spec is supported by each
>>> > > release.
>>> > > > > For
>>> > > > > example, for SCA there are several specs. A release can be at
>>> > Assembly
>>> > > > > 1.0level and an older version of Client spec.
>>> > > > > - Having a page that takes user to all the downloads[2] is
>>> good.
>>> > > > > - Having a download page per subproject is good since the
>>> audience
>>> > > for
>>> > > > > each
>>> > > > > download page may be different. For example, someone using
>>> SDO may
>>> > not
>>> > > > > necessarily want to download SCA.
>>> > > > >
>>> > > > > Here is an attempt for a sample download page which incorporates
>>> > your
>>> > > > > feedback [1]
>>> > > > > User will reach[1] from [2] (not linked yet)
>>> > > > >
>>> > > > > [1]
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
>>>
>>> > > > > [2]
>>> > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>>> > > > >
>>> > > > > Does it look OK?
>>> > > > >
>>> > > > >
>>> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>>> > > > > >
>>> > > > > > The idea of a single download page sounds good, but if we are
>>> > > thinking
>>> > > > > > about tracking page visitors to correlate to the number of
>>> > > downloads,
>>> > > > > > we won't be able to identify if the person is visiting the
>>> page to
>>> > > > > > download SCA, SDO or DAS.
>>> > > > > >
>>> > > > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
>>> > > > > > > I agree it would be good to not duplicate things for each
>>> > > > downloadable
>>> > > > > > > artifact associated with a release. Not sure it really
>>> needs the
>>> > > day
>>> > > > > of
>>> > > > > > the
>>> > > > > > > release or the assembly spec info either.
>>> > > > > > >
>>> > > > > > > And +1 to having old release downloads on a separate
>>> page. I'm
>>> > not
>>> > > > > sure
>>> > > > > > if
>>> > > > > > > this is the proposal but could there be a single download
>>> page
>>> > > that
>>> > > > > has
>>> > > > > > the
>>> > > > > > > current latest release of each of SCA, SDO and DAS?
>>> > > > > > >
>>> > > > > > > ...ant
>>> > > > > > >
>>> > > > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>>> > > > > > > >
>>> > > > > > > > My understanding is that you moved the release name and
>>> date
>>> > > from
>>> > > > > the
>>> > > > > > > > "download section" to the "download table". If they are
>>> > always
>>> > > > same
>>> > > > > > > > for a group of downloads, won't it take space from the
>>> page by
>>> > > > > > > > repeating it on each table row ?
>>> > > > > > > >
>>> > > > > > > > Also, do we want to keep all past releases available on
>>> the
>>> > main
>>> > > > > > > > download page ? Maybe we could have an separate archive
>>> page,
>>> > > and
>>> > > > > only
>>> > > > > > > > the latest release available in the main download page,
>>> this
>>> > > would
>>> > > > > > > > encourage people to always use the latest stable stuff ?
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
>>> > > > > > > > > Hi,
>>> > > > > > > > >
>>> > > > > > > > > 1) Would [1] be a better format & content for each
>>> download
>>> > > > page
>>> > > > > > > > of than
>>> > > > > > > > > what we have today [2]?
>>> > > > > > > > > If yes, I'll start upgrading the pages.
>>> > > > > > > > >
>>> > > > > > > > > 2) We currently use the same page to record download
>>> info
>>> > for
>>> > > > > > > > technologies.
>>> > > > > > > > > For example, SCA Native and Java download pages are the
>>> > same.
>>> > > > > > > > > It would be cleaner if we separate the pages. For
>>> example, a
>>> > > > Java
>>> > > > > > SCA
>>> > > > > > > > and a
>>> > > > > > > > > Native SCA download page which gets linked to from a
>>> common
>>> > > > > > > > > download page entry point [3]
>>> > > > > > > > > Does this seem reasonable?
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > [1]
>>> > > > > > > > >
>>> > > > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
>>>
>>> > > > > > > > > [2]
>>> > > > > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
>>> > > > > > > > > [3]
>>> > > > > >
>>> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>>> > > > > > > > >
>>> > > > > > > > >
>>> > > > > > > > > Haleh
>>> > > > > > > > >
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > > > --
>>> > > > > > > > Luciano Resende
>>> > > > > > > > Apache Tuscany Committer
>>> > > > > > > > http://people.apache.org/~lresende
>>> > > > > > > > http://lresende.blogspot.com/
>>> > > > > > > >
>>> > > > > > > >
>>> > > > >
>>> > ---------------------------------------------------------------------
>>> > > > > > > > To unsubscribe, e-mail:
>>> tuscany-dev-unsubscribe@ws.apache.org
>>> > > > > > > > For additional commands, e-mail:
>>> > tuscany-dev-help@ws.apache.org
>>> > > > > > > >
>>> > > > > > > >
>>> > > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > --
>>> > > > > > Luciano Resende
>>> > > > > > Apache Tuscany Committer
>>> > > > > > http://people.apache.org/~lresende
>>> > > > > > http://lresende.blogspot.com/
>>> > > > > >
>>> > > > > >
>>> > >
>>> ---------------------------------------------------------------------
>>> > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>>> > > > > > For additional commands, e-mail:
>>> tuscany-dev-help@ws.apache.org
>>> > > > > >
>>> > > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by Hernan Cunico <hc...@gmail.com>.
I'll run a manual autoexport to fix it.
You should see the changes in about 2 mins
Cheers!
Hernan
Luciano Resende wrote:
> Why it shows in [1] and not in [2] ?
>
> [1] http://cwiki.apache.org/TUSCANY/home.html
> [2] http://cwiki.apache.org/TUSCANY/
>
>
> On 5/31/07, Venkata Krishnan <fo...@gmail.com> wrote:
>> I've changed the home page to include a box highlighting the latest
>> releases. Let me know if it seems ok
>>
>> - Venkat
>>
>> On 5/31/07, haleh mahbod <hm...@gmail.com> wrote:
>> >
>> > I made the following updates:
>> > Tuscany Download page, 'SCA Java' is linked to [1]
>> > on [1], Other release DOWNLOAD is linked to the old Java SCA
>> Download page
>> > (old releases)
>> >
>> > To do:
>> > [1] could be renamed to SCA Java Latest Release. This page could always
>> > hold
>> > info about the latest release.
>> > [2] could be renamed to SCA Java previous Releases.
>> > [2] needs to be updated to the format that we discussed earlier on this
>> > thread
>> >
>> > If this looks OK, I go ahead and make the changes for the 'to do' list.
>> >
>> >
>> > [1]
>> >
>> >
>> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
>>
>> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
>> >
>> >
>> > On 5/31/07, ant elder <an...@gmail.com> wrote:
>> > >
>> > > Ok, I've added a new download page for the SCA Java 0.90 release
>> which
>> > > hopefully isn't to far away from whats been talked about:
>> > >
>> > >
>> > >
>> >
>> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
>>
>> > >
>> > > Its not linked to from anywhere yet as I'm not sure after all this
>> > > discussion where to put it. The main things I think would be good
>> are to
>> > > not
>> > > have to click through many links to get to the actual download
>> link for
>> > a
>> > > latest release and for it to be quite obvious what the current latest
>> > > release is of something and its not obscured that with lots of old
>> > > download
>> > > links.
>> > >
>> > > I wondered if the download page pointed to from the "General" menu
>> box
>> > > could
>> > > be expanded to have links to each of the current download pages (the
>> > > above
>> > > SCA+Java+0.90-incubating etc) and at the bottom another link to a
>> page
>> > > with
>> > > all the old downloads?
>> > >
>> > > ...ant
>> > >
>> > > On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
>> > > >
>> > > > Hi
>> > > >
>> > > > What we are attempting to do now it really far better than
>> cluttering
>> > > all
>> > > > the downloads together on one page. Here is what I think about
>> this
>> > > >
>> > > > - for every Release (SCA / SDO / DAS) have a separate page whose
>> first
>> > > > section talks about what comprises of that release (including spec
>> > > levels
>> > > > etc.) and then have a next section that is titled 'Downloads'.
>> > > > - then have a single page titled 'Releases' where we list all the
>> > > releases
>> > > > and each entry is a link to the separate Release page. Here
>> again we
>> > > > could
>> > > > choose to have SCA Releases, SDO Releases, DAS Releases on diff.
>> pages
>> > > or
>> > > > just have all in one under diff sections.
>> > > > - Finally from the global home page and the home page of the
>> > subprojects
>> > > > have a menu item 'Releases' that will point to the 'Releases' page.
>> > > >
>> > > > This way, with every release we simply have to go an make the
>> specific
>> > > > release page and add a link to the Releases page. I had created a
>> > > > Release
>> > > > page for the recent SDO Release without the Downloads section
>> > > > though. Here
>> > > > it is just for people to get an idea of what I mean
>> > > >
>> > > >
>> > >
>> >
>> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
>>
>> > > >
>> > > > When creating these Release pages my request is that we maintain
>> the
>> > > page
>> > > > hierarchies. For example the release page for the SCA 0.90 release
>> > > should
>> > > > be
>> > > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90
>> Release.
>> > > >
>> > > > By the way there is a SCA Java and a SCA Java Subproject page -
>> can we
>> > > > merge
>> > > > these two into one.
>> > > >
>> > > > Thanks
>> > > >
>> > > > - Venkat
>> > > >
>> > > > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
>> > > > >
>> > > > > I am including tuscany-users to get their opinion if interested.
>> > > > >
>> > > > > Here are my thoughts influenced by your comments :)
>> > > > > - Separate the download information for latest release from
>> the old
>> > > > > releases.
>> > > > > - Having the text of the change file/read me on the front
>> page of
>> > the
>> > > > > download page is good. This makes it easier to identify what
>> is in
>> > the
>> > > > new
>> > > > > release. So, added a section called 'what's new in this release'.
>> > > > > - It is good to have download information for at least the
>> back 2
>> > > > > releases.
>> > > > >
>> > > > > - It is useful to know what level of spec is supported by each
>> > > release.
>> > > > > For
>> > > > > example, for SCA there are several specs. A release can be at
>> > Assembly
>> > > > > 1.0level and an older version of Client spec.
>> > > > > - Having a page that takes user to all the downloads[2] is good.
>> > > > > - Having a download page per subproject is good since the
>> audience
>> > > for
>> > > > > each
>> > > > > download page may be different. For example, someone using SDO
>> may
>> > not
>> > > > > necessarily want to download SCA.
>> > > > >
>> > > > > Here is an attempt for a sample download page which incorporates
>> > your
>> > > > > feedback [1]
>> > > > > User will reach[1] from [2] (not linked yet)
>> > > > >
>> > > > > [1]
>> > > > >
>> > > >
>> > >
>> >
>> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
>> > > > > [2]
>> > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>> > > > >
>> > > > > Does it look OK?
>> > > > >
>> > > > >
>> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>> > > > > >
>> > > > > > The idea of a single download page sounds good, but if we are
>> > > thinking
>> > > > > > about tracking page visitors to correlate to the number of
>> > > downloads,
>> > > > > > we won't be able to identify if the person is visiting the
>> page to
>> > > > > > download SCA, SDO or DAS.
>> > > > > >
>> > > > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
>> > > > > > > I agree it would be good to not duplicate things for each
>> > > > downloadable
>> > > > > > > artifact associated with a release. Not sure it really
>> needs the
>> > > day
>> > > > > of
>> > > > > > the
>> > > > > > > release or the assembly spec info either.
>> > > > > > >
>> > > > > > > And +1 to having old release downloads on a separate page.
>> I'm
>> > not
>> > > > > sure
>> > > > > > if
>> > > > > > > this is the proposal but could there be a single download
>> page
>> > > that
>> > > > > has
>> > > > > > the
>> > > > > > > current latest release of each of SCA, SDO and DAS?
>> > > > > > >
>> > > > > > > ...ant
>> > > > > > >
>> > > > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>> > > > > > > >
>> > > > > > > > My understanding is that you moved the release name and
>> date
>> > > from
>> > > > > the
>> > > > > > > > "download section" to the "download table". If they are
>> > always
>> > > > same
>> > > > > > > > for a group of downloads, won't it take space from the
>> page by
>> > > > > > > > repeating it on each table row ?
>> > > > > > > >
>> > > > > > > > Also, do we want to keep all past releases available on the
>> > main
>> > > > > > > > download page ? Maybe we could have an separate archive
>> page,
>> > > and
>> > > > > only
>> > > > > > > > the latest release available in the main download page,
>> this
>> > > would
>> > > > > > > > encourage people to always use the latest stable stuff ?
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
>> > > > > > > > > Hi,
>> > > > > > > > >
>> > > > > > > > > 1) Would [1] be a better format & content for each
>> download
>> > > > page
>> > > > > > > > of than
>> > > > > > > > > what we have today [2]?
>> > > > > > > > > If yes, I'll start upgrading the pages.
>> > > > > > > > >
>> > > > > > > > > 2) We currently use the same page to record download info
>> > for
>> > > > > > > > technologies.
>> > > > > > > > > For example, SCA Native and Java download pages are the
>> > same.
>> > > > > > > > > It would be cleaner if we separate the pages. For
>> example, a
>> > > > Java
>> > > > > > SCA
>> > > > > > > > and a
>> > > > > > > > > Native SCA download page which gets linked to from a
>> common
>> > > > > > > > > download page entry point [3]
>> > > > > > > > > Does this seem reasonable?
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > [1]
>> > > > > > > > >
>> > > > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
>> > > > > > > > > [2]
>> > > > > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
>> > > > > > > > > [3]
>> > > > > >
>> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>> > > > > > > > >
>> > > > > > > > >
>> > > > > > > > > Haleh
>> > > > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > --
>> > > > > > > > Luciano Resende
>> > > > > > > > Apache Tuscany Committer
>> > > > > > > > http://people.apache.org/~lresende
>> > > > > > > > http://lresende.blogspot.com/
>> > > > > > > >
>> > > > > > > >
>> > > > >
>> > ---------------------------------------------------------------------
>> > > > > > > > To unsubscribe, e-mail:
>> tuscany-dev-unsubscribe@ws.apache.org
>> > > > > > > > For additional commands, e-mail:
>> > tuscany-dev-help@ws.apache.org
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > Luciano Resende
>> > > > > > Apache Tuscany Committer
>> > > > > > http://people.apache.org/~lresende
>> > > > > > http://lresende.blogspot.com/
>> > > > > >
>> > > > > >
>> > > ---------------------------------------------------------------------
>> > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> > > > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by Luciano Resende <lu...@gmail.com>.
Why it shows in [1] and not in [2] ?
[1] http://cwiki.apache.org/TUSCANY/home.html
[2] http://cwiki.apache.org/TUSCANY/
On 5/31/07, Venkata Krishnan <fo...@gmail.com> wrote:
> I've changed the home page to include a box highlighting the latest
> releases. Let me know if it seems ok
>
> - Venkat
>
> On 5/31/07, haleh mahbod <hm...@gmail.com> wrote:
> >
> > I made the following updates:
> > Tuscany Download page, 'SCA Java' is linked to [1]
> > on [1], Other release DOWNLOAD is linked to the old Java SCA Download page
> > (old releases)
> >
> > To do:
> > [1] could be renamed to SCA Java Latest Release. This page could always
> > hold
> > info about the latest release.
> > [2] could be renamed to SCA Java previous Releases.
> > [2] needs to be updated to the format that we discussed earlier on this
> > thread
> >
> > If this looks OK, I go ahead and make the changes for the 'to do' list.
> >
> >
> > [1]
> >
> > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> >
> >
> > On 5/31/07, ant elder <an...@gmail.com> wrote:
> > >
> > > Ok, I've added a new download page for the SCA Java 0.90 release which
> > > hopefully isn't to far away from whats been talked about:
> > >
> > >
> > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> > >
> > > Its not linked to from anywhere yet as I'm not sure after all this
> > > discussion where to put it. The main things I think would be good are to
> > > not
> > > have to click through many links to get to the actual download link for
> > a
> > > latest release and for it to be quite obvious what the current latest
> > > release is of something and its not obscured that with lots of old
> > > download
> > > links.
> > >
> > > I wondered if the download page pointed to from the "General" menu box
> > > could
> > > be expanded to have links to each of the current download pages (the
> > > above
> > > SCA+Java+0.90-incubating etc) and at the bottom another link to a page
> > > with
> > > all the old downloads?
> > >
> > > ...ant
> > >
> > > On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
> > > >
> > > > Hi
> > > >
> > > > What we are attempting to do now it really far better than cluttering
> > > all
> > > > the downloads together on one page. Here is what I think about this
> > > >
> > > > - for every Release (SCA / SDO / DAS) have a separate page whose first
> > > > section talks about what comprises of that release (including spec
> > > levels
> > > > etc.) and then have a next section that is titled 'Downloads'.
> > > > - then have a single page titled 'Releases' where we list all the
> > > releases
> > > > and each entry is a link to the separate Release page. Here again we
> > > > could
> > > > choose to have SCA Releases, SDO Releases, DAS Releases on diff. pages
> > > or
> > > > just have all in one under diff sections.
> > > > - Finally from the global home page and the home page of the
> > subprojects
> > > > have a menu item 'Releases' that will point to the 'Releases' page.
> > > >
> > > > This way, with every release we simply have to go an make the specific
> > > > release page and add a link to the Releases page. I had created a
> > > > Release
> > > > page for the recent SDO Release without the Downloads section
> > > > though. Here
> > > > it is just for people to get an idea of what I mean
> > > >
> > > >
> > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
> > > >
> > > > When creating these Release pages my request is that we maintain the
> > > page
> > > > hierarchies. For example the release page for the SCA 0.90 release
> > > should
> > > > be
> > > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 Release.
> > > >
> > > > By the way there is a SCA Java and a SCA Java Subproject page - can we
> > > > merge
> > > > these two into one.
> > > >
> > > > Thanks
> > > >
> > > > - Venkat
> > > >
> > > > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > >
> > > > > I am including tuscany-users to get their opinion if interested.
> > > > >
> > > > > Here are my thoughts influenced by your comments :)
> > > > > - Separate the download information for latest release from the old
> > > > > releases.
> > > > > - Having the text of the change file/read me on the front page of
> > the
> > > > > download page is good. This makes it easier to identify what is in
> > the
> > > > new
> > > > > release. So, added a section called 'what's new in this release'.
> > > > > - It is good to have download information for at least the back 2
> > > > > releases.
> > > > >
> > > > > - It is useful to know what level of spec is supported by each
> > > release.
> > > > > For
> > > > > example, for SCA there are several specs. A release can be at
> > Assembly
> > > > > 1.0level and an older version of Client spec.
> > > > > - Having a page that takes user to all the downloads[2] is good.
> > > > > - Having a download page per subproject is good since the audience
> > > for
> > > > > each
> > > > > download page may be different. For example, someone using SDO may
> > not
> > > > > necessarily want to download SCA.
> > > > >
> > > > > Here is an attempt for a sample download page which incorporates
> > your
> > > > > feedback [1]
> > > > > User will reach[1] from [2] (not linked yet)
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > [2]
> > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > >
> > > > > Does it look OK?
> > > > >
> > > > >
> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > > >
> > > > > > The idea of a single download page sounds good, but if we are
> > > thinking
> > > > > > about tracking page visitors to correlate to the number of
> > > downloads,
> > > > > > we won't be able to identify if the person is visiting the page to
> > > > > > download SCA, SDO or DAS.
> > > > > >
> > > > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > > > > > I agree it would be good to not duplicate things for each
> > > > downloadable
> > > > > > > artifact associated with a release. Not sure it really needs the
> > > day
> > > > > of
> > > > > > the
> > > > > > > release or the assembly spec info either.
> > > > > > >
> > > > > > > And +1 to having old release downloads on a separate page. I'm
> > not
> > > > > sure
> > > > > > if
> > > > > > > this is the proposal but could there be a single download page
> > > that
> > > > > has
> > > > > > the
> > > > > > > current latest release of each of SCA, SDO and DAS?
> > > > > > >
> > > > > > > ...ant
> > > > > > >
> > > > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > > > > >
> > > > > > > > My understanding is that you moved the release name and date
> > > from
> > > > > the
> > > > > > > > "download section" to the "download table". If they are
> > always
> > > > same
> > > > > > > > for a group of downloads, won't it take space from the page by
> > > > > > > > repeating it on each table row ?
> > > > > > > >
> > > > > > > > Also, do we want to keep all past releases available on the
> > main
> > > > > > > > download page ? Maybe we could have an separate archive page,
> > > and
> > > > > only
> > > > > > > > the latest release available in the main download page, this
> > > would
> > > > > > > > encourage people to always use the latest stable stuff ?
> > > > > > > >
> > > > > > > >
> > > > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > 1) Would [1] be a better format & content for each download
> > > > page
> > > > > > > > of than
> > > > > > > > > what we have today [2]?
> > > > > > > > > If yes, I'll start upgrading the pages.
> > > > > > > > >
> > > > > > > > > 2) We currently use the same page to record download info
> > for
> > > > > > > > technologies.
> > > > > > > > > For example, SCA Native and Java download pages are the
> > same.
> > > > > > > > > It would be cleaner if we separate the pages. For example, a
> > > > Java
> > > > > > SCA
> > > > > > > > and a
> > > > > > > > > Native SCA download page which gets linked to from a common
> > > > > > > > > download page entry point [3]
> > > > > > > > > Does this seem reasonable?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1]
> > > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > > > > > [2]
> > > > > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > > > > > [3]
> > > > > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Haleh
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Luciano Resende
> > > > > > > > Apache Tuscany Committer
> > > > > > > > http://people.apache.org/~lresende
> > > > > > > > http://lresende.blogspot.com/
> > > > > > > >
> > > > > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > > > > For additional commands, e-mail:
> > tuscany-dev-help@ws.apache.org
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Luciano Resende
> > > > > > Apache Tuscany Committer
> > > > > > http://people.apache.org/~lresende
> > > > > > http://lresende.blogspot.com/
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by Venkata Krishnan <fo...@gmail.com>.
I've changed the home page to include a box highlighting the latest
releases. Let me know if it seems ok
- Venkat
On 5/31/07, haleh mahbod <hm...@gmail.com> wrote:
>
> I made the following updates:
> Tuscany Download page, 'SCA Java' is linked to [1]
> on [1], Other release DOWNLOAD is linked to the old Java SCA Download page
> (old releases)
>
> To do:
> [1] could be renamed to SCA Java Latest Release. This page could always
> hold
> info about the latest release.
> [2] could be renamed to SCA Java previous Releases.
> [2] needs to be updated to the format that we discussed earlier on this
> thread
>
> If this looks OK, I go ahead and make the changes for the 'to do' list.
>
>
> [1]
>
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
>
>
> On 5/31/07, ant elder <an...@gmail.com> wrote:
> >
> > Ok, I've added a new download page for the SCA Java 0.90 release which
> > hopefully isn't to far away from whats been talked about:
> >
> >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
> >
> > Its not linked to from anywhere yet as I'm not sure after all this
> > discussion where to put it. The main things I think would be good are to
> > not
> > have to click through many links to get to the actual download link for
> a
> > latest release and for it to be quite obvious what the current latest
> > release is of something and its not obscured that with lots of old
> > download
> > links.
> >
> > I wondered if the download page pointed to from the "General" menu box
> > could
> > be expanded to have links to each of the current download pages (the
> > above
> > SCA+Java+0.90-incubating etc) and at the bottom another link to a page
> > with
> > all the old downloads?
> >
> > ...ant
> >
> > On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
> > >
> > > Hi
> > >
> > > What we are attempting to do now it really far better than cluttering
> > all
> > > the downloads together on one page. Here is what I think about this
> > >
> > > - for every Release (SCA / SDO / DAS) have a separate page whose first
> > > section talks about what comprises of that release (including spec
> > levels
> > > etc.) and then have a next section that is titled 'Downloads'.
> > > - then have a single page titled 'Releases' where we list all the
> > releases
> > > and each entry is a link to the separate Release page. Here again we
> > > could
> > > choose to have SCA Releases, SDO Releases, DAS Releases on diff. pages
> > or
> > > just have all in one under diff sections.
> > > - Finally from the global home page and the home page of the
> subprojects
> > > have a menu item 'Releases' that will point to the 'Releases' page.
> > >
> > > This way, with every release we simply have to go an make the specific
> > > release page and add a link to the Releases page. I had created a
> > > Release
> > > page for the recent SDO Release without the Downloads section
> > > though. Here
> > > it is just for people to get an idea of what I mean
> > >
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
> > >
> > > When creating these Release pages my request is that we maintain the
> > page
> > > hierarchies. For example the release page for the SCA 0.90 release
> > should
> > > be
> > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 Release.
> > >
> > > By the way there is a SCA Java and a SCA Java Subproject page - can we
> > > merge
> > > these two into one.
> > >
> > > Thanks
> > >
> > > - Venkat
> > >
> > > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> > > >
> > > > I am including tuscany-users to get their opinion if interested.
> > > >
> > > > Here are my thoughts influenced by your comments :)
> > > > - Separate the download information for latest release from the old
> > > > releases.
> > > > - Having the text of the change file/read me on the front page of
> the
> > > > download page is good. This makes it easier to identify what is in
> the
> > > new
> > > > release. So, added a section called 'what's new in this release'.
> > > > - It is good to have download information for at least the back 2
> > > > releases.
> > > >
> > > > - It is useful to know what level of spec is supported by each
> > release.
> > > > For
> > > > example, for SCA there are several specs. A release can be at
> Assembly
> > > > 1.0level and an older version of Client spec.
> > > > - Having a page that takes user to all the downloads[2] is good.
> > > > - Having a download page per subproject is good since the audience
> > for
> > > > each
> > > > download page may be different. For example, someone using SDO may
> not
> > > > necessarily want to download SCA.
> > > >
> > > > Here is an attempt for a sample download page which incorporates
> your
> > > > feedback [1]
> > > > User will reach[1] from [2] (not linked yet)
> > > >
> > > > [1]
> > > >
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > [2]
> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > >
> > > > Does it look OK?
> > > >
> > > >
> > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > >
> > > > > The idea of a single download page sounds good, but if we are
> > thinking
> > > > > about tracking page visitors to correlate to the number of
> > downloads,
> > > > > we won't be able to identify if the person is visiting the page to
> > > > > download SCA, SDO or DAS.
> > > > >
> > > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > > > > I agree it would be good to not duplicate things for each
> > > downloadable
> > > > > > artifact associated with a release. Not sure it really needs the
> > day
> > > > of
> > > > > the
> > > > > > release or the assembly spec info either.
> > > > > >
> > > > > > And +1 to having old release downloads on a separate page. I'm
> not
> > > > sure
> > > > > if
> > > > > > this is the proposal but could there be a single download page
> > that
> > > > has
> > > > > the
> > > > > > current latest release of each of SCA, SDO and DAS?
> > > > > >
> > > > > > ...ant
> > > > > >
> > > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > > > >
> > > > > > > My understanding is that you moved the release name and date
> > from
> > > > the
> > > > > > > "download section" to the "download table". If they are
> always
> > > same
> > > > > > > for a group of downloads, won't it take space from the page by
> > > > > > > repeating it on each table row ?
> > > > > > >
> > > > > > > Also, do we want to keep all past releases available on the
> main
> > > > > > > download page ? Maybe we could have an separate archive page,
> > and
> > > > only
> > > > > > > the latest release available in the main download page, this
> > would
> > > > > > > encourage people to always use the latest stable stuff ?
> > > > > > >
> > > > > > >
> > > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > 1) Would [1] be a better format & content for each download
> > > page
> > > > > > > of than
> > > > > > > > what we have today [2]?
> > > > > > > > If yes, I'll start upgrading the pages.
> > > > > > > >
> > > > > > > > 2) We currently use the same page to record download info
> for
> > > > > > > technologies.
> > > > > > > > For example, SCA Native and Java download pages are the
> same.
> > > > > > > > It would be cleaner if we separate the pages. For example, a
> > > Java
> > > > > SCA
> > > > > > > and a
> > > > > > > > Native SCA download page which gets linked to from a common
> > > > > > > > download page entry point [3]
> > > > > > > > Does this seem reasonable?
> > > > > > > >
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > >
> > > > >
> > > >
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > > > > [2]
> > > > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > > > > [3]
> > > > >
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > > > > >
> > > > > > > >
> > > > > > > > Haleh
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Luciano Resende
> > > > > > > Apache Tuscany Committer
> > > > > > > http://people.apache.org/~lresende
> > > > > > > http://lresende.blogspot.com/
> > > > > > >
> > > > > > >
> > > >
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > > > For additional commands, e-mail:
> tuscany-dev-help@ws.apache.org
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Luciano Resende
> > > > > Apache Tuscany Committer
> > > > > http://people.apache.org/~lresende
> > > > > http://lresende.blogspot.com/
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Wiki Download page cleanup
Posted by haleh mahbod <hm...@gmail.com>.
I made the following updates:
Tuscany Download page, 'SCA Java' is linked to [1]
on [1], Other release DOWNLOAD is linked to the old Java SCA Download page
(old releases)
To do:
[1] could be renamed to SCA Java Latest Release. This page could always hold
info about the latest release.
[2] could be renamed to SCA Java previous Releases.
[2] needs to be updated to the format that we discussed earlier on this
thread
If this looks OK, I go ahead and make the changes for the 'to do' list.
[1]
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
[2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
On 5/31/07, ant elder <an...@gmail.com> wrote:
>
> Ok, I've added a new download page for the SCA Java 0.90 release which
> hopefully isn't to far away from whats been talked about:
>
>
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
>
> Its not linked to from anywhere yet as I'm not sure after all this
> discussion where to put it. The main things I think would be good are to
> not
> have to click through many links to get to the actual download link for a
> latest release and for it to be quite obvious what the current latest
> release is of something and its not obscured that with lots of old
> download
> links.
>
> I wondered if the download page pointed to from the "General" menu box
> could
> be expanded to have links to each of the current download pages (the
> above
> SCA+Java+0.90-incubating etc) and at the bottom another link to a page
> with
> all the old downloads?
>
> ...ant
>
> On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
> >
> > Hi
> >
> > What we are attempting to do now it really far better than cluttering
> all
> > the downloads together on one page. Here is what I think about this
> >
> > - for every Release (SCA / SDO / DAS) have a separate page whose first
> > section talks about what comprises of that release (including spec
> levels
> > etc.) and then have a next section that is titled 'Downloads'.
> > - then have a single page titled 'Releases' where we list all the
> releases
> > and each entry is a link to the separate Release page. Here again we
> > could
> > choose to have SCA Releases, SDO Releases, DAS Releases on diff. pages
> or
> > just have all in one under diff sections.
> > - Finally from the global home page and the home page of the subprojects
> > have a menu item 'Releases' that will point to the 'Releases' page.
> >
> > This way, with every release we simply have to go an make the specific
> > release page and add a link to the Releases page. I had created a
> > Release
> > page for the recent SDO Release without the Downloads section
> > though. Here
> > it is just for people to get an idea of what I mean
> >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
> >
> > When creating these Release pages my request is that we maintain the
> page
> > hierarchies. For example the release page for the SCA 0.90 release
> should
> > be
> > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 Release.
> >
> > By the way there is a SCA Java and a SCA Java Subproject page - can we
> > merge
> > these two into one.
> >
> > Thanks
> >
> > - Venkat
> >
> > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> > >
> > > I am including tuscany-users to get their opinion if interested.
> > >
> > > Here are my thoughts influenced by your comments :)
> > > - Separate the download information for latest release from the old
> > > releases.
> > > - Having the text of the change file/read me on the front page of the
> > > download page is good. This makes it easier to identify what is in the
> > new
> > > release. So, added a section called 'what's new in this release'.
> > > - It is good to have download information for at least the back 2
> > > releases.
> > >
> > > - It is useful to know what level of spec is supported by each
> release.
> > > For
> > > example, for SCA there are several specs. A release can be at Assembly
> > > 1.0level and an older version of Client spec.
> > > - Having a page that takes user to all the downloads[2] is good.
> > > - Having a download page per subproject is good since the audience
> for
> > > each
> > > download page may be different. For example, someone using SDO may not
> > > necessarily want to download SCA.
> > >
> > > Here is an attempt for a sample download page which incorporates your
> > > feedback [1]
> > > User will reach[1] from [2] (not linked yet)
> > >
> > > [1]
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > [2]
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > >
> > > Does it look OK?
> > >
> > >
> > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > >
> > > > The idea of a single download page sounds good, but if we are
> thinking
> > > > about tracking page visitors to correlate to the number of
> downloads,
> > > > we won't be able to identify if the person is visiting the page to
> > > > download SCA, SDO or DAS.
> > > >
> > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > > > I agree it would be good to not duplicate things for each
> > downloadable
> > > > > artifact associated with a release. Not sure it really needs the
> day
> > > of
> > > > the
> > > > > release or the assembly spec info either.
> > > > >
> > > > > And +1 to having old release downloads on a separate page. I'm not
> > > sure
> > > > if
> > > > > this is the proposal but could there be a single download page
> that
> > > has
> > > > the
> > > > > current latest release of each of SCA, SDO and DAS?
> > > > >
> > > > > ...ant
> > > > >
> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > > >
> > > > > > My understanding is that you moved the release name and date
> from
> > > the
> > > > > > "download section" to the "download table". If they are always
> > same
> > > > > > for a group of downloads, won't it take space from the page by
> > > > > > repeating it on each table row ?
> > > > > >
> > > > > > Also, do we want to keep all past releases available on the main
> > > > > > download page ? Maybe we could have an separate archive page,
> and
> > > only
> > > > > > the latest release available in the main download page, this
> would
> > > > > > encourage people to always use the latest stable stuff ?
> > > > > >
> > > > > >
> > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > 1) Would [1] be a better format & content for each download
> > page
> > > > > > of than
> > > > > > > what we have today [2]?
> > > > > > > If yes, I'll start upgrading the pages.
> > > > > > >
> > > > > > > 2) We currently use the same page to record download info for
> > > > > > technologies.
> > > > > > > For example, SCA Native and Java download pages are the same.
> > > > > > > It would be cleaner if we separate the pages. For example, a
> > Java
> > > > SCA
> > > > > > and a
> > > > > > > Native SCA download page which gets linked to from a common
> > > > > > > download page entry point [3]
> > > > > > > Does this seem reasonable?
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > >
> > > >
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > > > [2]
> > > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > > > [3]
> > > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > > > >
> > > > > > >
> > > > > > > Haleh
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Luciano Resende
> > > > > > Apache Tuscany Committer
> > > > > > http://people.apache.org/~lresende
> > > > > > http://lresende.blogspot.com/
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > Apache Tuscany Committer
> > > > http://people.apache.org/~lresende
> > > > http://lresende.blogspot.com/
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > >
> > > >
> > >
> >
>
Re: Wiki Download page cleanup
Posted by Venkata Krishnan <fo...@gmail.com>.
HI Ant,
This looks in line with what I am imagining. I have linked up this page to
a SCA Releases page
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Releases. The SCA
Releases pages is futher linked to a Menu Item called 'SCA Releases' under
the Tuscany SCA menu box.
On the SCA Releases page we could list all the SCA Releases - Java, PHP, C++
all under separate sections though. Right now there is just for SCA Java
Releases with a single entry :)
The Tuscany Downloads page can have two sections 1) Latest Releases (where
will link up the latest release pages one of which is the one you have just
made) 2) Other Releases (where will simply include (using the includ macro)
the SCA Releases, SDO Release and DAS Releases pages)
So for a release - say an SCA release, we need to create a page for the
Release, then add it to the list of links under SCA Releases and update the
Tuscany Downloads page to show it as one of the latest releases.
Finally, when creating a Release page we need to ensure that we create it in
the right page hierarchy i.e for an SCA release, the relase page would go
under Home->SCA Overview->SCA Releases.
All of what is mentioned here for SCA could apply for SDO and DAS as well.
- Venkat
On 5/31/07, ant elder <an...@gmail.com> wrote:
>
> Ok, I've added a new download page for the SCA Java 0.90 release which
> hopefully isn't to far away from whats been talked about:
>
>
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
>
> Its not linked to from anywhere yet as I'm not sure after all this
> discussion where to put it. The main things I think would be good are to
> not
> have to click through many links to get to the actual download link for a
> latest release and for it to be quite obvious what the current latest
> release is of something and its not obscured that with lots of old
> download
> links.
>
> I wondered if the download page pointed to from the "General" menu box
> could
> be expanded to have links to each of the current download pages (the
> above
> SCA+Java+0.90-incubating etc) and at the bottom another link to a page
> with
> all the old downloads?
>
> ...ant
>
> On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
> >
> > Hi
> >
> > What we are attempting to do now it really far better than cluttering
> all
> > the downloads together on one page. Here is what I think about this
> >
> > - for every Release (SCA / SDO / DAS) have a separate page whose first
> > section talks about what comprises of that release (including spec
> levels
> > etc.) and then have a next section that is titled 'Downloads'.
> > - then have a single page titled 'Releases' where we list all the
> releases
> > and each entry is a link to the separate Release page. Here again we
> > could
> > choose to have SCA Releases, SDO Releases, DAS Releases on diff. pages
> or
> > just have all in one under diff sections.
> > - Finally from the global home page and the home page of the subprojects
> > have a menu item 'Releases' that will point to the 'Releases' page.
> >
> > This way, with every release we simply have to go an make the specific
> > release page and add a link to the Releases page. I had created a
> > Release
> > page for the recent SDO Release without the Downloads section
> > though. Here
> > it is just for people to get an idea of what I mean
> >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
> >
> > When creating these Release pages my request is that we maintain the
> page
> > hierarchies. For example the release page for the SCA 0.90 release
> should
> > be
> > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 Release.
> >
> > By the way there is a SCA Java and a SCA Java Subproject page - can we
> > merge
> > these two into one.
> >
> > Thanks
> >
> > - Venkat
> >
> > On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> > >
> > > I am including tuscany-users to get their opinion if interested.
> > >
> > > Here are my thoughts influenced by your comments :)
> > > - Separate the download information for latest release from the old
> > > releases.
> > > - Having the text of the change file/read me on the front page of the
> > > download page is good. This makes it easier to identify what is in the
> > new
> > > release. So, added a section called 'what's new in this release'.
> > > - It is good to have download information for at least the back 2
> > > releases.
> > >
> > > - It is useful to know what level of spec is supported by each
> release.
> > > For
> > > example, for SCA there are several specs. A release can be at Assembly
> > > 1.0level and an older version of Client spec.
> > > - Having a page that takes user to all the downloads[2] is good.
> > > - Having a download page per subproject is good since the audience
> for
> > > each
> > > download page may be different. For example, someone using SDO may not
> > > necessarily want to download SCA.
> > >
> > > Here is an attempt for a sample download page which incorporates your
> > > feedback [1]
> > > User will reach[1] from [2] (not linked yet)
> > >
> > > [1]
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > [2]
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > >
> > > Does it look OK?
> > >
> > >
> > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > >
> > > > The idea of a single download page sounds good, but if we are
> thinking
> > > > about tracking page visitors to correlate to the number of
> downloads,
> > > > we won't be able to identify if the person is visiting the page to
> > > > download SCA, SDO or DAS.
> > > >
> > > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > > > I agree it would be good to not duplicate things for each
> > downloadable
> > > > > artifact associated with a release. Not sure it really needs the
> day
> > > of
> > > > the
> > > > > release or the assembly spec info either.
> > > > >
> > > > > And +1 to having old release downloads on a separate page. I'm not
> > > sure
> > > > if
> > > > > this is the proposal but could there be a single download page
> that
> > > has
> > > > the
> > > > > current latest release of each of SCA, SDO and DAS?
> > > > >
> > > > > ...ant
> > > > >
> > > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > > >
> > > > > > My understanding is that you moved the release name and date
> from
> > > the
> > > > > > "download section" to the "download table". If they are always
> > same
> > > > > > for a group of downloads, won't it take space from the page by
> > > > > > repeating it on each table row ?
> > > > > >
> > > > > > Also, do we want to keep all past releases available on the main
> > > > > > download page ? Maybe we could have an separate archive page,
> and
> > > only
> > > > > > the latest release available in the main download page, this
> would
> > > > > > encourage people to always use the latest stable stuff ?
> > > > > >
> > > > > >
> > > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > 1) Would [1] be a better format & content for each download
> > page
> > > > > > of than
> > > > > > > what we have today [2]?
> > > > > > > If yes, I'll start upgrading the pages.
> > > > > > >
> > > > > > > 2) We currently use the same page to record download info for
> > > > > > technologies.
> > > > > > > For example, SCA Native and Java download pages are the same.
> > > > > > > It would be cleaner if we separate the pages. For example, a
> > Java
> > > > SCA
> > > > > > and a
> > > > > > > Native SCA download page which gets linked to from a common
> > > > > > > download page entry point [3]
> > > > > > > Does this seem reasonable?
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > > >
> > > >
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > > > [2]
> > > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > > > [3]
> > > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > > > >
> > > > > > >
> > > > > > > Haleh
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Luciano Resende
> > > > > > Apache Tuscany Committer
> > > > > > http://people.apache.org/~lresende
> > > > > > http://lresende.blogspot.com/
> > > > > >
> > > > > >
> > > ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > Apache Tuscany Committer
> > > > http://people.apache.org/~lresende
> > > > http://lresende.blogspot.com/
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > >
> > > >
> > >
> >
>
Re: Wiki Download page cleanup
Posted by ant elder <an...@gmail.com>.
Ok, I've added a new download page for the SCA Java 0.90 release which
hopefully isn't to far away from whats been talked about:
http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating
Its not linked to from anywhere yet as I'm not sure after all this
discussion where to put it. The main things I think would be good are to not
have to click through many links to get to the actual download link for a
latest release and for it to be quite obvious what the current latest
release is of something and its not obscured that with lots of old download
links.
I wondered if the download page pointed to from the "General" menu box could
be expanded to have links to each of the current download pages (the above
SCA+Java+0.90-incubating etc) and at the bottom another link to a page with
all the old downloads?
...ant
On 5/30/07, Venkata Krishnan <fo...@gmail.com> wrote:
>
> Hi
>
> What we are attempting to do now it really far better than cluttering all
> the downloads together on one page. Here is what I think about this
>
> - for every Release (SCA / SDO / DAS) have a separate page whose first
> section talks about what comprises of that release (including spec levels
> etc.) and then have a next section that is titled 'Downloads'.
> - then have a single page titled 'Releases' where we list all the releases
> and each entry is a link to the separate Release page. Here again we
> could
> choose to have SCA Releases, SDO Releases, DAS Releases on diff. pages or
> just have all in one under diff sections.
> - Finally from the global home page and the home page of the subprojects
> have a menu item 'Releases' that will point to the 'Releases' page.
>
> This way, with every release we simply have to go an make the specific
> release page and add a link to the Releases page. I had created a
> Release
> page for the recent SDO Release without the Downloads section
> though. Here
> it is just for people to get an idea of what I mean
>
> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
>
> When creating these Release pages my request is that we maintain the page
> hierarchies. For example the release page for the SCA 0.90 release should
> be
> added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 Release.
>
> By the way there is a SCA Java and a SCA Java Subproject page - can we
> merge
> these two into one.
>
> Thanks
>
> - Venkat
>
> On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
> >
> > I am including tuscany-users to get their opinion if interested.
> >
> > Here are my thoughts influenced by your comments :)
> > - Separate the download information for latest release from the old
> > releases.
> > - Having the text of the change file/read me on the front page of the
> > download page is good. This makes it easier to identify what is in the
> new
> > release. So, added a section called 'what's new in this release'.
> > - It is good to have download information for at least the back 2
> > releases.
> >
> > - It is useful to know what level of spec is supported by each release.
> > For
> > example, for SCA there are several specs. A release can be at Assembly
> > 1.0level and an older version of Client spec.
> > - Having a page that takes user to all the downloads[2] is good.
> > - Having a download page per subproject is good since the audience for
> > each
> > download page may be different. For example, someone using SDO may not
> > necessarily want to download SCA.
> >
> > Here is an attempt for a sample download page which incorporates your
> > feedback [1]
> > User will reach[1] from [2] (not linked yet)
> >
> > [1]
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> >
> > Does it look OK?
> >
> >
> > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > >
> > > The idea of a single download page sounds good, but if we are thinking
> > > about tracking page visitors to correlate to the number of downloads,
> > > we won't be able to identify if the person is visiting the page to
> > > download SCA, SDO or DAS.
> > >
> > > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > > I agree it would be good to not duplicate things for each
> downloadable
> > > > artifact associated with a release. Not sure it really needs the day
> > of
> > > the
> > > > release or the assembly spec info either.
> > > >
> > > > And +1 to having old release downloads on a separate page. I'm not
> > sure
> > > if
> > > > this is the proposal but could there be a single download page that
> > has
> > > the
> > > > current latest release of each of SCA, SDO and DAS?
> > > >
> > > > ...ant
> > > >
> > > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > > >
> > > > > My understanding is that you moved the release name and date from
> > the
> > > > > "download section" to the "download table". If they are always
> same
> > > > > for a group of downloads, won't it take space from the page by
> > > > > repeating it on each table row ?
> > > > >
> > > > > Also, do we want to keep all past releases available on the main
> > > > > download page ? Maybe we could have an separate archive page, and
> > only
> > > > > the latest release available in the main download page, this would
> > > > > encourage people to always use the latest stable stuff ?
> > > > >
> > > > >
> > > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > > Hi,
> > > > > >
> > > > > > 1) Would [1] be a better format & content for each download
> page
> > > > > of than
> > > > > > what we have today [2]?
> > > > > > If yes, I'll start upgrading the pages.
> > > > > >
> > > > > > 2) We currently use the same page to record download info for
> > > > > technologies.
> > > > > > For example, SCA Native and Java download pages are the same.
> > > > > > It would be cleaner if we separate the pages. For example, a
> Java
> > > SCA
> > > > > and a
> > > > > > Native SCA download page which gets linked to from a common
> > > > > > download page entry point [3]
> > > > > > Does this seem reasonable?
> > > > > >
> > > > > >
> > > > > > [1]
> > > > > >
> > > > >
> > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > > [2]
> > http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > > [3]
> > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > > >
> > > > > >
> > > > > > Haleh
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Luciano Resende
> > > > > Apache Tuscany Committer
> > > > > http://people.apache.org/~lresende
> > > > > http://lresende.blogspot.com/
> > > > >
> > > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende
> > > http://lresende.blogspot.com/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> > >
> >
>
Re: Wiki Download page cleanup
Posted by Simon Laws <si...@googlemail.com>.
There doesn't seem to been much distance between the last two suggestions.
It feels to me like people are starting to talk about the same structure.
Let me try and summarize...
Home
Downloads
SCA Java ---> SCA Java Releases
SCA Native -> SCA Native Releases
SDO Java --> SDO Java Releases
SDO Native --> SDO Native Releases
DAS --> DAS Releases
SCA Java
SCA Java Releases
Latest release ---> SCA 0.90 Release
M2 -------------------> SCA M2 Release
M1--------------------> SCA M1 Release
SCA Native
SCA Native Releases
etc.
I would hold ActiveMQ up as having quite a nice clear approach to the
Releases and individual Release pages we are discussing:
Their equivalient of "SCA Java Releases" is
http://activemq.apache.org/download.html
Their equivalent of "SCA 0.90 Release" is
http://activemq.apache.org/activemq-411-release.html (note that their change
log appears to be driven directly off of JIRAS as we have been discussing in
another thread)
Their homepage download link points to their equivalent of the "Downloads"
page that Haleh suggested previously (
http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads)
Regards
Simon
Re: Wiki Download page cleanup
Posted by Venkata Krishnan <fo...@gmail.com>.
Hi
What we are attempting to do now it really far better than cluttering all
the downloads together on one page. Here is what I think about this
- for every Release (SCA / SDO / DAS) have a separate page whose first
section talks about what comprises of that release (including spec levels
etc.) and then have a next section that is titled 'Downloads'.
- then have a single page titled 'Releases' where we list all the releases
and each entry is a link to the separate Release page. Here again we could
choose to have SCA Releases, SDO Releases, DAS Releases on diff. pages or
just have all in one under diff sections.
- Finally from the global home page and the home page of the subprojects
have a menu item 'Releases' that will point to the 'Releases' page.
This way, with every release we simply have to go an make the specific
release page and add a link to the Releases page. I had created a Release
page for the recent SDO Release without the Downloads section though. Here
it is just for people to get an idea of what I mean
http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1
When creating these Release pages my request is that we maintain the page
hierarchies. For example the release page for the SCA 0.90 release should be
added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 Release.
By the way there is a SCA Java and a SCA Java Subproject page - can we merge
these two into one.
Thanks
- Venkat
On 5/30/07, haleh mahbod <hm...@gmail.com> wrote:
>
> I am including tuscany-users to get their opinion if interested.
>
> Here are my thoughts influenced by your comments :)
> - Separate the download information for latest release from the old
> releases.
> - Having the text of the change file/read me on the front page of the
> download page is good. This makes it easier to identify what is in the new
> release. So, added a section called 'what's new in this release'.
> - It is good to have download information for at least the back 2
> releases.
>
> - It is useful to know what level of spec is supported by each release.
> For
> example, for SCA there are several specs. A release can be at Assembly
> 1.0level and an older version of Client spec.
> - Having a page that takes user to all the downloads[2] is good.
> - Having a download page per subproject is good since the audience for
> each
> download page may be different. For example, someone using SDO may not
> necessarily want to download SCA.
>
> Here is an attempt for a sample download page which incorporates your
> feedback [1]
> User will reach[1] from [2] (not linked yet)
>
> [1]
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> [2] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>
> Does it look OK?
>
>
> On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> >
> > The idea of a single download page sounds good, but if we are thinking
> > about tracking page visitors to correlate to the number of downloads,
> > we won't be able to identify if the person is visiting the page to
> > download SCA, SDO or DAS.
> >
> > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > I agree it would be good to not duplicate things for each downloadable
> > > artifact associated with a release. Not sure it really needs the day
> of
> > the
> > > release or the assembly spec info either.
> > >
> > > And +1 to having old release downloads on a separate page. I'm not
> sure
> > if
> > > this is the proposal but could there be a single download page that
> has
> > the
> > > current latest release of each of SCA, SDO and DAS?
> > >
> > > ...ant
> > >
> > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > >
> > > > My understanding is that you moved the release name and date from
> the
> > > > "download section" to the "download table". If they are always same
> > > > for a group of downloads, won't it take space from the page by
> > > > repeating it on each table row ?
> > > >
> > > > Also, do we want to keep all past releases available on the main
> > > > download page ? Maybe we could have an separate archive page, and
> only
> > > > the latest release available in the main download page, this would
> > > > encourage people to always use the latest stable stuff ?
> > > >
> > > >
> > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > Hi,
> > > > >
> > > > > 1) Would [1] be a better format & content for each download page
> > > > of than
> > > > > what we have today [2]?
> > > > > If yes, I'll start upgrading the pages.
> > > > >
> > > > > 2) We currently use the same page to record download info for
> > > > technologies.
> > > > > For example, SCA Native and Java download pages are the same.
> > > > > It would be cleaner if we separate the pages. For example, a Java
> > SCA
> > > > and a
> > > > > Native SCA download page which gets linked to from a common
> > > > > download page entry point [3]
> > > > > Does this seem reasonable?
> > > > >
> > > > >
> > > > > [1]
> > > > >
> > > >
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > [2]
> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > [3]
> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > >
> > > > >
> > > > > Haleh
> > > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > Apache Tuscany Committer
> > > > http://people.apache.org/~lresende
> > > > http://lresende.blogspot.com/
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
Simple use case problem
Posted by Patrick Vanhuyse <pv...@greisch.com>.
Hi,
I'm new to SCA and I'm trying to do a little example.
My very simple use case :
A ProviderComponent implemented in Java in a Provider composite. All this in
a jar file.
Alone works fine.
A ConsumerComponent implemented in Java in a Consumer composite in another
jar file.
This component references Provider.
Problem !
When I run the test, I receive an error (see below) :
Composite assembly problem: Component reference target not found:
ProviderComponent
and sometimes it's the ConsumerComponent which is not found.
I'am missing something.
I tried to attach the full code (zip 29K) to this e-mail but it's rejected.
I can send it if somebody could look at it.
Thanks in advance.
Patrick
H:\IT\Logiciel_GI\sca>mvn test
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Greisch Tuscany SCA
[INFO] Service Provider Sample
[INFO] Service Consumer Sample
[INFO] ---------------------------------------------------------------------
-------
[INFO] Building Greisch Tuscany SCA
[INFO] task-segment: [test]
[INFO] ---------------------------------------------------------------------
-------
[INFO] No goals needed for project - skipping
[INFO] ---------------------------------------------------------------------
-------
[INFO] Building Service Provider Sample
[INFO] task-segment: [test]
[INFO] ---------------------------------------------------------------------
-------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading:
http://people.apache.org/repo/m2-incubating-repository/wsdl4j/wsdl4j/1.6.2/w
sdl4j-1.6.2.pom
Downloading:
http://www.ibiblio.net/pub/packages/maven2/wsdl4j/wsdl4j/1.6.2/wsdl4j-1.6.2.
pom
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
H:\IT\Logiciel_GI\sca\provider\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running provider.ProviderTestCase
Arg: Provision
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.344 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] ---------------------------------------------------------------------
-------
[INFO] Building Service Consumer Sample
[INFO] task-segment: [test]
[INFO] ---------------------------------------------------------------------
-------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
H:\IT\Logiciel_GI\sca\consumer\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running consumer.ConsumerTestCase
Composite assembly problem: Component reference target not found:
ProviderComponent
Consumer Arg: Provision
java.lang.NullPointerException
at consumer.ConsumerImpl.consume(ConsumerImpl.java:17)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvoker.invo
keTarget(JavaTargetInvoker.java:1
12)
at
org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvoker.invo
ke(JavaTargetInvoker.java:134)
at
org.apache.tuscany.sca.implementation.java.invocation.TargetInvokerInvoker.i
nvoke(TargetInvokerInvoker.java:4
6)
at
org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invoke(Abst
ractInvocationHandler.java:84)
at
org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvoca
tionHandler.java:73)
at $Proxy6.consume(Unknown Source)
at consumer.ConsumerTestCase.test(ConsumerTestCase.java:23)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at
org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner.java:35
)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:62
)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(Ab
stractDirectoryTestSuite.java:138
)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractD
irectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireB
ooter.java:290)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:818
)
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.281 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO]
[INFO] ---------------------------------------------------------------------
---
[INFO] Reactor Summary:
[INFO] ---------------------------------------------------------------------
---
[INFO] Greisch Tuscany SCA ................................... SUCCESS
[0.016s]
[INFO] Service Provider Sample ............................... SUCCESS
[17.781s]
[INFO] Service Consumer Sample ............................... SUCCESS
[10.344s]
[INFO] ---------------------------------------------------------------------
---
[INFO] ---------------------------------------------------------------------
---
[INFO] BUILD SUCCESSFUL
[INFO] ---------------------------------------------------------------------
---
[INFO] Total time: 29 seconds
[INFO] Finished at: Wed May 30 13:15:25 CEST 2007
[INFO] Final Memory: 5M/10M
[INFO] ---------------------------------------------------------------------
---
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-user-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-user-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by haleh mahbod <hm...@gmail.com>.
I am including tuscany-users to get their opinion if interested.
Here are my thoughts influenced by your comments :)
- Separate the download information for latest release from the old
releases.
- Having the text of the change file/read me on the front page of the
download page is good. This makes it easier to identify what is in the new
release. So, added a section called 'what's new in this release'.
- It is good to have download information for at least the back 2 releases.
- It is useful to know what level of spec is supported by each release. For
example, for SCA there are several specs. A release can be at Assembly
1.0level and an older version of Client spec.
- Having a page that takes user to all the downloads[2] is good.
- Having a download page per subproject is good since the audience for each
download page may be different. For example, someone using SDO may not
necessarily want to download SCA.
Here is an attempt for a sample download page which incorporates your
feedback [1]
User will reach[1] from [2] (not linked yet)
[1]
http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
[2] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
Does it look OK?
On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>
> The idea of a single download page sounds good, but if we are thinking
> about tracking page visitors to correlate to the number of downloads,
> we won't be able to identify if the person is visiting the page to
> download SCA, SDO or DAS.
>
> On 5/29/07, ant elder <an...@gmail.com> wrote:
> > I agree it would be good to not duplicate things for each downloadable
> > artifact associated with a release. Not sure it really needs the day of
> the
> > release or the assembly spec info either.
> >
> > And +1 to having old release downloads on a separate page. I'm not sure
> if
> > this is the proposal but could there be a single download page that has
> the
> > current latest release of each of SCA, SDO and DAS?
> >
> > ...ant
> >
> > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > >
> > > My understanding is that you moved the release name and date from the
> > > "download section" to the "download table". If they are always same
> > > for a group of downloads, won't it take space from the page by
> > > repeating it on each table row ?
> > >
> > > Also, do we want to keep all past releases available on the main
> > > download page ? Maybe we could have an separate archive page, and only
> > > the latest release available in the main download page, this would
> > > encourage people to always use the latest stable stuff ?
> > >
> > >
> > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > 1) Would [1] be a better format & content for each download page
> > > of than
> > > > what we have today [2]?
> > > > If yes, I'll start upgrading the pages.
> > > >
> > > > 2) We currently use the same page to record download info for
> > > technologies.
> > > > For example, SCA Native and Java download pages are the same.
> > > > It would be cleaner if we separate the pages. For example, a Java
> SCA
> > > and a
> > > > Native SCA download page which gets linked to from a common
> > > > download page entry point [3]
> > > > Does this seem reasonable?
> > > >
> > > >
> > > > [1]
> > > >
> > >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > [3]
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > >
> > > >
> > > > Haleh
> > > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende
> > > http://lresende.blogspot.com/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> > >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Wiki Download page cleanup
Posted by haleh mahbod <hm...@gmail.com>.
I am including tuscany-users to get their opinion if interested.
Here are my thoughts influenced by your comments :)
- Separate the download information for latest release from the old
releases.
- Having the text of the change file/read me on the front page of the
download page is good. This makes it easier to identify what is in the new
release. So, added a section called 'what's new in this release'.
- It is good to have download information for at least the back 2 releases.
- It is useful to know what level of spec is supported by each release. For
example, for SCA there are several specs. A release can be at Assembly
1.0level and an older version of Client spec.
- Having a page that takes user to all the downloads[2] is good.
- Having a download page per subproject is good since the audience for each
download page may be different. For example, someone using SDO may not
necessarily want to download SCA.
Here is an attempt for a sample download page which incorporates your
feedback [1]
User will reach[1] from [2] (not linked yet)
[1]
http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
[2] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
Does it look OK?
On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>
> The idea of a single download page sounds good, but if we are thinking
> about tracking page visitors to correlate to the number of downloads,
> we won't be able to identify if the person is visiting the page to
> download SCA, SDO or DAS.
>
> On 5/29/07, ant elder <an...@gmail.com> wrote:
> > I agree it would be good to not duplicate things for each downloadable
> > artifact associated with a release. Not sure it really needs the day of
> the
> > release or the assembly spec info either.
> >
> > And +1 to having old release downloads on a separate page. I'm not sure
> if
> > this is the proposal but could there be a single download page that has
> the
> > current latest release of each of SCA, SDO and DAS?
> >
> > ...ant
> >
> > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > >
> > > My understanding is that you moved the release name and date from the
> > > "download section" to the "download table". If they are always same
> > > for a group of downloads, won't it take space from the page by
> > > repeating it on each table row ?
> > >
> > > Also, do we want to keep all past releases available on the main
> > > download page ? Maybe we could have an separate archive page, and only
> > > the latest release available in the main download page, this would
> > > encourage people to always use the latest stable stuff ?
> > >
> > >
> > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > 1) Would [1] be a better format & content for each download page
> > > of than
> > > > what we have today [2]?
> > > > If yes, I'll start upgrading the pages.
> > > >
> > > > 2) We currently use the same page to record download info for
> > > technologies.
> > > > For example, SCA Native and Java download pages are the same.
> > > > It would be cleaner if we separate the pages. For example, a Java
> SCA
> > > and a
> > > > Native SCA download page which gets linked to from a common
> > > > download page entry point [3]
> > > > Does this seem reasonable?
> > > >
> > > >
> > > > [1]
> > > >
> > >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > [3]
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > >
> > > >
> > > > Haleh
> > > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende
> > > http://lresende.blogspot.com/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> > >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Wiki Download page cleanup
Posted by Luciano Resende <lu...@gmail.com>.
On 5/29/07, ant elder <an...@gmail.com> wrote:
> Tracking page visitors is a bit meaningless due to things like caching isn't
> it?
Well, if the tracking is done via a js embedded on the page, cache
won't affect it, will it ?
While the incubator downloads aren't being mirrored we could just count
> those though (but I think they may be about to start mirroring them)
The count process trough the apache logs, is simple but slow and I'm
not sure a easy and simple way to automate it.
>
> ...ant
>
> On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> >
> > The idea of a single download page sounds good, but if we are thinking
> > about tracking page visitors to correlate to the number of downloads,
> > we won't be able to identify if the person is visiting the page to
> > download SCA, SDO or DAS.
> >
> > On 5/29/07, ant elder <an...@gmail.com> wrote:
> > > I agree it would be good to not duplicate things for each downloadable
> > > artifact associated with a release. Not sure it really needs the day of
> > the
> > > release or the assembly spec info either.
> > >
> > > And +1 to having old release downloads on a separate page. I'm not sure
> > if
> > > this is the proposal but could there be a single download page that has
> > the
> > > current latest release of each of SCA, SDO and DAS?
> > >
> > > ...ant
> > >
> > > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > > >
> > > > My understanding is that you moved the release name and date from the
> > > > "download section" to the "download table". If they are always same
> > > > for a group of downloads, won't it take space from the page by
> > > > repeating it on each table row ?
> > > >
> > > > Also, do we want to keep all past releases available on the main
> > > > download page ? Maybe we could have an separate archive page, and only
> > > > the latest release available in the main download page, this would
> > > > encourage people to always use the latest stable stuff ?
> > > >
> > > >
> > > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > > Hi,
> > > > >
> > > > > 1) Would [1] be a better format & content for each download page
> > > > of than
> > > > > what we have today [2]?
> > > > > If yes, I'll start upgrading the pages.
> > > > >
> > > > > 2) We currently use the same page to record download info for
> > > > technologies.
> > > > > For example, SCA Native and Java download pages are the same.
> > > > > It would be cleaner if we separate the pages. For example, a Java
> > SCA
> > > > and a
> > > > > Native SCA download page which gets linked to from a common
> > > > > download page entry point [3]
> > > > > Does this seem reasonable?
> > > > >
> > > > >
> > > > > [1]
> > > > >
> > > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > > [3]
> > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > > >
> > > > >
> > > > > Haleh
> > > > >
> > > >
> > > >
> > > > --
> > > > Luciano Resende
> > > > Apache Tuscany Committer
> > > > http://people.apache.org/~lresende
> > > > http://lresende.blogspot.com/
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > > >
> > > >
> > >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by ant elder <an...@gmail.com>.
Tracking page visitors is a bit meaningless due to things like caching isn't
it? While the incubator downloads aren't being mirrored we could just count
those though (but I think they may be about to start mirroring them)
...ant
On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>
> The idea of a single download page sounds good, but if we are thinking
> about tracking page visitors to correlate to the number of downloads,
> we won't be able to identify if the person is visiting the page to
> download SCA, SDO or DAS.
>
> On 5/29/07, ant elder <an...@gmail.com> wrote:
> > I agree it would be good to not duplicate things for each downloadable
> > artifact associated with a release. Not sure it really needs the day of
> the
> > release or the assembly spec info either.
> >
> > And +1 to having old release downloads on a separate page. I'm not sure
> if
> > this is the proposal but could there be a single download page that has
> the
> > current latest release of each of SCA, SDO and DAS?
> >
> > ...ant
> >
> > On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> > >
> > > My understanding is that you moved the release name and date from the
> > > "download section" to the "download table". If they are always same
> > > for a group of downloads, won't it take space from the page by
> > > repeating it on each table row ?
> > >
> > > Also, do we want to keep all past releases available on the main
> > > download page ? Maybe we could have an separate archive page, and only
> > > the latest release available in the main download page, this would
> > > encourage people to always use the latest stable stuff ?
> > >
> > >
> > > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > 1) Would [1] be a better format & content for each download page
> > > of than
> > > > what we have today [2]?
> > > > If yes, I'll start upgrading the pages.
> > > >
> > > > 2) We currently use the same page to record download info for
> > > technologies.
> > > > For example, SCA Native and Java download pages are the same.
> > > > It would be cleaner if we separate the pages. For example, a Java
> SCA
> > > and a
> > > > Native SCA download page which gets linked to from a common
> > > > download page entry point [3]
> > > > Does this seem reasonable?
> > > >
> > > >
> > > > [1]
> > > >
> > >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > > [3]
> http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > > >
> > > >
> > > > Haleh
> > > >
> > >
> > >
> > > --
> > > Luciano Resende
> > > Apache Tuscany Committer
> > > http://people.apache.org/~lresende
> > > http://lresende.blogspot.com/
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> > >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Wiki Download page cleanup
Posted by Luciano Resende <lu...@gmail.com>.
The idea of a single download page sounds good, but if we are thinking
about tracking page visitors to correlate to the number of downloads,
we won't be able to identify if the person is visiting the page to
download SCA, SDO or DAS.
On 5/29/07, ant elder <an...@gmail.com> wrote:
> I agree it would be good to not duplicate things for each downloadable
> artifact associated with a release. Not sure it really needs the day of the
> release or the assembly spec info either.
>
> And +1 to having old release downloads on a separate page. I'm not sure if
> this is the proposal but could there be a single download page that has the
> current latest release of each of SCA, SDO and DAS?
>
> ...ant
>
> On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
> >
> > My understanding is that you moved the release name and date from the
> > "download section" to the "download table". If they are always same
> > for a group of downloads, won't it take space from the page by
> > repeating it on each table row ?
> >
> > Also, do we want to keep all past releases available on the main
> > download page ? Maybe we could have an separate archive page, and only
> > the latest release available in the main download page, this would
> > encourage people to always use the latest stable stuff ?
> >
> >
> > On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > > Hi,
> > >
> > > 1) Would [1] be a better format & content for each download page
> > of than
> > > what we have today [2]?
> > > If yes, I'll start upgrading the pages.
> > >
> > > 2) We currently use the same page to record download info for
> > technologies.
> > > For example, SCA Native and Java download pages are the same.
> > > It would be cleaner if we separate the pages. For example, a Java SCA
> > and a
> > > Native SCA download page which gets linked to from a common
> > > download page entry point [3]
> > > Does this seem reasonable?
> > >
> > >
> > > [1]
> > >
> > http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > > [3] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> > >
> > >
> > > Haleh
> > >
> >
> >
> > --
> > Luciano Resende
> > Apache Tuscany Committer
> > http://people.apache.org/~lresende
> > http://lresende.blogspot.com/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by ant elder <an...@gmail.com>.
I agree it would be good to not duplicate things for each downloadable
artifact associated with a release. Not sure it really needs the day of the
release or the assembly spec info either.
And +1 to having old release downloads on a separate page. I'm not sure if
this is the proposal but could there be a single download page that has the
current latest release of each of SCA, SDO and DAS?
...ant
On 5/29/07, Luciano Resende <lu...@gmail.com> wrote:
>
> My understanding is that you moved the release name and date from the
> "download section" to the "download table". If they are always same
> for a group of downloads, won't it take space from the page by
> repeating it on each table row ?
>
> Also, do we want to keep all past releases available on the main
> download page ? Maybe we could have an separate archive page, and only
> the latest release available in the main download page, this would
> encourage people to always use the latest stable stuff ?
>
>
> On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> > Hi,
> >
> > 1) Would [1] be a better format & content for each download page
> of than
> > what we have today [2]?
> > If yes, I'll start upgrading the pages.
> >
> > 2) We currently use the same page to record download info for
> technologies.
> > For example, SCA Native and Java download pages are the same.
> > It would be cleaner if we separate the pages. For example, a Java SCA
> and a
> > Native SCA download page which gets linked to from a common
> > download page entry point [3]
> > Does this seem reasonable?
> >
> >
> > [1]
> >
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> > [3] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
> >
> >
> > Haleh
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Wiki Download page cleanup
Posted by Luciano Resende <lu...@gmail.com>.
My understanding is that you moved the release name and date from the
"download section" to the "download table". If they are always same
for a group of downloads, won't it take space from the page by
repeating it on each table row ?
Also, do we want to keep all past releases available on the main
download page ? Maybe we could have an separate archive page, and only
the latest release available in the main download page, this would
encourage people to always use the latest stable stuff ?
On 5/29/07, haleh mahbod <hm...@gmail.com> wrote:
> Hi,
>
> 1) Would [1] be a better format & content for each download page of than
> what we have today [2]?
> If yes, I'll start upgrading the pages.
>
> 2) We currently use the same page to record download info for technologies.
> For example, SCA Native and Java download pages are the same.
> It would be cleaner if we separate the pages. For example, a Java SCA and a
> Native SCA download page which gets linked to from a common
> download page entry point [3]
> Does this seem reasonable?
>
>
> [1]
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> [3] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>
>
> Haleh
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Wiki Download page cleanup
Posted by Jean-Sebastien Delfino <js...@apache.org>.
haleh mahbod wrote:
> Hi,
>
> 1) Would [1] be a better format & content for each download page of
> than
> what we have today [2]?
> If yes, I'll start upgrading the pages.
>
> 2) We currently use the same page to record download info for
> technologies.
> For example, SCA Native and Java download pages are the same.
> It would be cleaner if we separate the pages. For example, a Java SCA
> and a
> Native SCA download page which gets linked to from a common
> download page entry point [3]
> Does this seem reasonable?
>
>
> [1]
> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page
> [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads
> [3] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads
>
>
> Haleh
>
That looks good to me.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org