I am not intimately involved in day to day coding and I am not attached to
any of the branches or the names :) So, take this comment as a 3rd person's
point of view.
1.x relays the message that 1.0 and incremental releases of 1.0 are spawned
off of this version of the code.
2.x relays the message
I have started to define the structure and some classes to allow the GData
binding, as discussed above.
This project was created following the binding-atom-abdera project
structure. So there is some dependencies that need to be revised.
The initial created classes aim to handle with the reference
Hi Oscar,
I say that it is more difficult to debug because you need attach a source
code to each jar and etc, and when you are using projects, eclipse already
knows where to find the source code : )
The reply made sense to me, especially with regards to the fact that with
the Android plugin Eclip
[
https://issues.apache.org/jira/browse/TUSCANY-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Douglas Siqueira Leite updated TUSCANY-2376:
Attachment: tuscany2376_douglas_2008_06_06.patch
The dependencies at pom
Add Atom-GData binding extension
Key: TUSCANY-2376
URL: https://issues.apache.org/jira/browse/TUSCANY-2376
Project: Tuscany
Issue Type: New Feature
Components: Java SCA ATOM Binding Extension
I found that I needed to make a few small changes to the
ContributionContentProcessor to handle contributions with no
sca-contribution.xml, like existing regular JARs for example.
I've been able to use regular JARs in an SCA domain with the following
changes:
- define DefaultImport/DefaultEx
Luciano Resende wrote:
How about 1.5-SNAPSHOT ? This would probably give us some room to have
couple releases without the necessity to keep updating the trunk pom
version. And this would probably make everybody happy :)
On Fri, Jun 6, 2008 at 1:14 AM, ant elder <[EMAIL PROTECTED]> wrote:
On Fri
Hi Adriano,
If there is an option on retrotranslator to retrotranslate all the classes
> in a folder, it should work as well as it works on classes inside .jar
> files. So, I think you should try to understand why your first approach
> (retrotranslating the eclipse project classes) is not working
This was raised a few weeks ago here on this thread:
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg31241.html
On Fri, Jun 6, 2008 at 4:16 PM, Gilbert Kwan <[EMAIL PROTECTED]> wrote:
> Also, the namespace convention does not match to the section 2.3.2 of
> WS Binding Spec V1.0, saying
vtest to test generated wsdl
Key: TUSCANY-2375
URL: https://issues.apache.org/jira/browse/TUSCANY-2375
Project: Tuscany
Issue Type: Test
Components: Java SCA Verification Tests
Affects Versions: Jav
Did you try mvn -U ?
On Fri, Jun 6, 2008 at 10:18 AM, kelvin goodson <[EMAIL PROTECTED]> wrote:
> Hi Luciano,
> yes, I added that workaround, and that satisfied most of the EMF jars,
> but not these two. It's odd, the 2 jars we need are there in the repository
> you suggested, but maven will n
Mark Little wrote:
Hi, I just wanted to let people know officially that people from Red
Hat/JBoss will be getting involved with Tuscany over the coming months
as we look at the best way in which to provide SCA support for our SOA
Platform users. We're very excited about helping on Tuscany and
Also, the namespace convention does not match to the section 2.3.2 of
WS Binding Spec V1.0, saying:
"The target namespace of the WSDL document, and of the service, ports
and generated binding elements is:
Base System URI for HTTP / Component Name / Service Name"
Gilbert
On Fri, Jun 6,
[
https://issues.apache.org/jira/browse/TUSCANY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-2361.
---
Resolution: Fixed
Patch applied under r664103. Thanks,
> Databinding tests for primitives
[
https://issues.apache.org/jira/browse/TUSCANY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603160#action_12603160
]
Raymond Feng commented on TUSCANY-2371:
---
I applied the 1st patch and fixed a bunch
Hi Oscar,
Yup, you're right - there are indeed Eclipse files inside the folders. I
guess I was confused by the different names in [1] than those that result
[2] from importing to an Eclipse workspace - after which I see 13 projects
in both cases. So please ignore my previous remark.
I have added
Hi Adriano,
> Yep, they should be imported, if you check inside its folders, there are
> the
> eclipse project files, so they should be identified by the eclipse import
> tool as an eclipse project.
Yup, you're right - there are indeed Eclipse files inside the folders. I
guess I was confused by
Hi Luciano,
yes, I added that workaround, and that satisfied most of the EMF jars,
but not these two. It's odd, the 2 jars we need are there in the repository
you suggested, but maven will not download them.
Kelvin.
2008/6/6 Luciano Resende <[EMAIL PROTECTED]>:
> Did you try the workaround
I guess that would be me as the fix I did outlined another issue (as
described in the thread Luciano pointed at). So you guys expect to always
have all the tests passing on trunk all the time?
Cheers,
Matthieu
On Thu, Jun 5, 2008 at 12:57 PM, Mike Edwards <
[EMAIL PROTECTED]> wrote:
> Folks,
>
>
Run as Tuscany fails if workspace folder has name with space
-
Key: TUSCANY-2374
URL: https://issues.apache.org/jira/browse/TUSCANY-2374
Project: Tuscany
Issue Type: Bug
Did you try the workaround I mentioned before on this thread [1] where
I added a new repository ? It was actually for other jars, but might
help in this case as well...
[1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg31727.html
On Fri, Jun 6, 2008 at 4:56 AM, kelvin goodson <[EMAIL P
This is very good news. Welcome !!!
On Fri, Jun 6, 2008 at 8:29 AM, Raymond Feng <[EMAIL PROTECTED]> wrote:
> It's fantastic to see you folks come on board. Welcome!
> Thanks,
> Raymond
> --
> From: "Mark Little" <[EMAIL PROTECTED]>
> Sent: Friday, J
[
https://issues.apache.org/jira/browse/TUSCANY-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-2361:
-
Assignee: Raymond Feng
> Databinding tests for primitives and primitive arrays - local
[
https://issues.apache.org/jira/browse/TUSCANY-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-2371:
-
Assignee: Raymond Feng (was: Vamsavardhana Reddy)
> Databinding tests for StandardType
I have 2 services defined in a composite as,
http://localhost:8080/CComponent/CService"/>
I got both WSDL docs by
- http://localhost:8080/BComponent?wsdl
- http://localhost:8080/CComponent/CService?wsdl
and got their t
Simon Laws wrote:
On Fri, Jun 6, 2008 at 3:33 PM, ant elder <[EMAIL PROTECTED]> wrote:
On Fri, Jun 6, 2008 at 2:49 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
Simon Nash wrote:
I did a recent svn update and rebuild and I'm seeing the following test
error from the helloworld-bpel sample. Are
Hi All,
Here is the more detail regarding error...
I have trace the error and found that exceptino source is from method
"getInitialContext()" of
"org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactory"
Here is the complete stack trace
org.apache.tuscany.sca.binding.jms.impl.JMSBinding
On Thu, May 22, 2008 at 11:55 AM, ant elder <[EMAIL PROTECTED]> wrote:
> We can also look at doing an official ASF press release, a couple of
> examples are the Synapse ones at [1] and [2]. We probably want to wait till
> we have the website migrated to the TLP before sending that out but I'll
On Fri, Jun 6, 2008 at 3:33 PM, ant elder <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 6, 2008 at 2:49 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
>
> > Simon Nash wrote:
> >
> >> I did a recent svn update and rebuild and I'm seeing the following test
> >> error from the helloworld-bpel sample. Are oth
On Fri, Jun 6, 2008 at 2:49 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> Simon Nash wrote:
>
>> I did a recent svn update and rebuild and I'm seeing the following test
>> error from the helloworld-bpel sample. Are other people seeing this?
>> Any ideas?
>>
>> Simon
>>
>> I have committed a fix (
Simon Nash wrote:
I did a recent svn update and rebuild and I'm seeing the following test
error from the helloworld-bpel sample. Are other people seeing this?
Any ideas?
Simon
I have committed a fix (or at least a workaround) for this build
break problem. The revision number is r663938.
I
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603038#action_12603038
]
Rajini Sivaram commented on TUSCANY-2343:
-
Daniel,
Now that is good progress, th
On Fri, Jun 6, 2008 at 1:35 PM, Ramkumar R <[EMAIL PROTECTED]> wrote:
> Hi Simon,
> After disabling most of the exceptions, now i face a problem in the itest
> validations as we generally check for the last reported problem to verify
> the results. Now due to disabled exception the processing cont
[
https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam updated TUSCANY-2347:
-
Attachment: TUSCANY-2347-Part5.patch
> Removing the exception throws from the p
[
https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramkumar Ramalingam updated TUSCANY-2347:
-
Attachment: TUSCANY-2347-Part4.patch
> Removing the exception throws from the p
ant elder wrote:
+1 from me.
+1 from me also. Seems like a good time.
--
Thanks, Dan Becker
Hi Simon,
After disabling most of the exceptions, now i face a problem in the itest
validations as we generally check for the last reported problem to verify
the results. Now due to disabled exception the processing continues furthur
and more problems are reported even after the one we are expectin
[
https://issues.apache.org/jira/browse/TUSCANY-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated TUSCANY-2373:
-
Attachment: TUSCANY-2373-testcase.patch
TUSCANY-2373-testcase.patch: A testcase
Done. TUSCANY-2373.
++Vamsi
On Fri, Jun 6, 2008 at 4:46 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> Vamsavardhana Reddy wrote:
>
>> I have the following method in my service interface that uses binding.ws:
>> Bean1 getTypeUnbound(T[] anArray);
>>
>> I am getting the following exception in S
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603010#action_12603010
]
Daniel Stucky commented on TUSCANY-2343:
Hi Rajini,
Thanks again for your help !
I've made all the changes required in the tag [1] to get rid of the felix
jars, find and include the emf jars, and I've removed the incubating tag,
DISCLAIMER files etc. However, I'm currently stumped as to why two emf
jars available [2] and [3] don't get downloaded by the build. The build
outp
Vamsavardhana Reddy wrote:
I have the following method in my service interface that uses binding.ws:
Bean1 getTypeUnbound(T[] anArray);
I am getting the following exception in SCADomain.newInstance()
Please open a JIRA for this, with a test case.
Simon
org.osoa.sca.ServiceRuntimeExce
Simon Laws wrote:
On Fri, Jun 6, 2008 at 9:17 AM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
How about 1.5-SNAPSHOT ? This would probably give us some room to have
couple releases without the necessity to keep updating the trunk pom
version. And this would probably make everybody happy :)
On F
[
https://issues.apache.org/jira/browse/TUSCANY-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602993#action_12602993
]
ant elder commented on TUSCANY-2274:
One interesting part of this is it rarely happen
ant elder wrote:
On Fri, Jun 6, 2008 at 11:12 AM, Simon Laws <[EMAIL PROTECTED]>
wrote:
On Fri, Jun 6, 2008 at 10:57 AM, Mark Little <[EMAIL PROTECTED]> wrote:
Hi, I just wanted to let people know officially that people from Red
Hat/JBoss will be getting involved with Tuscany over the coming
On 6/5/08, Simon Laws <[EMAIL PROTECTED]> wrote:
>
> >
> > Here the processor would never throw ContributionReadException, when the
> > exceptions are blocked as most of the ContributionReadException are of
> > type1, 2 or 3.
>
>
> Do you mean type 2, 3 & 4 here. I still expect us to throw type 1
On Fri, Jun 6, 2008 at 11:12 AM, Simon Laws <[EMAIL PROTECTED]>
wrote:
> On Fri, Jun 6, 2008 at 10:57 AM, Mark Little <[EMAIL PROTECTED]> wrote:
>
> > Hi, I just wanted to let people know officially that people from Red
> > Hat/JBoss will be getting involved with Tuscany over the coming months as
[
https://issues.apache.org/jira/browse/TUSCANY-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Rutherford closed TUSCANY-2372.
-
Resolution: Won't Fix
Upgrading JDK to 1.6.0_05 or later seems to fix this issue.
> Un
On Fri, Jun 6, 2008 at 10:57 AM, Mark Little <[EMAIL PROTECTED]> wrote:
> Hi, I just wanted to let people know officially that people from Red
> Hat/JBoss will be getting involved with Tuscany over the coming months as we
> look at the best way in which to provide SCA support for our SOA Platform
Hi, I just wanted to let people know officially that people from Red
Hat/JBoss will be getting involved with Tuscany over the coming months
as we look at the best way in which to provide SCA support for our SOA
Platform users. We're very excited about helping on Tuscany and
complimenting th
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602965#action_12602965
]
Rajini Sivaram commented on TUSCANY-2343:
-
Daniel,
Thank you for doing this. I t
On Fri, Jun 6, 2008 at 9:17 AM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
> How about 1.5-SNAPSHOT ? This would probably give us some room to have
> couple releases without the necessity to keep updating the trunk pom
> version. And this would probably make everybody happy :)
>
> On Fri, Jun 6, 2
That seems a little odd to me, i'd prefer just "snapshot", 1.x, or the
actual next number over 1.5.
...ant
On Fri, Jun 6, 2008 at 9:17 AM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
> How about 1.5-SNAPSHOT ? This would probably give us some room to have
> couple releases without the necessit
+1 from me. Incidentally I've spent a bit of time over the last couple of
days trying all the various samples and demos etc with the latest trunk code
and its all looking in quite good shape so it does seem like a fine time to
be taking a release branch.
...ant
On Fri, Jun 6, 2008 at 9:21 AM,
[
https://issues.apache.org/jira/browse/TUSCANY-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602951#action_12602951
]
Daniel Stucky commented on TUSCANY-2343:
Hi Rajini,
as suggested I debugged the
It's been a little while now since we did our 1.2 release. Since then there
has been lots of activity and of course we have graduated. It feels like the
right time to do a 1.3 release. Looking back at the mail list over the last
couple of months there are quite a few candidates for inclusion that I
How about 1.5-SNAPSHOT ? This would probably give us some room to have
couple releases without the necessity to keep updating the trunk pom
version. And this would probably make everybody happy :)
On Fri, Jun 6, 2008 at 1:14 AM, ant elder <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 6, 2008 at 9:05 AM
On Fri, Jun 6, 2008 at 9:05 AM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
> I guess part of problem here is because a lot of people assume that
> the maven artifact version represents what is going to be our next
> release and then, if it's set as 2.0-SNAPSHOT, it means our next
> release would b
I guess part of problem here is because a lot of people assume that
the maven artifact version represents what is going to be our next
release and then, if it's set as 2.0-SNAPSHOT, it means our next
release would be 2.0. But I tend to take these two pieces as two
different things, the maven pom ve
Which number?
If we pick the next number - we've just done a 1.2 release so the trunk
version could now be "1.3-SNAPSHOT" which is the way we've done in the past
- then every time we branch for the next release we also have to update the
trunk. Thats a bit more work but also it means that *everyo
On Fri, Jun 6, 2008 at 8:50 AM, Luciano Resende <[EMAIL PROTECTED]>
wrote:
> I was trying to use a reference with multiplicity (see composite
> below), and looks like the reference is being populated with two
> references for the same component, instead of one reference for each
> component. Any
I was trying to use a reference with multiplicity (see composite
below), and looks like the reference is being populated with two
references for the same component, instead of one reference for each
component. Any ideas why this is happening ?
BTW, I'm using the Eclipse Plugin from 1.2 release to
Ant,
+1 in general - by why not simply choose a number, rather than "x"?
- the problem with "x" is "what comes next?"
Yours, Mike.
ant elder wrote:
Lots of different views so far on this thread, better than no one replying
:) I'm tempted to go with "1.x-SNAPSHOT" as I think from whats been s
On Thu, Jun 5, 2008 at 8:43 PM, Simon Nash <[EMAIL PROTECTED]> wrote:
> Simon Laws wrote:
>>
>> On Wed, Jun 4, 2008 at 1:34 PM, Giorgio Zoppi <[EMAIL PROTECTED]> wrote:
>>
>>> 2008/6/4 ant elder <[EMAIL PROTECTED]>:
Currently the trunk has a version of 2.0-incubating-SNAPSHOT, we need
to
64 matches
Mail list logo
