Workshop Support for WLS 9.0

I have been trying to evaluate the potential of WLS 9.0 using Beehive and Pollinate, only to discover that BEA may be developing the Workshop plugin for Eclipse themselves, and that the Pollinate project is dead.
Could somebody from BEA please give the official word on their plans to support Workshop in WLS 9.0.
Thanks,
Neil

Our sales rep told us yesterday that Workshop for WLS9 will be available around the end of the year.
Until then there is no upgrade path for current workshop apps either. That means that apps developed in Workshop 8.1 won't run in WLS9 apparently.

Similar Messages

Apache plugin support for WLS 6.1 is not working for me.

Following are the additional configurations I used in httpd.conf after doing LoadModule
& AddModule
Alias /weblogic "/opt/BEA/wlserver6.1/config/petstore/applications"
<Location /weblogic>
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
WebLogicHost localhost
WebLogicPort 7003
</IfModule>
I get Permission denied & not even 403/forbidden for Petstore example jsps. I
am trying
to proxy it by URL basis not on mime type. I tried doing same thing for one of
my own domains
& server. The results were same. Now, If I try to comment out the Alias line from
my httpd.conf
file, it gives me 404 error. Can anyone help me out in this regard? I doubt my
configurations
in my weblogic's config.xml file.
Thanks,
Naveen

Hi.
I'm not clear on what you are trying to accomplish with the alias pointing to the absolute
path of your WLS applications directory. This is not how the plugin works. As you have it
set up now the plugin looks for URLs with /weblogic in them and proxies those requests to a
running instance of WLS.
For example, the plugin will accept the following URL and forward it to WLS:
http://host:port/weblogic/index.html
WLS will respond IF you have a webapp named weblogic. From your example it looks like you
are trying to proxy to the petstore example. The URL to access the petstore example that
ships with wls is something like: http://localhost:7003/estore/control/main so if you want
to proxy by path you may want to proxy when the path contains /estore instead of /weblogic.
Hope this helps.
Michael
Naveen wrote:
Following are the additional configurations I used in httpd.conf after doing LoadModule
& AddModule
Alias /weblogic "/opt/BEA/wlserver6.1/config/petstore/applications"
<Location /weblogic>
SetHandler weblogic-handler
</Location>
<IfModule mod_weblogic.c>
WebLogicHost localhost
WebLogicPort 7003
</IfModule>
I get Permission denied & not even 403/forbidden for Petstore example jsps. I
am trying
to proxy it by URL basis not on mime type. I tried doing same thing for one of
my own domains
& server. The results were same. Now, If I try to comment out the Alias line from
my httpd.conf
file, it gives me 404 error. Can anyone help me out in this regard? I doubt my
configurations
in my weblogic's config.xml file.
Thanks,
Naveen--
Michael Young
Developer Relations Engineer
BEA Support
[att1.html]

Platform Support for WLS 5.1 SP9 and / or WLS 6.x

When will BEA support WLPS with either WLS 5.1 SP9 or WLS 6.x?

Should have been more specific:
When will BEA support WLPS __3.2__ with either WLS 5.1 SP9 or WLS 6.x? The
docs say it currently only supports WLS 5.1 sp6/sp8, depending on platform.
Are there plans for BEA to support WLPS __3.5__ with WLS 5.1 SP9? The doc
says it currently only supports WLS 6.x
Jesus M. Salvo Jr. wrote:
>
When will BEA support WLPS with either WLS 5.1 SP9 or WLS 6.x?

BEA Guardian Support for WLS 10

I am running Weblogic Server 10 and was wondering if Guardian supports it. I read in one FAQ that Guardian supports WLS 8.1 and up, but cannot get it to work with 10.
I tried to manually deploy the Agent to my local server, but I do not see a supported *.jar file for weblogic10. I attempted to deploy the Agent using the jar for weblogic9, but continue to get an error message stating that "Guardian is unable to verify that the agent has been properly deployed to all running servers..."
Any help is appreciated.

