[GLASSFISH-19430] Allow Jersey context of the RestAdapter to be configurable. Created: 11/Dec/12  Updated: 11/Dec/12  Resolved: 11/Dec/12

Status: Resolved
Project: glassfish
Component/s: rest-interface
Affects Version/s: 4.0_b66
Fix Version/s: 4.0_b67_ms7

Type: Improvement Priority: Major
Reporter: Sanjeeb Sahoo Assignee: Sanjeeb Sahoo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Currently RestAdapter only allows SubjectReferenceFactory to be customizable. Make it more extensible so that a specialized implementation can inject other objects in to the ResourceContext.



 Comments   
Comment by Sanjeeb Sahoo [ 11/Dec/12 ]

Introduced RestAdapter.getAdditionalBinders() in svn #57411.





[GLASSFISH-19415] Response content length is set zero , causing many pages failure in admin console Created: 06/Dec/12  Updated: 11/Dec/12  Resolved: 11/Dec/12

Status: Resolved
Project: glassfish
Component/s: rest-interface
Affects Version/s: 4.0_b66
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Critical
Reporter: Anissa Lam Assignee: Jason Lee
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Many of the console pages has stopped working due to the missing information from the Response.
This error has been there for quite a while, and reproducible in latest build.

Here is what I am seeing. Notice that Content-Length is set to zero.
The command actually goes through fine, domain.xml get updated correctly. However, the response it sent back is missing info.

Also please confirm if the returned 201 status is what it suppose to be. It is setting some attribute, nothing should be 'created'.

~ 2) curl -s -S --user admin: -H 'Accept: application/json' -H 'X-Requested-By: foo' -X POST -vsS -d 'applicationRoot=$

{com.sun.aas.instanceRoot}/applications' -d locale=null -d 'logRoot=${com.sun.aas.instanceRoot}

