Hi, Luciano.

I did indeed find that feature in WAS Liberty Profile.  It’s called Feature 
Manager and allows you to disable OSGI features as you mentioned.

However, I cannot find the same feature in WAS v8.0’s Admin Console.  I found a 
“OSGi bundle repositories” section within the “Environment” section.  There’s 
another potential section (Servers -> WebSphere application servers -> server1: 
Container Services), but no JAX-RS services are listed among other services 
such as JPA settings, Transaction settings, etc.

I’m not aware of any Feature Manager in WAS v8.0..(I hope there’s one though).

However, I could swear that I’ve read about similar WAS v8.0 OSGi-supplied 
library problems being classified as bugs while browsing the IBM Community 
forums.  I can’t recall a specific account, but I remember stumbling across 
such a post within the last 6 months.  The post wasn’t about JAX-RS, but it 
concerned another Java EE 6 technology such as JSF, CDI, or JPA.

 - Chris

On Dec 15, 2013, at 10:31 PM, Luciano Resende 
<[email protected]<mailto:[email protected]>> wrote:




On Sun, Dec 15, 2013 at 3:29 PM, Harris, Christopher P 
<[email protected]<mailto:[email protected]>> wrote:
I was using Wink v1.4 with the Classloader Policy set to PARENT_LAST, but I was 
getting the stack traces that I posted earlier. There's an issue with OSGI 
loading IBM's modified Wink v1.1 library. That library is still being exposed 
to my project, which causes the method signature conflict surrounding 
CreationUtils.injectFields.

I would like to use v1.4 if possible.


The WAS LP (and most like WAS as well) have an option on the server.xml to 
enable/disable exposed features which will allow you to disable the rest 
functionality that comes with WAS. Could you give that a try ?


--
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

The information transmitted is intended only for the person(s) or entity to 
which it is addressed and may contain confidential and/or legally privileged 
material. Delivery of this message to any person other than the intended 
recipient(s) is not intended in any way to waive privilege or confidentiality. 
Any review, retransmission, dissemination or other use of, or taking of any 
action in reliance upon, this information by entities other than the intended 
recipient is prohibited. If you receive this in error, please contact the 
sender and delete the material from any computer.

For Translation:

http://www.baxter.com/email_disclaimer

Reply via email to