Hi,
Just answer your karaf question on karaf mailling list.
And about this cxf in OSGi issue, could you please create a cxf jira
tickets and append your testcase there?
Thanks
Freeman
On 2011-8-27, at 上午2:40, Barry Hathaway wrote:
Dan,
Thanks for your suggestion. I downloaded TSF, but unf
> -Original Message-
> From: KARR, DAVID (ATTSI)
> Sent: Friday, August 26, 2011 2:19 PM
> To: users@cxf.apache.org
> Subject: Is the "Request Context" essentially a ThreadLocal?
>
> I consider this mostly a rhetorical question, but I need to ask it
> nevertheless.
>
> If your thread has
I created the one:
https://issues.apache.org/jira/browse/CXF-3770
I was planning to get to it ear;y next week - see if you can get a
chance, if not then I'll get it fixed shorlty
Cheers, Sergey
On 26/08/11 23:07, Jason Chaffee wrote:
I will see if I can get to it and supply a patch. Is the
I will see if I can get to it and supply a patch. Is there a jira number or
link for this?
-Original Message-
From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
Sent: Monday, August 22, 2011 4:06 AM
To: users@cxf.apache.org
Subject: Re: Enum as one of the query params in wadl
Will
I consider this mostly a rhetorical question, but I need to ask it nevertheless.
If your thread has a Port object, and you get the request context from that,
and you have another thread referencing the same Port object, and it gets the
request context, are those two request contexts always going
Hi,
I'm building a JAX-RS service with CXF 2.4.2 and JAXB for the bindings
(Java 1.6.0_26).
My response contains elements from two namespaces and it is correctly
rendered.
The second namespace gets automatically the prefix "ns2" which I have to
change to something more "meaningful" for a third-pa
Dan,
Thanks for your suggestion. I downloaded TSF, but unfortunately I got
the exact same result.
I also tried upgrading javax.xml.ws (in both SMX and TSF), but that
didn't work - see my posting on
karaf-user:
http://karaf.922171.n3.nabble.com/Starting-bundle-ignores-exports-td3285286.html
Ba
Hi,
If you post this to the Atomikos forums then I am sure somebody will help
there...
Basically, you need to:
-use Atomikos as the Spring transaction manager - see the Atomikos samples in
the download
-use Atomikos JDBC datasources
HTH
Guy
On 26-aug-2011, at 18:41, mymacin wrote:
Hi ever
On Wednesday, August 24, 2011 4:46:06 AM klerisson wrote:
> Greetings!
>
> Is there any example on CXF client consuming a WCF with WSHTTPBinding?
>
> Does anybody know how to achieve such integration?
If you can get the WSDL from the WsHTTPBinding based service, it more or less
should just work
On Wednesday, August 24, 2011 9:20:09 PM Stevo Slavić wrote:
> It would help if cxf-codegen-plugin had its configuration object model
> as separate module and if that module was an OSGi bundle. If not
> separate module for the config model, then at least entire plugin
> module to be an OSGi bundle.
Hi,
I'm building a JAX-RS service with CXF 2.4.2 and JAXB for the bindings
(Java 1.6.0_26).
My response contains elements from two namespaces and it is correctly
rendered.
The second namespace gets automatically the prefix "ns2" which I have
to change to something more "meaningful" for a
Hi every one,
Is it possible to acheive global jdbc transctions in spring.I have already
tried atomikos with cxf but no use.Can anyone help me on this.
How i can make it work global transaction with cxf.
Thanks in advance
Mymacin.
--
View this message in context:
http://cxf.547215.n5.nabble.com
When doing java-first stuff, the WSDL that we generate uses inline schemas as
it simplified things quite a bit. When inlining the schemas, there shouldn't
be schemaLocations on the imports. JAXB sticks kind of "fake"
schemaLocations there that we strip off.
Dan
On Friday, August 26, 2011
Ok, I was considering that but all the samples I saw then depended on the
WSDL:s which we dont want.
But it seems you are saying that once I generated the wsdl:s and then
back-generated the code (to get it correct) I should be able to discard the
wsdl:s if we want and depend only on the code decl
Hi Dennis
On 26/08/11 16:28, Dennis Sosnoski wrote:
Hi Sergey,
On 08/26/2011 09:37 PM, Sergey Beryozkin wrote:
On Fri, Aug 26, 2011 at 7:04 AM, Dennis Sosnoski wrote:
...
The principle of being strict in what you send, open in what you expect,
is what led to the browser wars on the web. Eac
On Friday, August 26, 2011 8:24:53 AM suryavikas wrote:
> Dan
>
> Thank you for clarifying my doubt on this, I also suspected this, and based
> on some of the examples you have given, I had successfully integrated
> session management into CXF 2.4.1 using the read phase.
>
> I have one more doubt
Am 26.08.2011 17:28, schrieb Dennis Sosnoski:
Ok, it's true that Postel's principle didn't really lead to the
browser wars on the web. The people who were producing content were
violating the principle by being sloppy in what they produced, and the
browsers had a competition to try to work with
On Friday, August 26, 2011 5:25:45 PM Christian Schneider wrote:
> Hi Dan,
>
> I did not know this. Since when is it done?
Oct 2, 2009. Quite a while. :-) I think it was 2.2.4 or so. Long time
ago.
> I think it is not so good to fail on invalid elements. As web services
> are often use
Hi Sergey,
On 08/26/2011 09:37 PM, Sergey Beryozkin wrote:
> On Fri, Aug 26, 2011 at 7:04 AM, Dennis Sosnoski wrote:
>> ...
>>
>> The principle of being strict in what you send, open in what you expect,
>> is what led to the browser wars on the web. Each browser implemented its
>> own way of hand
Hi Dan,
I did not know this. Since when is it done?
I think it is not so good to fail on invalid elements. As web services
are often used in loosely coupled scenarios I really liked that it did
not complain before.
At least it would be good to have a simple switch to turn that feature off.
C
Dan
Thank you for clarifying my doubt on this, I also suspected this, and based
on some of the examples you have given, I had successfully integrated
session management into CXF 2.4.1 using the read phase.
I have one more doubt, now as I am not using receive phase, instead I am
using READ phase,
On 08/26/2011 06:36 PM, Christian Schneider wrote:
> The problem is that strict versioning and loose coupling do not really
> match.
Agreed-on data formats are what makes loose coupling possible. If you
publish a data format that you don't follow, you're forcing your clients
to use tools which als
Creating the async methods can be tricky as the request object gets unwrapped,
the the wrapper object is used for the callback.
My suggestion is to create your service, grab the wsdl, and generate a client
with it enabling the async methods. (with 2.4.2, you can pass -asyncMethods
flag).
On Friday, August 26, 2011 6:04:20 PM Dennis Sosnoski wrote:
> Hi Christian,
>
> It's true that JAXB ignores schemas by default, just matching elements
> by name and ignoring any extra (or missing) ones.
Actually, by default, CXF configures JAXB to NOT ignore any extra elements.
Thus, this idea
With 2.4.x, the WSDL and schema requests are also routed onto the interceptor
chain as GET requests to allow the chain and interceptors to participate in
various parts of the WSDL requests.
The best option is to add:
String method = (String)message.get(Message.HTTP_REQUEST_METHOD);
Thanks a lot!
On Fri, Aug 26, 2011 at 6:51 AM, Sergey Beryozkin wrote:
> Hi
>
> the following feature has been created specifically for addressing the
> requirements like yours,
>
>
> http://cxf.apache.org/docs/jax-rs-advanced-features.html#JAX-RSAdvancedFeatures-RESTfulserviceswithoutannotatio
Hi,
Could you please create a jira ticket and append your testcase there?
Freeman
On 2011-8-25, at 下午11:25, robbywillz wrote:
Hi,
I've tried with CXF 2.3.6, the problem still exists.
When the SOAP attachment size is big, the DataHandler returning empty
content, even in 2.3.6 version.
I've als
Hi,
I've tried with CXF 2.3.6, the problem still exists.
When the SOAP attachment size is big, the DataHandler returning empty
content, even in 2.3.6 version.
I've also found that its using org.apache.cxf.attachment.LazyDataSource and
returns empty, same returns content of attachment size is small
Hi
the following feature has been created specifically for addressing the
requirements like yours,
http://cxf.apache.org/docs/jax-rs-advanced-features.html#JAX-RSAdvancedFeatures-RESTfulserviceswithoutannotations
Cheers, Sergey
On Thu, Aug 25, 2011 at 7:35 PM, Osvaldo Pina wrote:
> Hi,
>
>
Hi
On Fri, Aug 26, 2011 at 12:32 AM, dstainer wrote:
> Interesting feature, is there a way to do something dynamic based off message
> content? For example, could it remove a value if based off another fields
> contents, or something like that?
>
Not at the moment - users usually create custom in
Hi Dennis
On Fri, Aug 26, 2011 at 7:04 AM, Dennis Sosnoski wrote:
> Hi Christian,
>
> It's true that JAXB ignores schemas by default, just matching elements
> by name and ignoring any extra (or missing) ones. But if you start
> developing web services on this basis you're setting yourself up for
Now I did some small modifcations to my interfaces so I created a sample
service with a method declared like:
@WebMethod(operationName = "doAdd")
String doAdd(
@WebParam(name = "a") String a,
@WebParam(name = "b") String b);
@WebMethod(operationName = "doAdd")
@WebEndpoint(name="doAdd")
Future doA
32 matches
Mail list logo