Hi, the latest version of OCCAS (formerly known as WLSS) 4.0 is based on WLS 10.3 and Java 1.6.
Regards
Graham Pearce
Senior Manager, Oracle Support

Oracle 11g Support For WLS 10 and WLS 9.2

Hi,
Does anyone know where I can find out definatively when Weblogic 10 and 9.2 will officially support Oracle 11g ?
Any official BEA sources here.
Cheers
Simon

There is only one real answer here: test it and test it thoroughly. Asking this question here is pointless, you cannot trust anyone here to give you advice you can rely on. Whatever is said, you have to validate the claims anyway.
Or did you think that Oracle employees were going to answer your question? If so, you are sadly mistaken. Oracle charges money for giving technical support.

Workshop support for portal development

I have installed Weblogic platform 10.3, weblogic server and weblogic workshop gets installed. But when I open the workshop and search for portal perspective; it not there.
I have also installed Weblogic Portal 10.3.2, by which portal server, weblogic server and eclipse gets installed.
I need to create portal application and portal web project into workshop. but i am not able to find portal perspective or application.
Any help regarding will be highly appriciated.
Thanks a lot in advance.
-- Prashant

Our sales rep told us yesterday that Workshop for WLS9 will be available around the end of the year.
Until then there is no upgrade path for current workshop apps either. That means that apps developed in Workshop 8.1 won't run in WLS9 apparently.

Tool for WLS 9.1 / Weblogic Realtime development?

I'm looking for a Dev environment to do EJB development for the WLS 9.1 / Realtime server. My understanding is that BEA Workshop is going to be the tool going forward, ultimately replacing the Weblogic Workshop that comes with WebLogic Platform 8.1.
I've downloaded the eval copy, but I don't see there how to create EAR or EJB projects. Is the correct tool to use? I will eventually want to create webapps with that EAR, but I need a tool now to use for WLS 9.1.
Thanks,
Gary

Gary,
If you are interested in the beta of our BEA Workshop for WebLogic ? It
will be the combined M7 and WebLogic code lines on top of Eclipse.
I will contact you directly via email. We'd love your feedback on this.
br
Gary Mui wrote:
Hi Ram,
Yes, that would be true for 8.1, and is in fact what we're using now. But I'm trying to see what I can use for WLS 9.1 which as far as I understand, Weblogic Workshop does not support. Basically I'm looking for a Weblogic Workshop equivalent for WLS 9.1 and was wondering if BEA Workshop was it. So for now, I guess I'm stuck with just a text editor and the supplied ant scripts that come with WLS 9.1?
Thanks for your input, but unfortunately, I'm still a little unsure of what best to use to develop with BEA's latest app server.
Thanks,
Gary

WLS support for SC_NOT_MOFIDIED (304) status code

Hi all,
We are using WLS 7.0 and noticed that it does not support the conditional retrieval
of URL for static content (ie html pages and gif files etc). This is true at least
for web application deployed with either a war file or "exploded" directory structure.
For those of you who not familiar with this status code, it basically enables
browser to send IF-MODIFIED-SINCE header with a http request. The server is supposed
to check if a new version exisits and if not, returns status code 304. This would
speed up things for an application with large number of static images, css or
html files. We are quite surprised that a leading product like WLS would omit
somthing so basic. So we are not sure if there is a place to turn it on or off?
If there is simply no support for this feature, can someone provide some explaination
as to the rationale behind it? We have some idea, but would rather hear it directly
from BEA. Thanks.

No, we have consolidated on the Apache XML/XSL stuff. You are free to use
whatever other parser you would like however. The Sun XML pkg should work
fine.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Boris Tabenkin" <[email protected]> wrote in message
news:[email protected]..
Are you still including the sun XML package, and if so which version?
"Toby Allsopp" <[email protected]> wrote in message
news:[email protected]..
Hi, Craig.
Craig Macha wrote:
Our company typically does NOT use Open Source products. We can't
risk
not having support.
I think you're a little confused about what "Open Source" means. Itdoesn't mean "unsupported." If you want support then you need to pay forit,
just like any software. One of the advantages of open source software is
that you aren't tied to a single vendor for your support - anyone with the
appropriate skills can take the source code and
provide support, as BEA have chosen to do in this case.
Regards,
Toby Allsopp.

