You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2006/09/18 23:49:22 UTC
[jira] Created: (CXF-94) Javascript frontend should not be provider
based
Javascript frontend should not be provider based
------------------------------------------------
Key: CXF-94
URL: http://issues.apache.org/jira/browse/CXF-94
Project: CeltiXfire
Issue Type: Improvement
Components: Dynamic Languages
Reporter: Daniel Kulp
Priority: Minor
The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CXF-94) Javascript frontend should not be provider
based
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/CXF-94?page=all ]
Bozhong Lin updated CXF-94:
---------------------------
Fix Version/s: 2.0-RC
Description:
The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
was:
The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
Affects Version/s: 2.0-RC
> Javascript frontend should not be provider based
> ------------------------------------------------
>
> Key: CXF-94
> URL: http://issues.apache.org/jira/browse/CXF-94
> Project: CXF
> Issue Type: Improvement
> Components: Dynamic Languages
> Affects Versions: 2.0-RC
> Reporter: Daniel Kulp
> Priority: Minor
> Fix For: 2.0-RC
>
>
> The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
> Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (CXF-94) Javascript frontend should not be
provider based
Posted by "Adi Sakala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adi Sakala reassigned CXF-94:
-----------------------------
Assignee: Peter Jones
> Javascript frontend should not be provider based
> ------------------------------------------------
>
> Key: CXF-94
> URL: https://issues.apache.org/jira/browse/CXF-94
> Project: CXF
> Issue Type: Improvement
> Components: Dynamic Languages
> Affects Versions: 2.0-RC
> Reporter: Daniel Kulp
> Assigned To: Peter Jones
> Priority: Minor
> Fix For: 2.0-RC
>
>
> The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
> Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-94) Javascript frontend should not be provider
based
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-94:
---------------------------
Fix Version/s: (was: 2.1)
> Javascript frontend should not be provider based
> ------------------------------------------------
>
> Key: CXF-94
> URL: https://issues.apache.org/jira/browse/CXF-94
> Project: CXF
> Issue Type: Improvement
> Components: Dynamic Languages
> Affects Versions: 2.0
> Reporter: Daniel Kulp
> Assignee: Peter Jones
> Priority: Minor
>
> The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
> Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-94) Javascript frontend should not be provider
based
Posted by "Bozhong Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bozhong Lin updated CXF-94:
---------------------------
Fix Version/s: (was: 2.0-RC)
2.0
Affects Version/s: (was: 2.0-RC)
2.0
> Javascript frontend should not be provider based
> ------------------------------------------------
>
> Key: CXF-94
> URL: https://issues.apache.org/jira/browse/CXF-94
> Project: CXF
> Issue Type: Improvement
> Components: Dynamic Languages
> Affects Versions: 2.0
> Reporter: Daniel Kulp
> Assigned To: Peter Jones
> Priority: Minor
> Fix For: 2.0
>
>
> The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
> Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CXF-94) Javascript frontend should not be provider
based
Posted by "Dan Diephouse (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Diephouse updated CXF-94:
-----------------------------
Fix Version/s: (was: 2.0)
2.1
Scheduling for 2.1
> Javascript frontend should not be provider based
> ------------------------------------------------
>
> Key: CXF-94
> URL: https://issues.apache.org/jira/browse/CXF-94
> Project: CXF
> Issue Type: Improvement
> Components: Dynamic Languages
> Affects Versions: 2.0
> Reporter: Daniel Kulp
> Assigned To: Peter Jones
> Priority: Minor
> Fix For: 2.1
>
>
> The Javascript frontend should not be provider based. Currently, the javascript frontend uses the JAX-WS provider capabilities to do it's work. That is "overkill" and should not be necessary. It should interact with the "core" much like the JAX-WS frontend does.
> Also, it should provide it's own reader/writer things to do the StAX <---> E4X to avoid the whole StAX <--> DOM <---> E4X extra conversions.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.