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
Vincent

This 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

Similar Messages

Adding alt text tags in InDesign (and Acrobat Pro)

I am having real difficulty adding alternative text tags. I created an INDD doc with rollover buttons linked to URLs firstly in InDesign CS4. I couldn't add alt text tags in CS4 so I then tried to add them in Acrobat X Pro but failed. Acrobat keeps wanting to class the PDF as a form. I then installed InDesign CS6 from the cloud and added alt text to the rollover buttons via object export options. However, these do not show when I export to PDF.
Can someone help me add alt text to my rollover buttons in my interactive PDF either in InDesign CS6 or in Acrobat Pro after I export it?

In InDesign CS6, you just need to add descriptions to buttons. This is done in the buttons and forms panel:
This is the alt text in Acrobat when you roll over the button:
Hope that helps!

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

Html5 del tag support

Hi,
I am very disappointed by the way that Mozilla Firefox support <del> tag.
Please, try to display the code below with Firefox then Safari : you will get why I mention that Firefox has a wrong <del> tag support :
<pre><nowiki><!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<style>
h1 {
font: 3.4em/4 "Helvetica Neue";
font-weight: 100;
font-style: italic;
</style>
</head>
<body>
<h1>My <del>ex</del>Title</h1>
</body>
</html></nowiki></pre>

I can only compare Firefox and Chrome. Seems that both place the line through the center of a lower case x (half of the x-height) when the font size is a bit larger but where they vary, Chrome aims higher and Firefox aims lower.
Test page: http://jsfiddle.net/3futZ/
Not sure there is any applicable standard for exactly where a line-through is drawn.
''Note: You can change the font-family in the Fiddle and save as a new version if you like.''

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 Online

Oh 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.
          > > > > .
          > > > >
          > > > >
          > > > >
          > > >
          > > >
          > >
          > >
          >
          >

Feature request - More ID3 tag support (Key, label etc)

As the subject suggest, please include more ID3 tag support, I'd love to manage my library in iTunes alone, but now I rely on other applications to enter various bits such as:
- Key
- Label
- Catalogue nr.
and I'm sure there are a few others you can think of; but these 3 would be on my short-list.

You are not addressing Apple here.
You may leave feedback for Apple at:
http://www.apple.com/feedback

Does mm:treecontrol tag support focus event in Dreamweaver CS4

Hi
The mm:treecontrol tag support onfocus and onblur events well in Dreamweaver CS3. But it doesn't work in Dreamweaver CS4.
Does CS4 support it?
Thanks
Simon

Hi PZ,
Thank you for your useful solution.
I want to respond some keyboard events(Delete, Enter) for the tree in my floater panel. But some keys have been used by Dreamweaver.
If I write my shortcuts into Menus.xml, it will override Dreamweaver's responses.
Do you have any suggestions for this conflict?
Best Regards
Simon

ADF Faces: is mixing JSF RI and ADF Faces tags supported?

Hi,
I'm looking at ADF Faces as a future possibility for our application that is currently based on JSF RI.
When looking at the ADF Faces demo it strikes me that all pages are almost completely built up from ADF Faces tags.
For instance
af:form
af:commandButton
af:inputText
are used instead of the equivalent core jsf tags f:form, f:commandButton and f:inputText
I'm wondering if this is mandatory if we would like to use some ADF Faces components mixed within our existing application.
In other words: are ADF Faces tags supported in the environment of conventional JSF tags? And mixing ADF Faces JSF components with JSF components by other vendors?
Another thing that strikes me is that pages are constructed using ADF Faces tags for any and all markup content.
I guess this is meant to support several different clients (normal browser applications, mobile clients, voice activation over telephone) using different renderers.
In my experience abstracting markup this way inherently means loss of control over the exact markup that is sent to the client. This is not acceptable for all projects and customers.
Is embedding ADF Faces tags within template HTML, within f:verbatim tags or not, supported?
Regards,
Joost de Vries

You absolutely can mix JSF RI and ADF Faces tags. This is very much supported! You can swap in <h:form> and <h:commandButton> and <h:inputText>. Our versions support some features that the JSF tags do not, as described in our release notes.
Your point about using tags to produce all markup is a very cogent one. For some projects, absolute control over HTML will be a necessary requirement, so we do support that style of development. But we believe strongly that the future does not lie in constant handcoding of HTML, but instead in building more powerful, flexible, and reusable components and assembling those into pages. This was one of the themes of a talk I gave with two coworkers at this past JavaOne.
-- Adam Winer (JSF EG member and ADF Faces lead)

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.

When will iTunes not have ******** tag support?

I just hit this problem today of iTunes/ipod not liking tag headers on certain MP3s and just choking on them and not playing. After digging around some I found out that iTunes uses some outdated tag support whcih causes problems. When will apple fix this? I mean my winamp/WMP can play the files just fine, but in itunes, it doesn't even register in the playlist/library and if its alerady there, it just doesn't play. Can we fix this sometime apple?

Whenever the owner of the distribution rights of those films reach an agreement with Apple that allows them to sell them.
Typing in all caps indicates shouting, is considered rude, and is difficult to read. Many simply do not read such posts.

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
Mehdi

Spoke 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

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,
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]

ALT-DD Tag supported by WLS 7.0?

Similar Messages

Maybe you are looking for