Support for Java Server FAce in Workshop

Dear All,
Does anyone have any idea if and when Workshop will include support for the Java
Server Faces (JSF) framework?
Thank you
Abe

While I cannot share any specific product plans from any vendor, I would like to point out that all of the vendors of IDEs in the Java web application space are members of the JSR-127 expert group that is defining JavaServer Faces. Indeed, one of the primary design goals for the APIs is to ensure that development tools have sufficient information available to create high quality user interfaces at design time, so we're doing all we can to enable this kind of thing.
As JavaServer Faces matures, I think you will be very pleased with the quality and quantity of tools support for it.
Craig McClanahan

Does the JRE 1.5 is supported for the WLS 8.1SP3 client

Hi,
Does the JRE 1.5 is supported for the WLS 8.1SP3 client
Regards,
Ahamad

Hi,
Does the JRE 1.5 is supported for the WLS 8.1SP3 client
Regards,
Ahamad

Web Services support for collection like ArrayList

Getting this error message:
"<Info> Did not find property empty in java.util.ArrayList:
java.lang.NullPointerException"
Are collections like ArrayList supported or am I trying to do something that
can't be done? Any suggestions?
Thanks
Danny

Hi Danny,
Betcha thought I forgot 'bout cha, huh?
I didn't ;-)
The short answer to your question is no; WLS 6.1 does not support using any of
the classes in java.util.*. However, it does support Object arrays as an element
of an Object array, which means you can have code in you service implementation
that looks like this:
public Object[] getNestedObjects()
     Object[] objects = new Object[2];
     objects[0] = new Object[]{
          new String("23.76"),
          new Float((float)23.76)
     // Here, WorkOrder is a JavaBean or an object
     // that implements weblogic.soap.xml.XMLizable
     WorkOrder[] workOrders = new WorkOrder[]{
                    new WorkOrder(),
                    new WorkOrder(),
                    new WorkOrder()
     objects[1] = new Object[]{
          new String("My name is"),
          new String("Slim Shady"),
          workOrders
     return objects;
The main issue I see with doing this is again, interoperability ;-)
If the SOAP toolkit consuming the WSDL for the web service with the above method
cannot handle the "xsd:anyType" XML Schema data type, you're in trouble. In general,
SOAP toolkits want to know what type an element is so they can process it correctly.
When you use a Variant data type (in Visual Basic) or java.lang.Object (in Java),
you are basically promoting the use of weak data typing (or late binding). From
what I've read about SOAP (well, actually what Don Box said he had in mind), XML
Schema and namespaces were adopted to combat this very thing- weak or no data
typing. Personally, I agree ;-) I think strong data typing makes processing a
SOAP request much easier and faster, for everyone. Don't get me wrong, I don't
have anything against object casting, but SOAP parameters (and return values)
are not objects. They are XML elements, just like the other parts of the SOAP
message. There is no behavior, just state. This being the case, isn't it safer
to stick with the data types (e.g. arrays, structures, primitives, etc.) defined
in the SOAP spec and "XML Schema Part 2: Datatypes" document? Enough SOAP boxing
(pun intended). If you are interested in the "complexTypes" object graphs (using
developer defined classes that implement weblogic.soap.xml.XMLizable) lab results,
I can send you a zip. The biggest difference between using JavaBeans and objects
that implement weblogic.soap.xml.XMLizable, is that you have much more control
over which Java objects the later gets serialized/deserialized to/from. With classes
that implement weblogic.soap.xml.XMLizable, the SOAP processor passes you the
actual XML stream for the SOAP parameter (which in this case, is your developer
defined class). It (the SOAP processor) also calls your developer defined class
to get an XML representation for it's data types. It works great with Java clients
(using the client.jar, of course), and I'm trying it out with .NET and MS SOAP
clients this weekend. The most interesting revelation was figuring out how wsgen
(well, actually the WSDL processor) generates the information in the <types> element
of the WSDL ;-) I actually even know how to code an XMLizable so that it produces
the exact element and attribute names I want. I also figure out how to get it
to produce an <element ...>, as opposed to a <attribute ...>, and visa versa.
Of course, WLS 7.0 (and WebLogic Workshop) make all of this a moot point, but
it was fun to get the SOAP/WSDL processors in WLS 6.1 to "do my bidding" for a
short while ;-)
Regards,
Mike Wooten
"Danny Ngo" <[email protected]> wrote:
>
Hi Mike,
Thank you for your response. Do you know if WLS 6.1 Web Services support
the
return of nested object array (object that contains other object arrays).
Thanks
-Danny
"Michael Wooten" <[email protected]> wrote:
Hi Danny,
For interoperability (with non-Java SOAP implementations)reasons, the
Java collections
are not supported in WLS 6.1 ;-) You should consider using an arrayin
place of
this.
Regards,
Mike Wooten
Danny Ngo <[email protected]> wrote:
Getting this error message:
"<Info> Did not find property empty in java.util.ArrayList:
java.lang.NullPointerException"
Are collections like ArrayList supported or am I trying to do something
that
can't be done? Any suggestions?
Thanks
Danny

