On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws wrote:
> How about we start to making progress on the Beta release again...
>
> Things are looking ok I believe from an otest point of view.
> We've had discussion about the samples and that looks to be shaping up.
> We've also had disscussion about the
On Thu, Sep 30, 2010 at 8:29 AM, ant elder wrote:
> On Wed, Sep 29, 2010 at 6:27 PM, Simon Laws wrote:
>> How about we start to making progress on the Beta release again...
>>
>> Things are looking ok I believe from an otest point of view.
>> We've had discussion about the samples and that looks
On Wed, Sep 29, 2010 at 5:03 PM, Florian MOGA wrote:
> From what I understand node.xml would be the final configuration that you
> would export from the shell after adding/installing all the
> contributributions (please correct me if i'm wrong).
Yep thats what i was thinking would be useful.
> W
On Sat, Sep 25, 2010 at 12:55 PM, Fabio Albani wrote:
> Hi to all,
> I'm developing a new implementation type for Tuscany 1.x, based on ASM, I've
> been successfully in calling services and introspecting references and
> properties, but I don't know how to get the current wiring from the running
>
On Wed, Sep 29, 2010 at 6:11 PM, Simon Laws wrote:
> Ok well I've published a snapshot of our maven-bundle-plugin that
> allows us to generate some more meta-data for the binary distro. The
> snapshot is not synched yet to the Nexus repo so I haven't committed
> the distro poms that allow you to b
On Wed, Sep 29, 2010 at 7:24 PM, Raymond Feng wrote:
> To me, the "extension" is just a "feature" that contains only the modules
> that make up the "extension" :-).
What is the point in that? We call them extensions everywhere else
(doc, spec, code, website etc), so it seems simpler to not obfusc
On Wed, Sep 29, 2010 at 7:24 PM, Raymond Feng wrote:
> To me, the "extension" is just a "feature" that contains only the modules
> that make up the "extension" :-). For example, I can model the binding.ws
> extension as feature-binding-ws (a pom project that list feature-base,
> binding-ws, bindin
On Wed, Sep 29, 2010 at 6:42 PM, Simon Laws wrote:
>
> There is an issue though. The extension meta-data repeats all the
> dependencies that base provides. This actually doesn't make a
> difference because the duplicates don't have a material impact on the
> classpath (other than we might generat
On Thu, Sep 30, 2010 at 9:04 AM, ant elder wrote:
> On Wed, Sep 29, 2010 at 7:24 PM, Raymond Feng wrote:
>> To me, the "extension" is just a "feature" that contains only the modules
>> that make up the "extension" :-).
>
> What is the point in that? We call them extensions everywhere else
> (doc,
I can. Its so we have enough control to easily support all the valid
usages of contributions and combinations of contributions. Eg, take a
look at samples/getting-started/scdl-include, theres no doc or readme
yet but it uses two contributions, helloworld and scdl-include,
presently you can't easily
On Thu, Sep 30, 2010 at 9:06 AM, ant elder wrote:
> On Wed, Sep 29, 2010 at 6:42 PM, Simon Laws wrote:
>
>>
>> There is an issue though. The extension meta-data repeats all the
>> dependencies that base provides. This actually doesn't make a
>> difference because the duplicates don't have a mater
Ant,
I've been looking around and seen that node.xml is actually something
already existing. Is this something we added or is it in the spec as well?
Indeed, it would add consistency if you can generate and load node.xml as
well.
The "run" command is exactly what I'm suggesting as well as the sta
Given the fact that in about one week or so we are about to finish technical
tasks like the jsonp binding, the shell, etc. I think it is a good time to
do the release but not before we do the distribution cleanup. If we want to
improve our release process we'll need a clean, simple and organized pl
It's been a full day since I've proposed the *-contribution renaming and no
negative reactions so I'll proceed with doing the changes tomorrow morning.
On Thu, Sep 30, 2010 at 11:45 AM, Florian MOGA wrote:
> Ant,
>
> I've been looking around and seen that node.xml is actually something
> already
I agree with all those suggestions.
...ant
On Thu, Sep 30, 2010 at 10:10 AM, Florian MOGA wrote:
> Given the fact that in about one week or so we are about to finish technical
> tasks like the jsonp binding, the shell, etc. I think it is a good time to
> do the release but not before we do the
Simon Laws wrote:
On Thu, Sep 30, 2010 at 9:06 AM, ant elder wrote:
On Wed, Sep 29, 2010 at 6:42 PM, Simon Laws wrote:
There is an issue though. The extension meta-data repeats all the
dependencies that base provides. This actually doesn't make a
difference because the duplicates don't have
Simon Nash wrote:
Simon Laws wrote:
On Thu, Sep 30, 2010 at 9:06 AM, ant elder wrote:
On Wed, Sep 29, 2010 at 6:42 PM, Simon Laws
wrote:
There is an issue though. The extension meta-data repeats all the
dependencies that base provides. This actually doesn't make a
difference because the du
ant elder wrote:
On Sat, Sep 25, 2010 at 12:55 PM, Fabio Albani wrote:
Hi to all,
I'm developing a new implementation type for Tuscany 1.x, based on ASM, I've
been successfully in calling services and introspecting references and
properties, but I don't know how to get the current wiring from t
>> I think this will be difficult if the base is made up of a large number
>> of jars and poms. AIUI the exlude list would have to name all the poms
>> in the base. If the list of poms in the base ever changes then all the
>> exclude lists would have to change as well.
>>
>> A simple solution wou
On Thu, Sep 30, 2010 at 11:09 AM, Simon Laws wrote:
>>> I think this will be difficult if the base is made up of a large number
>>> of jars and poms. AIUI the exlude list would have to name all the poms
>>> in the base. If the list of poms in the base ever changes then all the
>>> exclude lists
On Thu, Sep 30, 2010 at 9:45 AM, Florian MOGA wrote:
> Ant,
> I've been looking around and seen that node.xml is actually something
> already existing. Is this something we added or is it in the spec as well?
No the spec doesn't define anything for this, its one of those areas
where they've left
JMS Binding erases the stack trach of runtime exceptions
Key: TUSCANY-3698
URL: https://issues.apache.org/jira/browse/TUSCANY-3698
Project: Tuscany
Issue Type: Bug
Components
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraig Myers updated TUSCANY-3698:
---
Summary: JMS Binding erases the stack trace of RuntimeException's (was:
JMS Binding erases
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraig Myers updated TUSCANY-3698:
---
Attachment: Patch_TUSCANY-3698
Patch to fix the specified bug
> JMS Binding erases the sta
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraig Myers updated TUSCANY-3698:
---
Description:
In the file
org.apache.tuscany.sca.binding.jms.provider.AbstractMessageProces
ant elder wrote:
On Thu, Sep 30, 2010 at 11:09 AM, Simon Laws wrote:
I think this will be difficult if the base is made up of a large number
of jars and poms. AIUI the exlude list would have to name all the poms
in the base. If the list of poms in the base ever changes then all the
exclude li
Since we're cleaning up things I took a look again at the JIRA Categories. I
propose simply having:
Java SCA
Java SDO
Java DAS
C++ SCA
C++ SDO
C++ DAS
OASIS
Tools (including Hudson, Maven, SVN issues)
Website/Documentation
User Questions
Ideas
instead of having ~30 categories which nobody uses...
On Thu, Sep 30, 2010 at 1:18 AM, Luciano Resende wrote:
> On Wed, Sep 29, 2010 at 8:27 AM, Simon Nash wrote:
>> I tried the "brute force" approach today. Without any changes to the
>> repository definitions in the poms I ran the top-level build and killed it
>> when it hit a "hung" download. I
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916454#action_12916454
]
Scott Kurz commented on TUSCANY-3698:
-
The original behavior was the design, (sort of
+1 on the shortened list of JIRA categories. The current granularity
doesn't seem to be all that helpful. I'm not sure if there needs to be
a separate section for user questions -- with the shortened list it
should be possible for even the newest of users to find a home for a
JIRA. Similarly for "I
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916459#action_12916459
]
Padraig Myers commented on TUSCANY-3698:
The problem here isn't so much that we a
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916464#action_12916464
]
ant elder commented on TUSCANY-3698:
Padraig, i think the issue is that we don't know
Hi Brent,
The idea for the User folder is that it would help us avoid issues being
assigned to the wrong category (might not be the case for such general
categories) but most important user reported issues will go through a triage
phase and become "official" issues after we take a look at them. It
On Thu, Sep 30, 2010 at 1:28 PM, ant elder wrote:
> On Thu, Sep 30, 2010 at 1:18 AM, Luciano Resende wrote:
>> On Wed, Sep 29, 2010 at 8:27 AM, Simon Nash wrote:
>>> I tried the "brute force" approach today. Without any changes to the
>>> repository definitions in the poms I ran the top-level b
Hi guys,
How did the JavaOne sessions go? Are there any photos/video available? What
is the overall impression you have on the reaction of the attendees?
Florian
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916505#action_12916505
]
Padraig Myers commented on TUSCANY-3698:
Thanks for the quick replies guys.
As I
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916505#action_12916505
]
Padraig Myers edited comment on TUSCANY-3698 at 9/30/10 11:05 AM:
-
samples/helloworld-ws-sdo README instructions are wrong and produce incorrect
results
-
Key: TUSCANY-3699
URL: https://issues.apache.org/jira/browse/TUSCANY-3699
Proj
samples/photo-gallery index and slideshow buttons don't work
Key: TUSCANY-3700
URL: https://issues.apache.org/jira/browse/TUSCANY-3700
Project: Tuscany
Issue Type: Bug
Co
What about a Samples category as well?
On Thu, Sep 30, 2010 at 4:57 PM, Florian MOGA wrote:
> Hi Brent,
>
> The idea for the User folder is that it would help us avoid issues being
> assigned to the wrong category (might not be the case for such general
> categories) but most important user rep
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Kurz updated TUSCANY-3698:
Attachment: 3698.skurz.patch
I guess we could add the stack trace, element by element, to message
On Thu, Sep 30, 2010 at 4:50 PM, Florian MOGA wrote:
> What about a Samples category as well?
>
> On Thu, Sep 30, 2010 at 4:57 PM, Florian MOGA wrote:
>>
>> Hi Brent,
>> The idea for the User folder is that it would help us avoid issues being
>> assigned to the wrong category (might not be the ca
Good remark, didn't know about it.
On Thu, Sep 30, 2010 at 7:08 PM, Simon Laws wrote:
> On Thu, Sep 30, 2010 at 4:50 PM, Florian MOGA wrote:
> > What about a Samples category as well?
> >
> > On Thu, Sep 30, 2010 at 4:57 PM, Florian MOGA
> wrote:
> >>
> >> Hi Brent,
> >> The idea for the User f
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916535#action_12916535
]
Padraig Myers commented on TUSCANY-3698:
I don't think there's a need to loop thr
>>>
>>> Well it would work ok if the "base" remained as an "pom" type pom
>>> which just groups together other modules. The only time this would
>>> need rebuilding would be when the set of dependency jars change. Which
>>> isn't very often.
>>>
>>> The question then remains whether you can exclude
Hi,
I added my session slides at the bottom of the following page. It will show up
when the wiki site is synced over.
http://tuscany.apache.org/tuscany-books-and-articles.html
The databinding session was 8:00am in the morning and about 50 people showed
up. It went well with good questions.
Th
1) If a contribution doesn't have sca-contribution.xml for the exports, all the
artifacts should be private to the contribution (similar as an OSGi bundle that
doesn't export any packages). We can only use it by attaching a deployment
composite. I don't think we should change the visibility.
2
On Thu, Sep 30, 2010 at 10:01 AM, Raymond Feng wrote:
> Hi,
> I added my session slides at the bottom of the following page. It will show
> up when the wiki site is synced over.
> http://tuscany.apache.org/tuscany-books-and-articles.html
> The databinding session was 8:00am in the morning and abou
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Padraig Myers updated TUSCANY-3698:
---
Attachment: 3698.padraig.ver2.patch
Sorry of course printStackTrace() wont work, sorry its
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916566#action_12916566
]
Padraig Myers edited comment on TUSCANY-3698 at 9/30/10 1:27 PM:
--
[
https://issues.apache.org/jira/browse/TUSCANY-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12916578#action_12916578
]
ant elder commented on TUSCANY-3698:
That sounds good to me too. I'll wait a little t
ant elder wrote:
On Thu, Sep 30, 2010 at 1:18 AM, Luciano Resende wrote:
On Wed, Sep 29, 2010 at 8:27 AM, Simon Nash wrote:
I tried the "brute force" approach today. Without any changes to the
repository definitions in the poms I ran the top-level build and killed it
when it hit a "hung" dow
Florian MOGA wrote:
Since we're cleaning up things I took a look again at the JIRA
Categories. I propose simply having:
Java SCA
Java SDO
Java DAS
C++ SCA
C++ SDO
C++ DAS
OASIS
Tools (including Hudson, Maven, SVN issues)
Website/Documentation
User Questions
Ideas
instead of having ~30 categori
ant elder wrote:
On Thu, Sep 30, 2010 at 1:28 PM, ant elder wrote:
On Thu, Sep 30, 2010 at 1:18 AM, Luciano Resende wrote:
On Wed, Sep 29, 2010 at 8:27 AM, Simon Nash wrote:
I tried the "brute force" approach today. Without any changes to the
repository definitions in the poms I ran the to
On Thu, Sep 30, 2010 at 8:31 PM, Simon Nash wrote:
> ant elder wrote:
>>
>> On Thu, Sep 30, 2010 at 1:28 PM, ant elder wrote:
>>>
>>> On Thu, Sep 30, 2010 at 1:18 AM, Luciano Resende
>>> wrote:
On Wed, Sep 29, 2010 at 8:27 AM, Simon Nash wrote:
>
> I tried the "brute force" ap
Simon N,
You are pointing out some good facts about which i can't express a realistic
opinion given my limited experience in working on tuscany... I'll be
following this thread with interest for opinions from the other tuscany
people. The only observation I can make is that in this case we'll need
It's great seeing the positive reactions after the sessions!
Can you also share with us other facts like observations on specific things
that kept the attendees interested? That would be helpful to have in mind
when working on improving the documentation/website. (that's one example,
basically any
57 matches
Mail list logo