/ABClog' -d version=anilam-private http://localhost:4848/management/domain

  • About to connect() to localhost port 4848 (#0)
  • Trying ::1... connected
  • Connected to localhost (::1) port 4848 (#0)
  • Server auth using Basic with user 'admin'
    > POST /management/domain HTTP/1.1
    > Authorization: Basic YWRtaW46
    > User-Agent: curl/7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8r zlib/1.2.5
    > Host: localhost:4848
    > Accept: application/json
    > X-Requested-By: foo
    > Content-Length: 134
    > Content-Type: application/x-www-form-urlencoded
    >
    < HTTP/1.1 201 Created
    < Date: Thu, 06 Dec 2012 20:11:10 GMT
    < Content-Length: 0 <============================== BUG
    <
  • Connection #0 to host localhost left intact
  • Closing connection #0


 Comments   
Comment by Anissa Lam [ 11/Dec/12 ]

Jason has checked in a fix and i verified that it is working as before. Console back to normal now.





[GLASSFISH-19403] JSF1091: No mime type could be found for file warning in server.log for every GUI page. Created: 05/Dec/12  Updated: 13/Dec/12  Resolved: 08/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0_b65
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Critical
Reporter: Anissa Lam Assignee: Anissa Lam
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by GLASSFISH-19062 Extra noise present in the log when s... Resolved

 Description   

For every page click, similar warning is logged.

[#|2012-12-04T17:26:37.835-0800|WARNING|44.0|javax.enterprise.resource.webcontainer.jsf.context|_ThreadID=72;_ThreadName=admin-listener(3);_TimeMillis=1354670797835;_LevelValue=900;_MessageID=jsf.externalcontext.no.mime.type.found;|JSF1091: No mime type could be found for file //index.jsp. To resolve this, add a mime-type mapping to the applications web.xml.|#]



 Comments   
Comment by Anissa Lam [ 08/Dec/12 ]

The warning starts after mojarra 2.2.0-m02 integrated.
Added the mime-type in web.xml for 'jsp' file and no more warning.





[GLASSFISH-19062] Extra noise present in the log when starting the admin console: JSF1091: No mime type could be found for file ... Created: 06/Sep/12  Updated: 13/Dec/12  Resolved: 13/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s: 4.0_b52
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Major
Reporter: Ryan Lubke Assignee: Anissa Lam
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates GLASSFISH-19403 JSF1091: No mime type could be found ... Resolved

 Description   

Per the summary. I'm seeing several of these messages being logged when access the admin console. Seems this is unnecessary noise.



 Comments   
Comment by Anissa Lam [ 13/Dec/12 ]

This is now fixed.





[GLASSFISH-18231] JAX-RS and Jersey packages don't have any version Created: 20/Jan/12  Updated: 08/Feb/13  Resolved: 08/Feb/13

Status: Resolved
Project: glassfish
Component/s: jax-rs
Affects Version/s: 3.1, 3.1.1
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Blocker
Reporter: Sanjeeb Sahoo Assignee: Jakub Podlesak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates GLASSFISH-16838 [OSGi] jersey-*** does export package... Resolved
Tags: 3_1_2-exclude

 Description   

While trying to analyse the metadata quality of GlassFish modules, I noticed that javax.ws.rs packages as well the Jersey internal packages exported by various jersey bundles are not associated with any OSGi version. This is a regression and must be fixed otherwise people who are using earlier versions of GlassFish may not be able to upgrade to 3.1.2.



 Comments   
Comment by Jakub Podlesak [ 20/Jan/12 ]

Regarding Jersey packages OSGi versions, i do not think this is a regression
as we were missing the version parameters in manifest from the very beginning
(when we first OSGified Jersey).

However, i agree this could cause serious issues and i am trying to investigate
on how to add OSGi versions correctly without spoiling our poms too much.

Please note, that i have been trying to add the version information to the manifest
several times in the past, but was struggling with
the org.apache.felix.maven-bundle-plugin, as i ended up with incorrect versions
in manifest unless i specified an exact version package by package.
The above solution does not look fine from the maintenance point of view,
but it is probably the only backup solution i have in mind, if any other solution fails.

Comment by Sanjeeb Sahoo [ 20/Jan/12 ]

It's a regression from javax.ws.rs packages point of view. GF3.0 had versions for those packages:
ss141213@Sahoo:/space/ss141213/WS/gf/v3/publish/glassfish3/glassfish$ exports /space3/gf-3.0.1/glassfish/modules/jsr311-api.jar
Export-Package javax.ws.rs;uses:="javax.ws.rs.core";version="1.1.1",

                  • javax.ws.rs.ext;uses:="javax.ws.rs.core,javax.ws.rs";version="1.1.1",
                  • javax.ws.rs.core;uses:="javax.ws.rs.ext,javax.ws.rs";version="1.1.1"
Comment by Jakub Podlesak [ 20/Jan/12 ]

Agreed, the JAX-RS packages used to be distributed separately
in the original jsr311-api.jar, which has the correct version information included.

Sahoo: would it be O.K. to just add the javax.ws.rs.* packages version?

I mean, i understand all other packages should have the version information
included as well, but as i wrote above, that is something much harder to achieve.

Comment by Sanjeeb Sahoo [ 20/Jan/12 ]

For 3.1.2 release, it should be OK as long as we specify the correct version number for javax.ws.rs packages. You can defer fixing the version number for Jersey packages to a later release no later than 4.0.

Comment by Jakub Podlesak [ 23/Jan/12 ]

This should be fully fixed in 4.0 as part of Jersey 2

Comment by Sanjeeb Sahoo [ 07/Feb/12 ]

Jakub and others who made the decision to exclude this bug from 3.1.2 release, please see the related issue for the impact. There are users who are actually impacted by this bug which is quite easy to fix. Too late...

Comment by Jakub Podlesak [ 08/Feb/13 ]

This has been fixed in JAX-RS 2 bundles integrated into GF.





[GLASSFISH-17173] Build Errors on Java SE 7 Created: 09/Aug/11  Updated: 12/Dec/12  Resolved: 12/Dec/12

Status: Resolved
Project: glassfish
Component/s: build_system
Affects Version/s: None
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Critical
Reporter: Byron Nevins Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1_x-exclude

 Description   

Isn't it time to solve this? GF can not be built using Java SE7. I am constantly going back and forth between 6 and 7 because of this.

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'org.glassfish.hk2:hk2-maven-plugin:1.6.12:hk2-compile': Unable to load the mojo 'org.glassfish.hk2:hk2-maven-plugin:1.6.12:hk2-compile' in the plugin 'org.glassfish.hk2:hk2-maven-plugin'. A required class is missing: com/sun/mirror/apt/AnnotationProcessorFactory
com.sun.mirror.apt.AnnotationProcessorFactory



 Comments   
Comment by scatari [ 07/Nov/11 ]

GlassFish 3.1.x will not be built with JDK 7 to support compatibility.

Comment by Joe Di Pol [ 12/Dec/12 ]

This has been fixed in the 4.0 trunk.





[GLASSFISH-16838] [OSGi] jersey-*** does export packages with default version ("0.0.0") Created: 10/Jun/11  Updated: 08/Feb/13  Resolved: 08/Feb/13

Status: Resolved
Project: glassfish
Component/s: jax-rs, OSGi
Affects Version/s: 3.1, 3.1.1
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Major
Reporter: ancoron Assignee: Jakub Podlesak
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
blocks GLASSFISH-16518 Jersey: Allow regular users to run di... Open
Duplicate
is duplicated by GLASSFISH-18231 JAX-RS and Jersey packages don't have... Resolved
Tags: 3_1_1-scrubbed, 3_1_2-exclude

 Description   

Currently, all jersey-*** bundles export their packages (including "javax.ws.rs") without a version, which means exporting with the OSGi default version "0.0.0".

Now I tried to use Apache CXF (the minimal bundle), which requires the following:

javax.ws.rs;resolution:=optional;version="[1.1,2)",
javax.ws.rs.core;resolution:=optional;version="[1.1,2)",
javax.ws.rs.ext;resolution:=optional;version="[1.1,2)",


 Comments   
Comment by ancoron [ 13/Dec/11 ]

This issue is still valid even for 3.1.2 and 4.0 currently.

I could help out if you're short on resources to work on a patch for this.

Comment by ancoron [ 14/Dec/11 ]

Please have a look at the patch provided in JERSEY-752 for inclusion.

Comment by Joe Di Pol [ 07/Feb/12 ]

Too late for 3.1.2

Comment by Jakub Podlesak [ 10/Feb/12 ]

The OSGi headers were fixed for Jersey 1.12. You should be able to get this version installed to GF, once Jersey 1.12
gets released and appropriate GF UC module is published.

Comment by ancoron [ 11/Feb/12 ]

Thanx for fixing this!

Comment by Jakub Podlesak [ 20/Feb/12 ]

Too early
Please see JERSEY-752 for details.

Comment by Jakub Podlesak [ 08/Feb/13 ]

All Jersey exported packages should have a non-default, correct, version specified.





[GLASSFISH-16396] Add below properties under 'Logger Settings' -> General tab. Created: 20/Apr/11  Updated: 11/Dec/12  Resolved: 11/Dec/12

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: 4.0_b67_ms7

Type: Improvement Priority: Major
Reporter: naman_mehta Assignee: Anissa Lam
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified
Environment:

all


Issue Links:
Related
is related to GLASSFISH-19426 OHL and inline help needed for the 2 ... Resolved
Sub-Tasks:
Key
Summary
Type
Status
Assignee
GLASSFISH-19426 OHL and inline help needed for the 2 ... Sub-task Resolved Gail Risdal  

 Description   

Add below properties under 'Logger Settings'-> 'General' tab page.

com.sun.enterprise.server.logging.GFFileHandler.maxHistoryFiles=0
com.sun.enterprise.server.logging.GFFileHandler.rotationOnDateChange=false

Allow user to set above properties from GUI. Back end code has already support for the same.



 Comments   
Comment by Anissa Lam [ 19/Oct/12 ]

target for 4.0

Comment by Anissa Lam [ 11/Dec/12 ]

Added the 2 properties to the logger setting page. Will open a doc bug for the online an inline help.
Request Naman to update the report for those 2 properties usage.

Comment by Anissa Lam [ 11/Dec/12 ]

Transmitting file data ...
Committed revision 57387.
Revision: 57387
Author : anilam
Date : Dec 10, 2012 5:09:37 PM
GLASSFISH-16396. Add the 2 new properties for logging.properties file: rotationOnDateChange and maxHistoryFile. Waiting for information to update inline and online help.





[GLASSFISH-13236] [jersey] Jersey bundles optionally depend mandatory packages Created: 02/Sep/10  Updated: 08/Feb/13  Resolved: 08/Feb/13

Status: Resolved
Project: glassfish
Component/s: jax-rs
Affects Version/s: 3.1
Fix Version/s: 4.0_b67_ms7

Type: Bug Priority: Major
Reporter: Sanjeeb Sahoo Assignee: Jakub Podlesak
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File config.properties.nojaxb    
Issue Links:
Dependency
blocks GLASSFISH-11780 Specify bundle metadata corretcly. Open
blocks JERSEY-660 NPE in com.sun.jersey.core.impl.provi... Resolved
blocks GLASSFISH-16518 Jersey: Allow regular users to run di... Open
Issuezilla Id: 13,236
Tags: 3_1-exclude, 3_1-next, 3_1_1-scrubbed, 3_2prd

 Description   

I see code like this jersey-json bundle:
./1.4-ea05/src/main/java/com/sun/jersey/json/impl/reader/Jackson2StaxReader.java

import com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallingContext;

public int getAttributeCount() {

final UnmarshallingContext uctx =
UnmarshallingContext.getInstance();
...

Yet, this bundle has optionally import com.sun.xml.bind.v2.runtime.unmarshaller
package as shown below:

Import-Package =
com.sun.jersey.api.json,com.sun.jersey.core.provider,com.sun.jersey.core.provider.jaxb,com.sun.jersey.core.util,com.sun.jersey.json.impl,com.sun.jersey.json.impl.provider.entity,com.sun.jersey.json.impl.reader,com.sun.jersey.json.impl.writer,com.sun.jersey.localization,com.sun.jersey.spi,com.sun.xml.bind.annotation;resolution:=optional,com.sun.xml.bind.v2.model.core;resolution:=optional,com.sun.xml.bind.v2.model.runtime;resolution:=optional,com.sun.xml.bind.v2.runtime;resolution:=optional,com.sun.xml.bind.v2.runtime.property;resolution:=optional,com.sun.xml.bind.v2.runtime.unmarshaller;resolution:=optional,javax.ws.rs,javax.ws.rs.core,javax.ws.rs.ext,javax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.annotation.adapters,javax.xml.bind.attachment,javax.xml.namespace,javax.xml.stream,javax.xml.transform,javax.xml.validation,org.codehaus.jackson;version="1.5",org.codehaus.jackson.jaxrs;version="1.5",org.codehaus.jackson.map;version="1.5",org.codehaus.jackson.type;version="1.5",org.codehaus.jettison.badgerfish;version="1.1",org.codehaus.jettison.json;version="1.1",org.codehaus.jettison.mapped;version="1.1",org.w3c.dom,org.xml.sax

How can this class load in the absence of such a package?

This is causing OSGi class loader constraint violation when we add jaxb packages
to system bundle.

Pl. note this is a P2, as other P2 bug depends on this.
Sahoo



 Comments   
Comment by Sanjeeb Sahoo [ 02/Sep/10 ]

Updated dependency

Comment by Sanjeeb Sahoo [ 03/Sep/10 ]

The instructions to reproduce is like this:
You need GlassFish svn rev 40358 at least.
Copy the attached config.properties.nojaxb to glassfish/osgi/felix/conf/
java -jar glassfish.jar

From another terminal:
telnet localhost 6666
ss141213@Sahoo:/space/ss141213/WS/hk2/trunk$ telnet localhost 6666
Felix Remote Shell Console:
============================

-> find jersey-json
START LEVEL 1
ID State Level Name
[ 74] [Installed ] [ 1] jersey-json (1.4.0.ea06)
-> start 74
org.osgi.framework.BundleException: Constraint violation for package
'javax.xml.bind.annotation' when resolving module 74.0 between existing import
0.javax.xml.bind.annotation BLAMED ON [[74.0] package;
(package=javax.xml.bind.annotation)] and uses constraint
226.0.javax.xml.bind.annotation BLAMED ON [[74.0] package;
(package=com.sun.xml.bind.v2.runtime.property), [172.0] package;
(&(package=javax.xml.bind.annotation)(version>=2.2.1))]
->

Comment by Sanjeeb Sahoo [ 03/Sep/10 ]

Created an attachment (id=4796)
Felix config file compatible with GlassFish svn rev 40358

Comment by ludo [ 27/Sep/10 ]

Status? or M6 target?

Need a resolution to advance some internal work with Eclipse embedded server

Comment by Sanjeeb Sahoo [ 27/Sep/10 ]

We need this by 3.1_ms06, else we will be forced to repackage jersey bundles
with our own OSGi metadata in GlassFish.

Comment by Jakub Podlesak [ 07/Oct/10 ]

Sahoo, please go ahead with GlassFish specific OSGi headers as you suggested
in the above post. We won't be able to fix this in the current (GFv3.1) release.

I am also lowering priority of the bug to p4, and setting the 3.1-exclude keyword.

Comment by Jakub Podlesak [ 07/Oct/10 ]

removed 3.1-exclude keyword

Comment by Sanjeeb Sahoo [ 07/Oct/10 ]

No, it is not a p4. I am taking ownership of the bug so that I can repackage
jersey bundles to fix the OSGi metadata. It is hard to understand why Jersey
team took so long to come to the conclusion that they won't correct their
metadata in gf3.1.

Comment by Sanjeeb Sahoo [ 07/Oct/10 ]

taking ownership of the bug

Comment by Jakub Podlesak [ 12/Oct/10 ]

Just to clarify my comment from Thu Oct 7 17:10:09 +0000 2010:
re-packaging Jersey bundles itself within GlassFish workspace is not the way to go
as it would mean great impact on QA/bug-fixing process

Comment by ludo [ 12/Oct/10 ]

So what is the recommended suggestion for a fix in 3.1 product which is the most important release for
our entire group?
Sahoo to commit in Jersey?
Sahoo to provide a patch to Jersey for you to try?
What else?

Comment by Marek Potociar [ 13/Oct/10 ]

Moving to proper? component

Comment by Martin Matula [ 15/Oct/10 ]

Ludo> The way to go is fixing it properly. That we consider being too risky for 3.1, so we want to defer this

  • which will allow us to address other issues we consider being more important. Maybe if we could
    understand what practical benefits this fix brings for our end users and why it is so important for GF 3.1 as
    opposed to fixing other issues in our queue it would help us to prioritize better.
Comment by Chris Kasso [ 27/Oct/10 ]

Changed Target milestone back to not determined. MS6 has sailed.

Comment by Sanjeeb Sahoo [ 14/Dec/10 ]

needs to be fixed by jersey team

Comment by Martin Matula [ 16/Dec/10 ]

Agree with Sahoo. But not for 3.1.

Comment by scatari [ 23/Jun/11 ]

Marking this to be considered for next release. Does not affect the functionality of the release 3.1.1.

Comment by Jakub Podlesak [ 08/Feb/13 ]

This has been fixed be breaking jersey json support down into several modules. Two of them are being bundled with GF:

./bin/asadmin osgi lb jersey
START LEVEL 2
ID|State |Level|Name
164|Resolved | 1|jersey-core-client (2.0.0.m10)
165|Resolved | 1|jersey-core-common (2.0.0.m10)
166|Resolved | 1|jersey-container-grizzly2-http (2.0.0.m10)
167|Installed | 1|jersey-container-servlet-core (2.0.0.m10)
168|Installed | 1|jersey-container-servlet (2.0.0.m10)
169|Resolved | 1|jersey-gf-ejb (2.0.0.m10)
170|Resolved | 1|jersey-media-json-jackson (2.0.0.m10)
171|Resolved | 1|jersey-media-json-jettison (2.0.0.m10)
172|Installed | 1|jersey-media-moxy (2.0.0.m10)
173|Resolved | 1|jersey-media-multipart (2.0.0.m10)
174|Resolved | 1|jersey-media-sse (2.0.0.m10)
175|Resolved | 1|jersey-core-server (2.0.0.m10)

./bin/asadmin osgi start 170 171
Command osgi executed successfully.

./bin/asadmin osgi lb jersey
START LEVEL 2
ID|State |Level|Name
164|Resolved | 1|jersey-core-client (2.0.0.m10)
165|Resolved | 1|jersey-core-common (2.0.0.m10)
166|Resolved | 1|jersey-container-grizzly2-http (2.0.0.m10)
167|Installed | 1|jersey-container-servlet-core (2.0.0.m10)
168|Installed | 1|jersey-container-servlet (2.0.0.m10)
169|Resolved | 1|jersey-gf-ejb (2.0.0.m10)
170|Active | 1|jersey-media-json-jackson (2.0.0.m10)
171|Active | 1|jersey-media-json-jettison (2.0.0.m10)
172|Installed | 1|jersey-media-moxy (2.0.0.m10)
173|Resolved | 1|jersey-media-multipart (2.0.0.m10)
174|Resolved | 1|jersey-media-sse (2.0.0.m10)
175|Resolved | 1|jersey-core-server (2.0.0.m10)





Generated at Mon Mar 02 11:50:12 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.