"error: thread-local storage not supported for this target"

I have a program that uses the __thread specifier, to be run on a Solaris 9/UltraSprac.
I am not able to compile it using gcc 3.4.4 or 4.0.4, it emits the msg "error: thread-local storage not supported for this target".
xz@gamera% gcc -v -Wall -D_REENTRANT -c -o func_stack.o func_stack.c
Reading specs from /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/specs
Configured with: ../srcdir/configure --prefix=/opt/gcc/3.4.4 --disable-nls
Thread model: posix
gcc version 3.4.4
/opt/gcc/3.4.4/libexec/gcc/sparc-sun-solaris2.8/3.4.4/cc1 -quiet -v -D_REENTRANT -DMESS func_stack.c -quiet -dumpbase func_stack.c -mcpu=v7 -auxbase-strip func_stack.o -Wall -version -o /var/tmp//cc0poHSN.s
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/../../../../sparc-sun-solaris2.8/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/gcc/3.4.4/include
/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/include
/usr/include
End of search list.
GNU C version 3.4.4 (sparc-sun-solaris2.8)
        compiled by GNU C version 3.4.4.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
func_stack.c:16: error: thread-local storage not supported for this target
func_stack.c:17: error: thread-local storage not supported for this target
func_stack.c:19: error: thread-local storage not supported for this target
xs@gamera% gcc -v -D_REENTRANT -c -o func_stack.o func_stack.c
Using built-in specs.
Target: sparc-sun-solaris2.9
Configured with: /net/clpt-v490-0/export/data/bldmstr/20070711_mars_gcc/src/configure --prefix=/usr/sfw --enable-shared --with-system-zlib --enable-checking=release --disable-libmudflap --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-cpu=v9 --with-ld=/usr/ccs/bin/ld --without-gnu-ld
Thread model: posix
gcc version 4.0.4 (gccfss)
/pkg/gcc/4.0.4/bin/../libexec/gcc/sparc-sun-solaris2.9/4.0.4/cc1 -quiet -v -I. -iprefix /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/ -D__sparcv8 -D_REENTRANT -DMESS func_stack.c -quiet -dumpbase func_stack.c -mcpu=v9 -auxbase-strip func_stack.o -version -m32 -o /tmp/ccjsdswh.s -r /tmp/cc2w4ZRo.ir
ignoring nonexistent directory "/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/../../../../sparc-sun-solaris2.9/include"
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/usr/sfw/lib/gcc/sparc-sun-solaris2.9/4.0.4/include"
ignoring nonexistent directory "/usr/sfw/lib/../sparc-sun-solaris2.9/include"
#include "..." search starts here:
#include <...> search starts here:
/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/include
/usr/sfw/include
/usr/include
End of search list.
GNU C version 4.0.4 (gccfss) (sparc-sun-solaris2.9)
        compiled by GNU C version 4.0.4 (gccfss).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
