This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 106582 - Java EE5 JSF Applications unable to run on Weblogic 10
Summary: Java EE5 JSF Applications unable to run on Weblogic 10
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
: 103508 (view as bug list)
Depends on: 108395
Blocks: 103508
  Show dependency tree
 
Reported: 2007-06-14 00:50 UTC by Yousuf Haider
Modified: 2008-01-15 21:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Server Log (82.49 KB, text/plain)
2007-06-14 00:50 UTC, Yousuf Haider
Details
Server Output (5.20 KB, text/plain)
2007-06-14 00:53 UTC, Yousuf Haider
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Haider 2007-06-14 00:50:05 UTC
Build:200706130000
JDK5(update10)

Steps to reproduce:
1. Install Weblogic 10 and create new domain through Configuration wizard.
2. Create new Java EE 5 project with Non-visual or Visual JSF framework.
3. Due to this issue ( http://www.netbeans.org/issues/show_bug.cgi?id=106580 ) add JSF1.2 and JSTl library manually to
project.
4. Deploy application.

Browser shows the following errors:
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable

The server is currently unable to handle the request due to a temporary
overloading or maintenance of the server. The implication is that this is a
temporary condition which will be alleviated after some delay. If known, the
length of the delay may be indicated in a Retry-After header. If no Retry-After
is given, the client SHOULD handle the response as it would for a 500 response.

    Note: The existence of the 503 status code does not imply that a server must
use it when becoming overloaded. Some servers may wish to simply refuse the
connection.



Instead of adding the JSF library I added the following entry in the weblogic.xml according to
http://e-docs.bea.com/wls/docs100/webapp/configurejsfandjtsl.html

<library-ref>
    <library-name>jsf</library-name>
    <specification-version>1.2</specification-version>
    <implementation-version>1.2</implementation-version>
    <exact-match>false</exact-match>
  </library-ref>

This had no effect and I still got the same error on deployment. Server output contained no exceptions. (see attachments)
Comment 1 Yousuf Haider 2007-06-14 00:50:39 UTC
Created attachment 43657 [details]
Server Log
Comment 2 Yousuf Haider 2007-06-14 00:53:28 UTC
Created attachment 43658 [details]
Server Output
Comment 3 Sherold Dev 2007-06-28 14:14:24 UTC
Can you please describe how did you register the user created domain? By default it is created in
bea/user_projects/domains folder and the current plugin does not allow to register it.

Does the same issue occur even if you deploy the project without NetBeans?

At this point I am not able to evaluate this issue because of the issue 108395.
Comment 4 Yousuf Haider 2007-06-28 17:13:03 UTC
To register the domain please go through the following steps:

1. Browse to the 'wlserver_10.0' directory in your weblogic installation directory (something like this
C:\bea10\wlserver_10.0).
2. Goto Next Step and then it will show all the domains that you have created in the drop down list for 'Local
Instances'. The path for each domain will be shown in the Domain Path field. 
3. Enter username and password for selected domain and click  'Finish'. 
Comment 5 Sherold Dev 2007-07-12 13:23:19 UTC
Although, I am getting a bit different error message from the server, the described scenario also doesn't work for me.

Setting the target milestone to 6.0.
Comment 6 Sherold Dev 2007-08-06 16:50:44 UTC
It seems to me that you have defined library dependencies without deploying the libraries, see

http://edocs.bea.com/wls/docs100/webapp/configurejsfandjtsl.html#wp162992

Anyway, even if you followed the steps properly and the problem still existed, the issue should not be filed against
NetBeans but against WebLogic.

Closing the issue as INVALID
Comment 7 _ potingwu 2008-01-15 21:51:25 UTC
*** Issue 103508 has been marked as a duplicate of this issue. ***