Hi,
We Observed Servicebeans created by
"org.apache.cxf.transport.servlet.CXFServlet” is always singleton. How can I
change their scope to prototype or in best case HTTP Session Scope? Please
Suggest.
*WEB.xml:*
CXFServlet
CXF Servlet
On 2010/06/17 0:29, Daniel Kulp wrote:
>
>
> The Apache CXF team recently discovered a security issue that may allow an
> attacker to carry out denial of service attacks and to read arbitrary files
> on
> the file system of the node where CXF runs. Details of the vulnerability are
> described
On Wednesday 16 June 2010 10:00:03 pm Nikolay Elenkov wrote:
> On 2010/06/17 0:29, Daniel Kulp wrote:
> > The Apache CXF team recently discovered a security issue that may allow
> > an attacker to carry out denial of service attacks and to read arbitrary
> > files on the file system of the node whe
I believe the easiest way to do it is to just use the Spring AOP stuff and set
the bookService bean to be scope=session. Spring will handle the rest.
Dan
On Thursday 17 June 2010 6:19:21 am Balaji Sankar Chopparapu wrote:
> Hi,
>
>
>
> We Observed Servicebeans created by
> "org.apache.cxf
Hi
JAXRS module also ships prototypes aware factories :
http://cxf.apache.org/docs/jax-rs.html#JAX-RS-Lifecyclemanagement
cheers, Sergey
On Thu, Jun 17, 2010 at 2:57 PM, Daniel Kulp wrote:
>
>
> I believe the easiest way to do it is to just use the Spring AOP stuff and
> set
> the bookService
Hi all ,
When we update to jaxws 2.2 , we have to endorse the jaxws api jar for
jdk6. I've updated the jaxws api dependency to 2.2 and endorsed the
jaxws api 2.2 jar to maven surefire and compiler plugin . If there
is no objection , I will check in this change .
We also need to look at endorsing
BTW, what does "endorse" mean here--I don't understand the concept.
Thanks,
Glen
jim ma wrote:
>
> Hi all ,
>
> When we update to jaxws 2.2 , we have to endorse the jaxws api jar for
> jdk6. I've updated the jaxws api dependency to 2.2 and endorsed the
> jaxws api 2.2 jar to maven surefire
More or less putting it in the boot classpath.
On Thu, Jun 17, 2010 at 12:30 PM, Glen Mazza wrote:
>
> BTW, what does "endorse" mean here--I don't understand the concept.
>
> Thanks,
> Glen
>
>
> jim ma wrote:
>>
>> Hi all ,
>>
>> When we update to jaxws 2.2 , we have to endorse the jaxws api j
I'm not sure that actually is needed, from the jax-ws website -
JDK 6u4 includes JAX-WS 2.1 and JAXB 2.1 API and RI. JAX-WS RI 2.2EA includes
newer and enhanced RI of JAX-WS/JAXB 2.1. In order to run JAX-WS RI 2.2EA you
would need to put the jars in the classpath(endorsed mechanism is not requi
On Thursday 17 June 2010 12:02:41 pm jim ma wrote:
> Hi all ,
>
> When we update to jaxws 2.2 , we have to endorse the jaxws api jar for
> jdk6. I've updated the jaxws api dependency to 2.2 and endorsed the
> jaxws api 2.2 jar to maven surefire and compiler plugin . If there
> is no objection ,
Christian,
Did the stuff that is marked "Moved to User´s Guide" ever actually get moved?
I don't see them there.
Thanks!
Dan
On Monday 07 June 2010 12:50:55 pm Daniel Kulp wrote:
> I like all the changes EXCEPT the removal of the Mailing Lists.I really
> don't consider the mailing li
I'd like to try and get a handle on what is needed to get 2.3 out the door.
It's really long, long overdue. The things I can think of off the top of
my head:
1) JAX-WS 2.2 - we're close on this, just need to figure out a few more
things.
2) JAX-RS 1.1 - Sergey: do you know how close we
Hi - good to see the OAuth project going on - let us know if there's
anything that we can help with.
I've looked through the initial commits, looks good. I was about to tell you
a CXF 'application' code does not explicitly depends on Spring but you've
removed that one :-).
Just for the record, Tom
On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
> Hi - good to see the OAuth project going on - let us know if there's
> anything that we can help with.
> I've looked through the initial commits, looks good. I was about to tell
> you a CXF 'application' code does not explicitly depends
JAXB 2.2.1[1]?
[1] http://old.nabble.com/-ANN--JAXB-2.2.1-is-released-td28583411.html
dkulp wrote:
>
> Anything else anyone can think of?
>
--
View this message in context:
http://old.nabble.com/Stuff-left-for-2.3--tp28917374p28918191.html
Sent from the cxf-dev mailing list archive at Nabb
On Thursday 17 June 2010 2:42:33 pm Glen Mazza wrote:
> JAXB 2.2.1[1]?
>
> [1] http://old.nabble.com/-ANN--JAXB-2.2.1-is-released-td28583411.html
That falls into the JAX-WS 2.2 stuff as JAX-WS 2.2 requires it.It's also
in the "it required endorsing the 2.2 api jar" thing to work, which suck
Hi,
On Thu, Jun 17, 2010 at 7:43 PM, Daniel Kulp wrote:
> On Thursday 17 June 2010 1:31:30 pm Sergey Beryozkin wrote:
>> Just for the record, Tomasz's project is also going well
>Well, for the record, I haven't seen anything on the dev list about it yet.
>Thus, from CXF/Apache's point of view
Hi Tomasz
I think you're doing really well; I agree with Dan that we'd like to see
more discussions on the dev list but it's my fault I did not CC to the dev
list during our last exchange :-) but I think i did not do it because the
links to the slides were pointing to your own album.
Please don't
Hi Dan
On Thu, Jun 17, 2010 at 6:25 PM, Daniel Kulp wrote:
>
> I'd like to try and get a handle on what is needed to get 2.3 out the door.
> It's really long, long overdue. The things I can think of off the top
> of
> my head:
>
> 1) JAX-WS 2.2 - we're close on this, just need to figure out
Hi,
On Fri, Jun 18, 2010 at 12:15 AM, Sergey Beryozkin wrote:
> Hi Tomasz
>
> I think you're doing really well; I agree with Dan that we'd like to see
> more discussions on the dev list but it's my fault I did not CC to the dev
> list during our last exchange :-) but I think i did not do it becau
Hi,
Consider the following Java class which provides simple echoString service.
public interface EchoService {
String echoString(String content);
}
I exposed it as a Web service using the following code.
EchoServiceImpl echoServiceImpl = new EchoServiceImpl();
ServerFactoryBean svrFactory
Hi,
I'm getting the following error (for both the simple types case and complex
types case) when I feed the XMLStreamReader to Unmarshalling context without
the following workaround[2]. It seems that the problem occurs when the
XMLStreamReader is used by JiBX framework to access an element which a
Well, another option to consider (I'm not saying this is the way to go, just
something to consider. I don't even know if this is possible with JIBX) is
how the JAXWS/JAXB code handles this
With JAX-WS/JAXB, it uses ASM to generate, in memory, classes for the wrapper
element which contains
Hi all ,
When I build distribution module I got this failure :
POM Location: /x1/code/cxf/trunk/distribution/pom.xml
Validation Messages:
[0] 'dependencies.dependency.version' is missing for ant:ant
Reason: Failed to validate POM for project org.apache.cxf:apache-cxf
at /x1/code/cxf/trunk/dis
Hi,
Daniel Kulp wrote:
I'd like to try and get a handle on what is needed to get 2.3 out the door.
It's really long, long overdue. The things I can think of off the top of
my head:
1) JAX-WS 2.2 - we're close on this, just need to figure out a few more
things.
2) JAX-RS 1.1 - Sergey:
25 matches
Mail list logo