func_stack.c:16: error: thread-local storage not supported for this target
func_stack.c:17: error: thread-local storage not supported for this target
func_stack.c:19: error: thread-local storage not supported for this targetJust as comparison, the corresponding output of compiling another file which does not have __thread declaration is as follows:
xz@gamera% gcc -v -Wall -D_REENTRANT -c -o common.o common.c
Reading specs from /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/specs
Configured with: ../srcdir/configure --prefix=/opt/gcc/3.4.4 --disable-nls
Thread model: posix
gcc version 3.4.4
/opt/gcc/3.4.4/libexec/gcc/sparc-sun-solaris2.8/3.4.4/cc1 -quiet -v -D_REENTRANT -DMESS common.c -quiet -dumpbase common.c -mcpu=v7 -auxbase-strip common.o -Wall -version -o /var/tmp//cc4VxrLz.s
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/../../../../sparc-sun-solaris2.8/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/gcc/3.4.4/include
/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/include
/usr/include
End of search list.
GNU C version 3.4.4 (sparc-sun-solaris2.8)
        compiled by GNU C version 3.4.4.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
/usr/ccs/bin/as -V -Qy -s -xarch=v8 -o common.o /var/tmp//cc4VxrLz.s
/usr/ccs/bin/as: Sun WorkShop 6 update 2 Compiler Common 6.2 Solaris_9_CBE 2001/04/02Note that the last 2 lines seem to suggest that a Sun assembler is used as the back-end of gcc. I am not sure whether the failure to compile the first file (with __thread) was due to the incompatibility of this Sun assembler. In the first case, the error msg was emitted before these 2 lines are printed.
I further read a post about gcc 3.3.3's inability to compile code that has __thread in it, on a HP-UX 11.11: http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1216595175060+28353475&threadId=1148976 The conclusion seems to suggest that "the 2.17 GNU assembler did not support thread local storage" and gcc sees that and thus disallows TLS.
If the assembler is the culprit, then does anyone know whether this "Sun WorkShop 6 update 2" assembler in my installation can work with TLS? And how come a Sun assembler becomes the back-end of gcc? I read that gas (the GNU assembler) is the default backend of gcc. (How) can one specify the assembler to be used for gcc?
As an aside, I am able to compile my file on this same Solaris 9/UltraSparc platform using the Sun Studio 12 C Compiler:
xz@gamera% cc -V -# -D_REENTRANT -c -o func_stack.o func_stack.c
cc: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12
### Note: NLSPATH = /pkg/SUNWspro/12/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/pkg/SUNWspro/12/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
###     command line files and options (expanded):
### -c -D_REENTRANT -V func_stack.c -o func_stack.o
/pkg/SUNWspro/12/prod/bin/acomp -xldscope=global -i func_stack.c -y-fbe -y/pkg/SUNWspro/12/prod/bin/fbe -y-xarch=generic -y-xmemalign=8i -y-o -yfunc_stack.o -y-verbose -y-xthreadvar=no%dynamic -y-comdat -xdbggen=no%stabs+dwarf2+usedonly -V -D_REENTRANT -m32 -fparam_ir -Qy -D__SunOS_5_9 -D__SUNPRO_C=0x590 -D__SVR4 -D__sun -D__SunOS -D__unix -D__sparc -D__BUILTIN_VA_ARG_INCR -D__C99FEATURES__ -Xa -D__PRAGMA_REDEFINE_EXTNAME -Dunix -Dsun -Dsparc -D__RESTRICT -xc99=%all,no%lib -D__FLT_EVAL_METHOD__=0 -I/pkg/SUNWspro/12/prod/include/cc "-g/pkg/SUNWspro/12/prod/bin/cc -V -D_REENTRANT -c -o func_stack.o " -fsimple=0 -D__SUN_PREFETCH -destination_ir=yabe
acomp: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12Interestingly, the output no longer mentions the "/usr/ccs/bin/as: Sun WorkShop 6 update 2" assembler.

