cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-94) Javascript frontend should not be provider based
Date Tue, 30 Jun 2009 15:21:47 GMT

     [ https://issues.apache.org/jira/browse/CXF-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-94.
----------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.3
         Assignee: Daniel Kulp  (was: Peter Jones)


With the dispatch/provider refactor, this isn't a big deal anymore.  I HAVE removed the JAX-WS
annotations from it so it doesn't look like a JAX-WS provider (and thus app server scanners
won't try to deploy it) which pretty much solves the big issues with it.



> 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: Daniel Kulp
>            Priority: Minor
>             Fix For: 2.2.3
>
>
> 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.


Mime
View raw message