ution (why it was I know not).
Overwriting locally the corresp. artifacts with these three modifications I
manage to get around the issue. Obviously this is not a solution to the problem.
What would you suggest?
Many thanks,
Matteo
> On 1 Jun 2021, at 10:45, Jean-Baptiste Onofre wrote:
&
060159.html
<http://karaf.922171.n3.nabble.com/OpenAPI-and-CXF-issues-with-Karaf-4-2-11-td4060159.html>
Matteo
> On 31 May 2021, at 12:02, Matteo Rulli wrote:
>
> Hello,
>
> I recently upgraded from CXF 3.3.2 to 3.4.0 and my rest endpoints stopped to
> work. I g
vice.http package within the cxf-rt-transports-http manifest
but I’m not sure if this is the way to go trying to solve this.
Could you please provide help?
Thank you,
Matteo
Hi Colm,
thank you for you answer!
I ended up doing this [1], in order to also return the modulus and the
private key.
I don't know whether it could be accomplish in a better way, maybe by
taking more advantage from the "JwkUtils" class!
Thank you for your help!
Best regards,
Hi,
is it possible to have a snippet on how to generate random JWK keys
(e.g. the JSON on [1])?
I was checking the official reference on [2], but could not figure out
how to do that.
Thanks
[1]
rom config-admin. Is this a good approach? Is there any example I could use as
a starting point to develop such a response filter?
Thank you,
Matteo
Hello,
I created an issue (https://issues.apache.org/jira/browse/CXF-7966) and
submitted a PR (https://github.com/apache/cxf/pull/510/).
Matteo
> On 22 Jan 2019, at 17:33, Colm O hEigeartaigh wrote:
>
> Hi,
>
> Please create a pull request and we will review it in more de
tch, getter type is %s while
setter type is %s",
accessor, getterClass.getName(),
setterClass.getName()));
}
}
}
If you think this is OK we can create a pull request with this.
Thank you,
Matteo
cannot register as
Filter extensions, right?
Besides, is it enough to have CXF bundles installed in my runtime to get the
"whiteboard magic" happen or do I need to set up and configure the CXF bus
somehow?
I really appreciate your help.
Matteo
-----
matteo
--
Sent from: http://cxf
CXF JAX-RS servers and CXF providers in this way?
Thank you very much,
Matteo
-
matteo
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
authentication header in place), the authorization invocation fails because
the securityContext.getUserPrincipal() returns null.
What is the right way in CXF to correctly populate the SecurityContext with
a sound user principal?
Many thanks again,
matte
-
matteo
--
View this message in context
? Is it
possible to serve a custom login form in case the
AuthorizationCodeGrantService detects that the Authorization header is
missing?
Many thanks.
matteo
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/How-to-manage-resource-owner-login-in-CXF-tp5766808.html
Sent
and the
other runtime bundles
- It does not require to modify the existing bundles that worked in versions
< 3.1.4
Honestly I still don't understand why the Bundle-ActivationPolicy: lazy has
been introduced.
m
-----
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CX
generate a launch config or a bndtools bndrun file
for cxf that makes sense without fighting with all the
karaf/felix/equinox/... idiosyncrasies?
Thanks,
matteo
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-3-1-4-bundles-remain-in-starting-state
a lazy
activation policy, then the bundle may remain in this state for some time
until the activation is triggered./ /Triggered/ seems a synonym of /first
class load from the bundle occurs/: probably the blueprint endpoint
configuration I'm using does not trigger the the cxf bundles activation?
either a launch configuration or a bndrun file
for cxf+OSGi out of the cxf distribution?
Thanks!
matteo
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-3-1-4-bundles-remain-in-starting-state-tp5763687.html
Sent from the cxf-user mailing list archive
Hi,
I enabled the cxf logs and I set logs level to /debug/ but I did not spot
any anomaly. Maybe it would be useful to enable the swagger logs, but I did
not find a way to configure them via osgi log service / log4j config.
I'll try to remote debug swagger flow as you suggested.
Thanks,
matteo
/
(I put the bundles in alphabetical order and I removed the
org.apache.karaf.* bundles):
Assuming bundle starting order does not matter, I cannot understand what is
the culprit in the first environment. Maybe some vm properties? What do you
think?
Thanks again,
matteo
-
matteo
--
View
http://localhost:8081/rest/users/swagger.json/*; actually what I get is
the following:
As you can see, it contains generic info and does not contain APIs details.
Could anyone spot what is missing here?
Thanks a lot.
-----
matteo
--
View this message in context:
http://cxf.547215.n5.nabble
required to serve the SOAP response make the TTL
check fails.
*My question is: why we need to check the TTL of InMessage here? *
Thank you!
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/JMSConduit-and-InMessage-TTL-tp5745854.html
Sent from the cxf-user mailing
Hi everybody,
please excuse me if I'm insisting, I did not receive any answer to my
request below,
may anyone please help me?
Thanks in advance,
Matteo
On 30/04/2014 16:12, Pampolini Matteo wrote:
Hello there,
I'm trying to subscribe to WS-Notification events on a remote device
Hi everybody,
please excuse me if I'm insisting, I did not receive any answer to my
request below, may anyone please help me?
Thanks in advance,
Matteo
On 30/04/2014 16:12, Pampolini Matteo wrote:
Hello there,
I'm trying to subscribe to WS-Notification events on a remote device
Hi everybody,
please excuse me if I'm insisting, I did not receive any answer to my
request below, may anyone please help me?
Thanks in advance,
Matteo
On 30/04/2014 16:12, Pampolini Matteo wrote:
Hello there,
I'm trying to subscribe to WS-Notification events on a remote device
hot to
relate it to Consumer or
NotificationBroker or whatever else.
May you please help me?
Many thanks in advance,
Matteo
This email and any attachments are confidential to the intended recipient and
may also be privileged. If you are not the intended recipient please delete it
from your
Hi Dan,
many thanks for your and all other replies. Just another question: how
can I pass WSSConfig
object to the WSS4J out interceptor in a legal way without hacking the
code?
Regards, Matteo
On 16/04/2014 17:19, Daniel Kulp wrote:
The WSSConfig object that is used to pass configuration
comment out the line:
message.getInterceptorChain().doIntercept(message);
the packet is transmitted, but my XML message to be modified is empty.
Any ideas? I really don't know how to go further...
Many thanks in advance,
Matteo
This email and any attachments are confidential to the intended
Hello Dan,
did you have the chance to further investigate this issue?
Many thanks in advance,
Matteo
On 27/01/2014 16:16, Pampolini Matteo wrote:
Hello Dan,
thanks for your quick reply. NullPointerException occurs just after few
response packets are received,
usually Discovery Proxy
have an idea of why bus is
null? I suspect
that the SOAP fault sent by WCF Discovery Proxy is intercepted, but then
the message
goes on for further processing causing the error.
Many many thanks once again in advance for your kind support,
Matteo
On 24/10/2013 18:40, Daniel Kulp wrote:
I really
Hello Dan,
thanks for your reply, I downloaded and tested snapshot
2.7.8-20131023.085812-20 but now, even with
WCF proxy stopped, I'm not able to find any device, am I doing anything
wrong?
Regards, Matteo
On 23/10/2013 22:21, Daniel Kulp wrote:
On Oct 23, 2013, at 8:37 AM, Pampolini Matteo
Thanks Dan,
WireShark shows me the discovery request sent and all the replies, and
handleResponse in
WSDiscoveryClient is called (I simply added a println there).
Regards, Matteo
On 24/10/2013 16:58, Daniel Kulp wrote:
On Oct 24, 2013, at 10:42 AM, Daniel Kulp dk...@apache.org wrote:
On Oct
:99)
at
org.apache.cxf.ws.discovery.WSDiscoveryClient$1.handleResponse(WSDiscoveryClient.java:357)
Matteo
On 24/10/2013 16:58, Daniel Kulp wrote:
On Oct 24, 2013, at 10:42 AM, Daniel Kulp dk...@apache.org wrote:
On Oct 24, 2013, at 10:05 AM, Pampolini Matteo matteo.pampol...@selex-es.com
in issue description the WS-Discover version
mentioned is 1.1, could it be that
the issue is still present when setting version 1.0, as requested by ONVIF
specs?
Any help is very appreciated, thanks in advance,
Matteo
This email and any attachments are confidential to the intended recipient
Hello there,
this is Matteo from Italy.
I would like to know if it's possible to use WS-Notification implemented
by CXF to send messages to an external ActiveMQ instance, by using JMS
transport, I guess.
If so, can you please point me to some code examples/fragments?
Many thanks in advance
. Moreover, while I see (through
WireShark) the multicast WS-Discovery
packet being transmitted in Linux, the same does not happen in Windows 7.
Any help is really appreciated, many thanks in advance.
Matteo
INFO: Creating Service
{http://docs.oasis-open.org/ws-dd/ns/discovery/2009/01
Hi Dan,
I checked out trunk at revision 1477500 that includes your latest
updates on this topic, I tested it and everything is fine.
Many many thanks once again for your excellent support, I'm looking
forward for the next release.
Best regards,
Matteo
On 29/04/2013 17:12, Daniel Kulp wrote
great, many thanks again!
Will you add another API to configure the return value of
getSoapVersion() or do you have a better solution in mind?
Best regards,
Matteo
On 26/04/2013 17:11, Daniel Kulp wrote:
On Apr 23, 2013, at 11:05 AM, Pampolini Matteo matteo.pampol...@selex-es.com
wrote:
Hi
, line 36, column 21
Any suggestions?
Best regards,
Matteo
On 08/04/2013 20:36, Daniel Kulp wrote:
I just committed a bunch of updates to the WS-Discovery stuff that adds a
setVersion10() method onto the WSDiscoveryClient that should allow it to flip
to the older WS-Discovery spec (and SOAP
is the release plan for 2.7.5?
Best regards,
Matteo
On 08/04/2013 20:36, Daniel Kulp wrote:
I just committed a bunch of updates to the WS-Discovery stuff that adds a
setVersion10() method onto the WSDiscoveryClient that should allow it to flip
to the older WS-Discovery spec (and SOAP 1.1
thanks in advance for your kind support,
Matteo
--
Write once, compile everywhere
Compile once, run somewhere...
This email and any attachments are confidential to the intended recipient and
may also be privileged. If you are not the intended recipient please delete it
from your system
).
Thank you
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/SOAP-OAuth-in-CXF-2-7-tp5723286p5723330.html
Sent from the cxf-user mailing list archive at Nabble.com.
and
2 above? Or at least a hint where I could start implementing these
approaches?
Thanks
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/SOAP-OAuth-in-CXF-2-7-tp5723286.html
Sent from the cxf-user mailing list archive at Nabble.com.
different from the one provided by the sample
itself, moreover
the async call is not invoked at all (even the comment inside the code says
'not called')
Any suggestions?
Many thanks in advance,
Matteo
--
Write once, compile everywhere
Compile once, run somewhere...
This email and any attachments
Hi Glen,
thanks for your reply and for the link to your interesting article.
Sorry, I forgot to mention that during my tests I had a look at the POM
file of the
sample, and even without -all wsdl2java does not generate the async code.
Regards, Matteo
On 01/02/2013 17:35, Glen Mazza wrote:
Hi
Hello there,
my name is Matteo and I'm writing from Italy.
I'm trying to create a very simple client application, starting from
ws-discovery sample,
to find all ONVIF devices in my network, are you aware of any issues or do you
have
any suggestions?
Many thanks in advance,
Matteo
--
Write
the code is completely consistent.
May you please help me? Frankly speaking I cannot really understand why
there's this kind of
need in CXF framework.
Many thanks in advance,
Matteo
--
Write once, compile everywhere
Compile once, run somewhere...
.
Please note that this code is part of a product that has to be installed
at customer premises, on private
networks with all the constraints you can imagine.
Any suggestions?
Matteo
On 09/01/2013 15:43, Ron Wheeler wrote:
What site is it trying to reach?
You can always make your own Internet
a look at the WSDL file I cited to better
understand my case?
Many thanks, Matteo
On 09/01/2013 15:49, Daniel Kulp wrote:
With CXF, if you set the wsdlLocation to null or an empty string, the
Server/Client will likely work, although it will internally generate a new WSDL
from the java classes
Many many thanks Dan.
While I was trying to understand this stuff, I made some changes to the
WSDL/code and I removed
wsdlLocation in the wrong place, now I started from scratch and
everything is fine!
I really appreciated your kind help.
Best regards,
Matteo
On 09/01/2013 16:55, Daniel
-48cf-8b6e-a31d47b7a17a/RelatesTo/soap:Headersoap:Body
xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd;
wsu:Id=id-3//soap:Envelope
As you can see the Body is empty! How is that possible??? Where the original
body has gone?
Thank you,
matteo
is not
correctly handled, though...
Thank you everybody,
matteo
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/Problem-on-the-way-back-to-the-client-CXF-WS-dispatch-tp571p5720225.html
Sent from the cxf-user mailing list archive at Nabble.com.
Ok, we'll try with 2.5.7. If we experience the same situation I'll let you
know. Anyway, to return a DOMSource instead of the original source is not a
big problem, once you know it :)
Best,
matteo
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/Problem
, Matteo
On 12/12/2012 03:07, Freeman Fang wrote:
Hi,
Just FYI, actually you can also use https to access the wsdl, please take a
look at CXF-3421[1] to get more details.
[1]https://issues.apache.org/jira/browse/CXF-3421
－
Freeman(Yue) Fang
Red Hat, Inc.
FuseSource is now part
:GetPlatUserByUsernameAndPswResponse/soap:Body and
we return this as a SAXSource source, we get the exception that I listed in
my first post.
So the main question here is: what is the correct strategy? remove all but
the body from the SAXSource or return the whole envelope?
Thank you very much!
Best,
matteo
Hi,
we are using 2.5.0. WS Addressing is configured through the
WSAddressingFeature both at client-side and on the dispatcher.
matteo
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/Problem-on-the-way-back-to-the-client-CXF-WS-dispatch-tp571p5720154.html
Sent
Hello there,
my name is Matteo and I'm writing from Italy.
I'm new to Apache CXF, so please excuse me if this first question can
appear silly, I searched the Web
for an answer without success.
I'm testing CXF with ONVIF web services, so I simply invoked wsdl2java
with the main ONVIF WSDL
!
-
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/Problem-on-the-way-back-to-the-client-CXF-WS-dispatch-tp571p5720085.html
Sent from the cxf-user mailing list archive at Nabble.com.
. The only
missing piece is your example!
Thank you again,
Matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Service-Routing-to-Remote-Server-tp5713087p5713131.html
Sent from the cxf-user mailing list archive at Nabble.com.
or share a hint?
Thank you!
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Service-Routing-to-Remote-Server-tp5713087.html
Sent from the cxf-user mailing list archive at Nabble.com.
]
Inviato: mercoledì 8 febbraio 2012 22:25
A: users@cxf.apache.org
Oggetto: Re: serve static content through jetty
Hi
On 08/02/12 17:10, matteo rulli wrote:
Dear all,
I publish some soap-WS through CXF (v. 2.5.0 - bundled into OSGi equinox)
on
the following URI:
http://10.0.2.243:8160
The file is on the classpath. More precisely is in a folder which is specified
in xbootclasspath option with append option. This usually works well with wss4j
configuration files, so I thought it could work also for jetty.
Matteo Rulli
Begin forwarded message:
From: Sergey Beryozkin sberyoz
little
information to solve my problem! I studied Jetty, I understand every
step perfectly, but I can't reproduce that in my code because the
classes don't match at all and so forth.
So: is it maybe out of date? May someone help me with this? Any piece
of suggestion is welcome.
Thanks,
Matteo
can be the key to
solve our problem: it should be just a matter of putting the right ws-policy
elements into the wsdl generated by CXF, shouldn't it?
Thanks again for the hint and for the example: I really appreciated.
Matteo
On Jan 28, 2011, at 9:33 PM, Dennis Sosnoski d...@sosnoski.com wrote
-200401-wss-wssecurity-secext-1
.0.xsd}Security] are not understood.
Maybe CXF needs some external library to handle these headers? What puzzle
me a bit is that the security header is not understood
Should not this be
the job of wss4j???
Thanks,
matteo
Da: Dennis Sosnoski [mailto:d
if this test-bench is publicly
available?
Thank you very much.
Matteo Rulli
pages out of my WS uri (my
service is register as helloWorld)? Are there any cleaner ways?
Thanks
Matteo
On 21 December 2010 01:16, Freeman Fang freeman.f...@gmail.com wrote:
Hi,
You can easily use the option 3 Custom error handle class with cxf
embeded jetty, register your customer error
:-)
Matteo
Ok, I figured this out: the problem was due to a deprecated method of Apache
Cayenne I used in the CleanDb() method. Once I eliminated this deprecated
method the classloader context switch trick worked perfectly.
Thank you again Dan!
matteo
--
View this message in context:
http://cxf.547215
spoils the CleanDb web service functioning also when no
Interceptors are enabled (I get many ClassNotFoundEx probably due to the
class loader modification above).
Do you have any suggestions?
Thank you again,
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Interceptors
client-side and server-side).
I cannot understand if this is a CXF-OSGi interoperability problem or just a
silly error of mine in the procedure that I reported above.
Thank you very much,
matteo
--
View this message in context:
http://cxf.547215.n5.nabble.com/CXF-Interceptors-problem-in-OSGi
69 matches
Mail list logo