Just as another comparison, I compiled a file without __thread on the Solaris 9/UltraSparc platform using gcc 4.0.4. Not surprisingly it worked. But I no longer see the mention of the Sun assembler as in the case of gcc 3.4.4. Nor did I see the mention of "GNU assembler" as in the case of gcc 4.0.4/Solaris 10/x86. Instead, I saw something called "iropt" and "cg". Does anyone know what they are?
xz@gamera% gcc -v -Wall -D_REENTRANT -c -o common.o common.c
Using built-in specs.
Target: sparc-sun-solaris2.9
Configured with: /net/clpt-v490-0/export/data/bldmstr/20070711_mars_gcc/src/configure --prefix=/usr/sfw --enable-shared --with-system-zlib --enable-checking=release --disable-libmudflap --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-cpu=v9 --with-ld=/usr/ccs/bin/ld --without-gnu-ld
Thread model: posix
gcc version 4.0.4 (gccfss)
/pkg/gcc/4.0.4/bin/../libexec/gcc/sparc-sun-solaris2.9/4.0.4/cc1 -quiet -v -iprefix /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/ -D__sparcv8 -D_REENTRANT -DMESS common.c -quiet -dumpbase common.c -mcpu=v9 -auxbase-strip common.o -Wall -version -m32 -o /tmp/ccSGJIDD.s -r /tmp/ccKuJz76.ir
ignoring nonexistent directory "/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/../../../../sparc-sun-solaris2.9/include"
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/usr/sfw/lib/gcc/sparc-sun-solaris2.9/4.0.4/include"
ignoring nonexistent directory "/usr/sfw/lib/../sparc-sun-solaris2.9/include"
#include "..." search starts here:
#include <...> search starts here:
/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/include
/usr/sfw/include
/usr/include
End of search list.
GNU C version 4.0.4 (gccfss) (sparc-sun-solaris2.9)
        compiled by GNU C version 4.0.4 (gccfss).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
/pkg/gcc/4.0.4/SUNW0scgfss/4.0.4/prod/bin/iropt -F -xarch=v8plus -xchip=generic -O1 -xvector=no -xbuiltin=%none -xcache=generic -Qy -h_gcc -o /tmp/ccUl4mVM.ircg /tmp/ccKuJz76.ir -N/dev/null -is /tmp/ccSGJIDD.s
/pkg/gcc/4.0.4/SUNW0scgfss/4.0.4/prod/bin/cg -Qy -xarch=v8plus -xchip=generic -OO0 -T3 -Qiselect-C0 -Qrm:newregman:coalescing=0 -xcode=abs32 -xcache=generic -xmemalign=8i -il /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4//gccbuiltins.il -xvector=no -xthreadvar=no%dynamic -xbuiltin=%none -Qassembler-ounrefsym=0 -Qiselect-T0 -Qassembler-I -Qassembler-U -comdat -h_gcc -is /tmp/ccSGJIDD.s -ir /tmp/ccUl4mVM.ircg -oo common.o

Java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

