[GLASSFISH-5297] Need to check all the samples for JSR 109 compliant Created: 11/Jul/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: sample_apps
Affects Version/s: V3
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: judytangs Assignee: jagadesh
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 5,297
Status Whiteboard:



After seeing this email thread in quality alias, I feel there is a need to check
for our samples to see if they are JSR 109 compliant or not. If not, should we
fix them or doc them ?

Log this issue to address this so customer will not hit the same issue again.

Aditya Dada wrote:
> Thanks Anissa for the information.
> The customer is using jax-ws sample app.
> Any idea if that application is JSR 109 compliant?
> Anissa Lam wrote:
>> Siraj can confirm since he owns web service managment, but i also believe it
needs to be JSR 109 compliance. Admin console displays the web services based
on WebServiceEndpoint mbean. To confirm whether the app. is detected as web
services, the customer can use jconsole to see if there is WebServiceEndpoint
mbeans created.
>> Another way is by using CLI list-component command.
>> eg.
>> %asadmin> list-components
>> hello <web-module>
>> AddNumbersService <web-module>
>> AddNumbersService#AddNumbers <webservice>
>> Command list-components executed successfully.
>> You will see that AddNumberService.war is detected as webservice, and the
web service endpoint is 'AddNumbers'. You should be able to see that in the
admin console as well. thanks
>> Anissa.
>> Jerome Dochez wrote:
>>> my guess is that they are not using JSR109 style of web services and the
console cannot detect the Servlet style of web services. Anissa, can you confirm ?
>>> jerome
>>> On Jul 9, 2008, at 8:33 AM, Aditya Dada wrote:
>>>> Hi,
>>>> I was just speaking with a customer who's trying out GlassFish for
deployment. They ran into an issue with webservice deployment not showing up in
the admin console.
>>>> They're following steps listed in the guide:
>>>> http://developers.sun.com/appserver/reference/techart/ws_mgmt.html#2
>>>> and after deploying the sample app, they couldn't see the webservices app
under the webservices section, even though the webservice which was deployed as
a war and as an ear works fine.
>>>> The customer is using jdk 1.6, community GF v2ur2 b04 build on Windows xp.
>>>> Does anyone know what may be going on?
>>>> Thanks,
>>>> Aditya

Comment by kumara [ 19/Aug/08 ]

Add gfv3-prelude-include to status whiteboard

Comment by kumara [ 03/Sep/08 ]

v3 defect tracking

Comment by msreddy [ 04/Sep/08 ]

We have two sample apps on web services. One is hello-jaxws which is JSR109
compliant and the other is ssl-jaxws-ear.

Jagadish will update the bug reg. JSR109 compliance of ssl-jaxws-ear.

Comment by msreddy [ 09/Sep/08 ]

Request Jagadish to update the bug with his findings.

Comment by kumara [ 19/Sep/08 ]

Not a product issue.

Comment by kumara [ 24/Oct/08 ]

Reclassifying as P4 because these issues are not must fix for prelude release.
This issue will be scrubbed after prelude release and will be given the right
priority for v3 final release.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Tue Oct 13 17:49:28 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.