Support wire multiplicty in JavaScript components
-
Key: TUSCANY-74
URL: http://issues.apache.org/jira/browse/TUSCANY-74
Project: Tuscany
Type: Bug
Components: Java SCA JavaScript Container
Reporter: Jim Marino
As a heads up, I will need to make some some modifications to the
builder and proxy configuration to support multiplicity. Specifically:
- RuntimeConfiguration.getSourceProxyFactories() returns
List as opposed to a Map keyed by reference name. This
needed to be changed since there exists 1.
ant elder wrote:
What would be in the core namespace of a PHP SCA runtime?
If a goal is to be able to take any SCA module and deploy it unchanged in
any SCA runtime then doesn't it have to be consistent - either everything in
the core namespace or everything in its own namespace?
...ant
On
[ http://issues.apache.org/jira/browse/TUSCANY-38?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-38:
---
Resolution: Fixed
This is now fixed. The bootstrap code has been integrated with a Tomcat Host
implementation and a Servlet listener
[ http://issues.apache.org/jira/browse/TUSCANY-41?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-41:
---
Resolution: Fixed
All the test cases pass, this is now fixed.
> Wire builder algorithm uses incorrect scope container
>
I created a new JIRA component for our JavaScript container. The name of
the component is Java SCA JavaScript Container. We can use it to report
issues with this module.
--
Jean-Sebastien
[ http://issues.apache.org/jira/browse/TUSCANY-44?page=all ]
Jean-Sebastien Delfino updated TUSCANY-44:
--
Component: Java SCA JavaScript Container
Moving to the correct JIRA component
> Resolve licensing issue with Rhino for JavaScript container
[ http://issues.apache.org/jira/browse/TUSCANY-68?page=all ]
Jean-Sebastien Delfino updated TUSCANY-68:
--
Component: Specification
This belongs to the specification JIRA component.
> Work with SDO spec group to resolve issues around INSTANCE
> -
[ http://issues.apache.org/jira/browse/TUSCANY-51?page=all ]
Jean-Sebastien Delfino updated TUSCANY-51:
--
Component: Java SCA Tomcat Integration
Moving to the correct component.
> Tomcat integration should provide Session scope context
> ---
[ http://issues.apache.org/jira/browse/TUSCANY-29?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-29:
---
Resolution: Fixed
> HelloWorldMC sample fails to build
> --
>
> Key: TUSCANY-29
> U
[ http://issues.apache.org/jira/browse/TUSCANY-29?page=all ]
Jean-Sebastien Delfino updated TUSCANY-29:
--
Component: Java Samples HelloWorld
Moving to the right JIRA component.
> HelloWorldMC sample fails to build
> -
[
http://issues.apache.org/jira/browse/TUSCANY-37?page=comments#action_12369373 ]
Jean-Sebastien Delfino commented on TUSCANY-37:
---
Mike, can you confirm that this has been fixed? Just double checking before
marking this resolved. Thanks.
> Mo
Which access modifiers on fields annotated with @Reference?
---
Key: TUSCANY-73
URL: http://issues.apache.org/jira/browse/TUSCANY-73
Project: Tuscany
Type: Sub-task
Components: Specification
Reporter: Je
[
http://issues.apache.org/jira/browse/TUSCANY-25?page=comments#action_12369370 ]
Jean-Sebastien Delfino commented on TUSCANY-25:
---
Here's what the SCA 0.9 spec says for @Properties:
The @Property annotation may be used irrespective of the acce
[ http://issues.apache.org/jira/browse/TUSCANY-46?page=all ]
Jean-Sebastien Delfino updated TUSCANY-46:
--
Component: Specification
(was: Java SCA Core)
The SCA specification does not specify a scope attribute that you can use i
[
http://issues.apache.org/jira/browse/TUSCANY-6?page=comments#action_12369364 ]
Jean-Sebastien Delfino commented on TUSCANY-6:
--
I suggest we actually remove getAllResources() and change getResources() to do
exactly what ClassLoader.getResource
[ http://issues.apache.org/jira/browse/TUSCANY-14?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-14:
---
Resolution: Fixed
Thanks for the patch. I made similar changes to all the WSDL files missing
definition names or soap addresses.
>
[ http://issues.apache.org/jira/browse/TUSCANY-14?page=all ]
Jean-Sebastien Delfino reassigned TUSCANY-14:
-
Assign To: Jean-Sebastien Delfino
> Some WSDLs used by the test cases don't conform to the WSDL schema
> -
[ http://issues.apache.org/jira/browse/TUSCANY-23?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-23:
---
Resolution: Fixed
This has been fixed as part of our bring-up session last week. The soap
addresses have been adjusted to match the
[ http://issues.apache.org/jira/browse/TUSCANY-1?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-1:
--
Resolution: Fixed
This is now fixed. The port of our build to Maven 2 is complete.
> port build process to Maven2
> ---
[ http://issues.apache.org/jira/browse/TUSCANY-59?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-59:
---
Resolution: Fixed
Jared, thanks for reporting this problem. I checked in a fix under revision
r384081.
> Invalid bundle dependenci
[ http://issues.apache.org/jira/browse/TUSCANY-59?page=all ]
Jean-Sebastien Delfino reassigned TUSCANY-59:
-
Assign To: Jean-Sebastien Delfino
> Invalid bundle dependencies in HellowWorld sub-projects
>
What would be in the core namespace of a PHP SCA runtime?
If a goal is to be able to take any SCA module and deploy it unchanged in
any SCA runtime then doesn't it have to be consistent - either everything in
the core namespace or everything in its own namespace?
...ant
On 3/7/06, Jean-Sebast
ant elder wrote:
(don't you hate the way gmail sends the mail before you've finished if you
hit the wrong key)
So the key problem here was that the standard Tuscany bindings aren't the
same as custom ones. Custom bindings and component types need to be in their
own namespace, and the SCDLModelLo
The trace I posted before is for a different bug - I forgot to uncomment
the definition in the SCDL. We should detect this and report
a better error (I'll open a JIRA).
Once I uncomment the SCDL, I get the real error:
org.apache.tuscany.core.context.TargetException: Component not found
[org.apac
[ http://issues.apache.org/jira/browse/TUSCANY-20?page=all ]
Frank Budinsky updated TUSCANY-20:
--
Priority: Minor (was: Major)
> Default SDO 2 types not available or working correctly
> --
>
>
Yea I hadn't implemented that case (also in the Java container).
I'll go back and do that now.
Jim
On Mar 7, 2006, at 8:33 AM, Jeremy Boynes wrote:
Jim Marino wrote:
Jeremy mentioned that intra-aggregate system component wires were not
working. I check some test cases in that exercise fu
The error message in the SystemEntryPointBuilder is not the most
helpful. I'm fixing wiring to List types now so I'll go in and
provide a more descriptive error as well.
Jim
On Mar 7, 2006, at 9:32 AM, ant elder wrote:
Ok, forget this. Brain dead coding in the scdl module loader.
On 3/7/
Ok, forget this. Brain dead coding in the scdl module loader.
On 3/7/06, ant elder <[EMAIL PROTECTED]> wrote:
>
> Unfortunately I still can't get this to work, although the assembly
> testcase now works if I try to use the new binding in an sca module in
> tomcat it fails to find the new binding.
Jim Marino wrote:
> Jeremy mentioned that intra-aggregate system component wires were not
> working. I check some test cases in that exercise functionality that
> was already in place. I'm probably missing something here so can
> someone let me know? I may be incorrectly generating the model in
Improve handling of Axis exceptions
---
Key: TUSCANY-72
URL: http://issues.apache.org/jira/browse/TUSCANY-72
Project: Tuscany
Type: Improvement
Components: C++ SCA
Reporter: Pete Robbins
Axis exceptions should be caught and h
Provide logging to file
---
Key: TUSCANY-71
URL: http://issues.apache.org/jira/browse/TUSCANY-71
Project: Tuscany
Type: New Feature
Components: C++ SCA
Reporter: Pete Robbins
Assigned to: Pete Robbins
Default internal logging for C++ S
Unfortunately I still can't get this to work, although the assembly testcase
now works if I try to use the new binding in an sca module in tomcat it
fails to find the new binding. It looks like the runtime is not correctly
picking up the new SCDL and it ignores the binding on entry points trying to
33 matches
Mail list logo