JAXM support in wls 7.0?
Does Bea WLS 7.0 (sp 2 or newer) support JAXM?
It looks like the majority of the packages is there (SOAP Message
Handler Chain Operations use them also), but at least an
implementation of HttpSOAPConnectionFactory seems to be missing.
So, what is the status with JAXM, is it going to be bundled in the
WLS, or do we have to use jwsdp packages for that functionality?
When I invoke the following
SOAPConnectionFactory.newInstance();
the exception looks like this:
javax.xml.soap.SOAPException: Unable to create SOAP connection
factory: Provider
com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
at testclient.WsTestDynamicClient.<init>(WsTestDynamicClient.java:45)
at testclient.WsTestDynamicClient.main(WsTestDynamicClient.java:189)
Regards,
Toni N.
Hi Toni,
HttpSOAPConnectionFactory and the related classes you are
using, are now part of a SAAJ [1] and WLS 8.1 [2] supports it.
regards,
-manoj
[1] http://java.sun.com/xml/saaj/
[2] http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=-1
"toni nykanen" <[email protected]> wrote in message
news:3e6deb8d$[email protected]..
>
Does Bea WLS 7.0 (sp 2 or newer) support JAXM?
It looks like the majority of the packages is there (SOAP Message
Handler Chain Operations use them also), but at least an
implementation of HttpSOAPConnectionFactory seems to be missing.
So, what is the status with JAXM, is it going to be bundled in the
WLS, or do we have to use jwsdp packages for that functionality?
When I invoke the following
SOAPConnectionFactory.newInstance();
the exception looks like this:
javax.xml.soap.SOAPException: Unable to create SOAP connection
factory: Provider
com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
at testclient.WsTestDynamicClient.<init>(WsTestDynamicClient.java:45)
at testclient.WsTestDynamicClient.main(WsTestDynamicClient.java:189)
Regards,
Toni N.
Similar Messages
-
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 aboveHave you checked the 'Web Service Migration Guide' mentioned in the error message?
Timo -
Reg: JAXM support on BEA Weblogic 7.0
BACKGROUND: I am developing a Point-to-point SOAP sender/receiver application.
A client sends a SOAP message directly to the ultimate recipient
using a SOAPConnection object. Here client to the intended recipient
rather than to a messaging provider. Therefore, when the application
sends a message, the message goes directly to the intended recipient.
This kind of SOAP message exchange uses the APIs in the javax.xml.soap package.
SOAPConnection (and its related classes) is a pure library implementation
that lets you send SOAP messages directly to a remote party.
CODE:
try
String endpoint="http://localhost:7001/WholesaleVendor/wsv";
URLEndpoint urlEndpoint= new URLEndpoint(endpoint);
SOAPConnectionFactory soapConnFct = SOAPConnectionFactory.newInstance();
SOAPConnection soapConnection = soapConnFct.createConnection();
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage requestSoapMsg = messageFactory.createMessage();
//REST OF THE CODE FOLLOWS
PROBLEM: It works on Sun's JWSDP 1.0. Howerver, on BEA Weblogic 7.0, I get error.
The error is in the following line:
============================
javax.xml.soap.SOAPException: Unable to create SOAP connection factory:
Provider com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
at supermarket.InventoryBuilder.placePOOnWholeSaleVendor(InventoryBuilder.java:74)
============================
QUERY: Is Point-to-point JAXM communication supported on BEA Weblogic 7.0?
If not, what is alternative?
What is the scope of JAXM support on BEA Weblogic 7.0?
Thanking you in anticipation.
Sachin RaverkarWe have not implemented JAXM, nor has JAXM been included in J2EE 1.4.
JAXM has not gotten much traction in the marketplace, and we have
focused instead on JAX-RPC, which is available in 7.0 and 8.1. From
your description, it sounds like JAX-RPC would meet your requirements.
Note that we do support the SAAJ APIs, which were previously part of JAXM.
-Don
Sachin Raverkar wrote:
BACKGROUND: I am developing a Point-to-point SOAP sender/receiver application.
A client sends a SOAP message directly to the ultimate recipient
using a SOAPConnection object. Here client to the intended recipient
rather than to a messaging provider. Therefore, when the application
sends a message, the message goes directly to the intended recipient.
This kind of SOAP message exchange uses the APIs in the javax.xml.soap package.
SOAPConnection (and its related classes) is a pure library implementation
that lets you send SOAP messages directly to a remote party.
CODE:
try
String endpoint="http://localhost:7001/WholesaleVendor/wsv";
URLEndpoint urlEndpoint= new URLEndpoint(endpoint);
SOAPConnectionFactory soapConnFct = SOAPConnectionFactory.newInstance();
SOAPConnection soapConnection = soapConnFct.createConnection();
MessageFactory messageFactory = MessageFactory.newInstance();
SOAPMessage requestSoapMsg = messageFactory.createMessage();
//REST OF THE CODE FOLLOWS
PROBLEM: It works on Sun's JWSDP 1.0. Howerver, on BEA Weblogic 7.0, I get error.
The error is in the following line:
============================
javax.xml.soap.SOAPException: Unable to create SOAP connection factory:
Provider com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
at supermarket.InventoryBuilder.placePOOnWholeSaleVendor(InventoryBuilder.java:74)
============================
QUERY: Is Point-to-point JAXM communication supported on BEA Weblogic 7.0?
If not, what is alternative?
What is the scope of JAXM support on BEA Weblogic 7.0?
Thanking you in anticipation.
Sachin Raverkar -
Will JDK 1.2.2_08 be supported with WLS 5.1?
Hiya,
Will JDK 1.2.2_08 be supported with WLS 5.1?
If not, why?
If so, when?
Much thanks,
Richard Fanta
Systems Architect
Morgan Stanley OnlineOh yeah, like - that wasn't there when he asked the question - THREE MONTHS AGO.
Slow day at Loud Cloud?
Mike
David Peng <[email protected]> wrote:
http://e-docs.bea.com/wls/platforms/index.html#solaris
Mike Reiche wrote:
It seems to work fine here.
Is there some reason you're not running 1.3 ?
As I recall you guys are on Solaris (I was there in December).
Mike Reiche
"Richard Fanta" <[email protected]> wrote:
Hiya,
Will JDK 1.2.2_08 be supported with WLS 5.1?
If not, why?
If so, when?
Much thanks,
Richard Fanta
Systems Architect
Morgan Stanley Online -
Is role base security supported by WLS 5.1?
To what extent is role based security supported by servlets under WLS 5.1?
Declarative role based security does not seem to be supported?
Are any of the following methods supported?
HttpServletRequest.isUserInRole()
HttpServletRequest.getUserPrincipal()
If so, where are the roles declared? Where is the role/principal mapping
done? Does getUserPrinicipal() return the principal using the WLS security
realm?
Thank you.
Marko.
Cool. Bonus mystery feature. I will call support.
Thanks Winston.
Marko.
Winston Koh <[email protected]> wrote in message
news:[email protected]...
> no, i am not referring to ACL. to my knowledge, the servlet security
> features docs do not make it into the WLS 5.1. I understand its a bit hard
> to use the features properly without proper documentation. contact support
> for more info
>
> thanx
>
> Winston
> Marko Milicevic <[email protected]> wrote in message
> news:[email protected]...
> > The only servlet authorization mechanism I can see documented is ACL's.
> Is
> > this what you are referring to Winston? If so, I believe ACL are
> different
> > than declarative role based security. An ACL grants access to a servlet
> for
> > a set of principals (users and/or groups). But a role is not a
> prinicipal.
> > A role name is mapped to a set of principals.
> >
> > If you are referring to roles, can you give a URL to the documentation
> which
> > discusses this?
> >
> > Thanks Winston.
> >
> > Marko.
> > .
> >
> > Winston Koh <[email protected]> wrote in message
> > news:[email protected]...
> > > both declarative and programmtic based security roles are supported by
> WLS
> > > 5.1.
> > >
> > > if you don't specify any specific security realm in the
> > weblogic.properties
> > > file, a default WebLogic Security realm is assumed. you could specify
> the
> > > group and its associated users and passwords there in the properties
> file.
> > > in the web.xml file associated with each web app, you could speciify
the
> > > security constraints for each servlet
> > >
> > > I would imagine when accessing a secured servlet within a web app, a
> > client
> > > would supply her credentials thru some sort of authentication, and
based
> > on
> > > the credentials, we find out the role name from the
weblogic.properties
> > file
> > > which in turn mapped to the web.xml which specify the security role
that
> > > could access the particular servlet. if the role matches, access to
the
> > > servlet is granted
> > >
> > > refer to WL Docs for more specific details
> > >
> > > thanx
> > >
> > > Winston
> > > Marko Milicevic <[email protected]> wrote in message
> > > news:[email protected]...
> > > > To what extent is role based security supported by servlets under
WLS
> > 5.1?
> > > >
> > > > Declarative role based security does not seem to be supported?
> > > >
> > > > Are any of the following methods supported?
> > > >
> > > > HttpServletRequest.isUserInRole()
> > > > HttpServletRequest.getUserPrincipal()
> > > >
> > > > If so, where are the roles declared? Where is the role/principal
> > mapping
> > > > done? Does getUserPrinicipal() return the principal using the WLS
> > > security
> > > > realm?
> > > >
> > > > Thank you.
> > > >
> > > > Marko.
> > > > .
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
-
Weblogic Events - are they supported in WLS 8.1?
Weblogic Events - are they supported in WLS 8.1?
From the documents posted at:
http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html
which states:
The following APIs and features are deprecated in anticipation of future removal
from the product.
WebLogic Events are deprecated and should be replaced by JMS messages with NO_ACKNOWLEDGE
or MULTICAST_NO_ACKNOWLEDGE delivery modes. See Non-transacted session <../jms/fund.html>
in Programming WebLogic JMS for more information.
and
http://e-docs.bea.com/wls/docs81/cluster/overview.html
Which states Weblogic Events cannot be clustered.
Packages:
weblogic.event.actions <../javadocs/weblogic/event/actions/package-summary.html>Package
weblogic.event.common <../javadocs/weblogic/event/common/package-summary.html>Package
weblogic.event.evaluators <../javadocs/weblogic/event/evaluators/package-summary.html>
However - I cannot find these in the package paths of WLS 8.1.
Does anybody know for sure whether or not they are supported?
Is anybody using Weblogic events with WLS 8.1?
Thanks.I believe it's 6.1.
-- Rob
John Slaman wrote:
Thanks Rob.
Does anybody know the actual last version of WLS where the Weblogic Events were
supported?
Rob Woollen <[email protected]> wrote:
No, WebLogic Events are not included in the 8.1 product. The docs
should be cleaned up to reflect that.
-- Rob
John Slaman wrote:
Weblogic Events - are they supported in WLS 8.1?
From the documents posted at:
http://e-docs.bea.com/wls/docs81/upgrade/upgrade51to81.html
which states:
The following APIs and features are deprecated in anticipation offuture removal
from the product.
WebLogic Events are deprecated and should be replaced by JMS messageswith NO_ACKNOWLEDGE
or MULTICAST_NO_ACKNOWLEDGE delivery modes. See Non-transacted session<../jms/fund.html>
in Programming WebLogic JMS for more information.
and
http://e-docs.bea.com/wls/docs81/cluster/overview.html
Which states Weblogic Events cannot be clustered.
Packages:
weblogic.event.actions <../javadocs/weblogic/event/actions/package-summary.html>Package
weblogic.event.common <../javadocs/weblogic/event/common/package-summary.html>Package
weblogic.event.evaluators <../javadocs/weblogic/event/evaluators/package-summary.html>
However - I cannot find these in the package paths of WLS 8.1.
Does anybody know for sure whether or not they are supported?
Is anybody using Weblogic events with WLS 8.1?
Thanks. -
BIweb service proxy JAX-RPC 1.1 method is not supported in WLS 8.1 clients
Hello
I have an application in oracle Application server and I'm migrating to weblogic 11g .
I have used web service proxy for BIPublisher 10.1.3.4 , careated by jdeveloper web service proxy wizard , when I want using it in weblogic , In corresponding form that uses BI Publisher web service proxy , I encounter following error :
"JAX-RPC 1.1 method is not supported in WLS 8.1 clients , if you attempting to run oc4j 10.1.3 JAX-RPC client in WLS,please see Web service Migration Guide for Instructions"
What should I do?
Regards
MehdiSpoke to dev and there was a bug logged, it seems to be down to Weblogic's implementation.
+This is pure WLS issue. The root cause of this problem is that Weblogic's
SAAJ implementation. No codechange on BIP server side
WLS 10 ships with two SAAJ implementations. By default the buggy 9.x
implementation is used (which lives in the package
weblogic.webservice.core.soap), but there is a new implementation, which
supports SAAJ 1.3 (which lives in the package weblogic.xml.saaj). I also
checked in a debugging jsp page, which could help looking at the DEBUG
logging to see which SAAJ implementation is used.
JSP testpage xmlponline/wwwroot/wsclient/soapclient-wls-8270711.jsp
To use this new version, you have to make sure setting the
-Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl
in startWebLogic script. +
Please give the solution a try and let me know if it works.
Regards
tim -
WebDAV support in WLS 7.0
Is WebDAV supported in Weblogic Server 7.0?
Hi Toni,
HttpSOAPConnectionFactory and the related classes you are
using, are now part of a SAAJ [1] and WLS 8.1 [2] supports it.
regards,
-manoj
[1] http://java.sun.com/xml/saaj/
[2] http://commerce.bea.com/showproduct.jsp?family=WLP&major=8.1&minor=-1
"toni nykanen" <[email protected]> wrote in message
news:3e6deb8d$[email protected]..
>
Does Bea WLS 7.0 (sp 2 or newer) support JAXM?
It looks like the majority of the packages is there (SOAP Message
Handler Chain Operations use them also), but at least an
implementation of HttpSOAPConnectionFactory seems to be missing.
So, what is the status with JAXM, is it going to be bundled in the
WLS, or do we have to use jwsdp packages for that functionality?
When I invoke the following
SOAPConnectionFactory.newInstance();
the exception looks like this:
javax.xml.soap.SOAPException: Unable to create SOAP connection
factory: Provider
com.sun.xml.messaging.client.p2p.HttpSOAPConnectionFactory not found
at javax.xml.soap.SOAPConnectionFactory.newInstance(Unknown Source)
at testclient.WsTestDynamicClient.<init>(WsTestDynamicClient.java:45)
at testclient.WsTestDynamicClient.main(WsTestDynamicClient.java:189)
Regards,
Toni N. -
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
>
>
>
-
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,
NaveenHi.
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? -
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,
NeilOur 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. -
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 -
ALT-DD Tag supported by WLS 7.0?
Hi,
When I try to deploy an EAR into WLS 7.0 SP1, I get the following error each time
that WLS reaches an <ALT-DD> tag inside the application.xml file:
"Alternative descriptor bla-bla.xml can not be found"
However, this alternative descriptor file is contained in the EAR file !
Does it mean that WLS 7.0 SP1 does not support this kind of standard tag?
Thanks for your help
VincentThis is a known issue. Contact [email protected] and reference CR089760.
Vincent Ducret wrote:
Hi,
Context:
I'm trying to deploy a simple EAR application on WLS 7.0sp1 that contains a single
JAR file. In the application.xml of this EAR file, I use the <ALT-DD> tag to specify
a specific deployment file for my JAR module, e.g. toto.xml, which is localized
at the root of my EAR file.
Problem:
Every time, I try to deploy this EAR file, I got the following error from WLS:
<1 nov. 02 16:37:03 CET> <Error> <Deployer> <149201> <The Slave Deployer failed
to complete the deployment task with id 1 for the application Test.
weblogic.management.ApplicationException: Prepare failed. Task Id = 6
Module Name: toto.jar, Error: Alternative descriptor toto.x
ml can't be found.
Where's the problem ?
Thanks for your help
Vincent--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support
Maybe you are looking for
-
Unwanted hor-scroll bars in IE
Hello all, I have designed a web page in Dreamweaver MX using frames (3-T,L,C) when I view it in Firefox scroll bars appear on the right side, which is correct, but when I view it in IE scroll bars appear on the right AND the bottom, even thow there
-
i'm not a good one in english i'm flemish so do it letter by letter please . if i want to use the filter liquifi open's a new page wat's normaly yes , but in stade of my picture i get a black screen whats going wrong ?
-
How Do I Import My G4 Files Into G5???
So, I have a G4 with Tiger, and have just upgraded to a G5 with Leopard. Using Target Mode, I have moved over most of my documents and applications with no problem. HOWEVER, I can't figure out how to get my old Address Book, Inbox, and Sent Mail to c
-
I purchased a video clip (no audio) from a web vendor and the file is a .mov format. It plays fine in Windows Media Player. When I try to import it in PE7 with the Add Media function the file selection window will not even show the .mov file. It is n
-
One of the table in Production system contains 450K entries. I want to download the entire table records. Is there a way of doing it other than exporting to a local file. Since there is too many entries I dont think it is a good idea to display all t