We have some web services that run under OC4J 10.1.3.4. We have various JEE 'client' apps (JSF, servlets etc.) that use these web services. These JEE apps also run under OC4J.
We started a migration project from oc4j to weblogic 10.3.2. In phase 1 we want to move these JEE 'client' apps to weblogic. In phase 2 we want to move the web services themselves to weblogic with adjustments to the JEE 'client' apps as needed.
However we ran into an issue during this phase 1. Deploying these JEE 'client' apps to weblogic results in an error like this:
java.lang.Error: JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions.
We are including Oracle web services client libraries (http://download.oracle.com/otn/java/oc4j/1013/wsclient_extended.zip) in these JEE 'client' apps's war files because weblogic does not have them.
What part of Web Service Migration Guide is the above error message talking about? Do we have to re-generate the client side proxies for all these web services using weblogic's clientgen task in 'JAXRPC' mode? Many of these web services are doc/literal jax-rpc web services. Or does the migration guide recommend we migrate the web services first to weblogic? Any other specific information on working around this error message would be greatly appreciated.

Hi,
I had the same issue but I just managed to fix it. You must upgrade and/or regenerate you proxy. This creates new classes (possibily in a new package) that you must use in your code. I had this error because the classes directory was not clean after the rebuild and the old classes (in the old package) were still present, so the compilation was successful with the old classes. So clean your classes directories, regenerate your proxy and use the new classes in your code.
Regards,
Sylvain

Jdeveloper 11g - JAX-RPC 1.1 method is not supported in WLS 8.1 clients.

Hi,
I am using Jdeveloper 11g and migrating a web Service Proxy created using jdeveloper 10g.
I imported all the proxy classes and when I try to run web service client In Jdeveloper 11g I get the following error
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients. If you are attempting to run an OC4J 10.1.3 JAX-RPC client in WLS, please see the Web Service Migration Guide for instructions."
Please advise on how to solve this?
which is the offending jar/library file in Jdeveloper 11g which is causing the above error?.
Is the above problem there in the WebLogic Server Runtime also?
Please let me know.
2) I cannot generate web server proxies also with jdev11g because the wsdl has overloaded methods omitting the name property within the input and output message, ie, they have a null name. therefore Jdeveloper 11g is using the library which
when called with an overloaded operation that contains null input/output message names, a duplicate error occurs because it sees other operations with the same name. so it is effectively not allowing to create the web service proxies.
Thanks,
Appreciate your quick response to the above

Have you checked the 'Web Service Migration Guide' mentioned in the error message?
Timo

Full servlet 2.3 support in WLS 6.1 available?

          Hi,
          I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The same code
          generates compile errors when compiling against WLS 6.1 sp4 jar.
          Here is the list of inconsistencies as documented in 6.1 notes - go to http://edocs.bea.com/wls/docs61/notes/new.html
          and search for "Servlet API Classes" you should see table with the following classes
          that are not fully 2.3 compatible.
          javax.servlet.Filter
          javax.servlet.ServletContext
          javax.servlet.ServletContextAttributesListener
          javax.servlet.http.HttpServletResponse
          javax.servlet.http.HttpSession
          javax.servlet.http.HttpSessionAttributesListener
          For some classes I a rename works fine, however other are more problematic.
          Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification? Or,
          what else would you suggest?
          Thanks,
          Radu


          WLS6.1 supports Public Final Draft 1 of Servlet 2.3 specification, not the Servlet
          specification 2.3.
          Refer to
          http://support.bea.com/application?namespace=askbea&origin=ask_bea_answer.jsp&event=link.view_answer_page_clfydoc&answerpage=solution&page=wls%2FS-10618.htm
          thanks,
          Deepak
          "Radu" <[email protected]> wrote:
          >
          >Hi,
          >
          >I have succeffully ported a servlet 2.3 based web app to WLS 7.0. The
          >same code
          >generates compile errors when compiling against WLS 6.1 sp4 jar.
          >
          >Here is the list of inconsistencies as documented in 6.1 notes - go to
          >http://edocs.bea.com/wls/docs61/notes/new.html
          >and search for "Servlet API Classes" you should see table with the following
          >classes
          >that are not fully 2.3 compatible.
          >
          >javax.servlet.Filter
          >javax.servlet.ServletContext
          >javax.servlet.ServletContextAttributesListener
          >javax.servlet.http.HttpServletResponse
          >javax.servlet.http.HttpSession
          >javax.servlet.http.HttpSessionAttributesListener
          >
          >For some classes I a rename works fine, however other are more problematic.
          >
          >Is there a patch for WLS 6.1 that fully supports servlet 2.3 specification?
          > Or,
          >what else would you suggest?
          >
          >Thanks,
          >Radu
          >
          >
          >

Workshop Support for WLS 9.0

Similar Messages

Maybe you are looking for