Clashes with class of same name: weblogic 6.0 sp2

          Hi Mike,
          Thanks for the response.
          I am getting this error
          C:\bea\testDir\jsp_servlet\_vgn\_portal\_system\_site\_edit.java:7: package jsp_servlet._vgn._portal._system
          clashes with class of same name
          Full compiler error(s): C:\bea\testDir\jsp_servlet\_vgn\_portal\_system\_site\_edit.java:7:
          package jsp_servlet._vgn._portal._system clashes with class of same name package
          jsp_servlet._vgn._portal._system._site; ^ 1 error
          This is the error on the screen and the messages I posted are from the weblogic.log
          Let me know if you need more info. Also, i found some suggestion somewhere that
          I should install rolling patch 2, bu i searched the downloads and did not find
          anything called Rolling Patch 2.
          Varun
          (No more information available, probably caused by another error) Michael Young
          <[email protected]> wrote:
          >Hi.
          >
          >Can you post the complete error? I don't see anything about class name
          >clashes in the exception you posted below.
          >
          >Cheers,
          >Michael
          >
          >Varun Garg wrote:
          >
          >> I am getting a "clashes with class of same name" error with some of
          >my jsp pages
          >> on weblogic 6.0 sp2. I have tried deleting my temporary jsp file, i
          >have tried
          >> using a working directory for the jsp using weblogic.xml.
          >>
          >> This happens for few files and not all of them
          >>
          >> java.io.IOException: Compiler failed executable.exec(java.lang.String[javac,
          >-classpath,
          >> C:\bea\wlserver6.0\config\mydomain\applications\DefaultWebApp_myserver;C:\bea\wlserver6.0\.\config\mydomain\applications\DefaultWebApp_myserver\WEB-INF\lib\ASTab.jar;C:\bea\testDir;C:\bea\jdk130\jre\lib\rt.jar;C:\bea\jdk130\jre\lib\i18n.jar;C:\bea\jdk130\jre\lib\sunrsasign.jar;C:\bea\jdk130\jre\classes;.;C:\bea\wlserver6.0\lib\weblogic_sp.jar;C:\bea\wlserver6.0\lib\weblogic.jar;C:\bea\wlserver6.0\lib\jce1_2_1.jar;C:\bea\wlserver6.0\lib\sunjce_provider.jar;C:\bea\wlserver6.0\lib\US_export_poli
          c
          >y.jar;C:\bea\wlserver6.0\lib\local_policy.jar;C:\bea\wlserver6.0\config\mydomain\applications\DefaultWebApp\WEB-INF\lib;;null,
          >> -d, C:\bea\testDir, C:\bea\testDir\jsp_servlet\_vgn\_portal\_system\_title.java])
          >> at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:585)
          >> at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:354)
          >>
          >> Thanks in advance for the help.
          >>
          >>
          >
          >--
          >Michael Young
          >Developer Relations Engineer
          >BEA Support
          >
          >

Similar Messages

Jsp name clashes with package of same name (WL5.1)

          I have the following directory structure, well not really, but anyway...
          foo.jsp
          foo/bar.jsp
          The compilation of foo.jsp will fail stating that "jsp_servlet/_foo clashes with
          package of same name".
          The problem is that you can't have a jsp and directory of the same name. Actually,
          to be specific, you can't only if that directory contains another jsp, which in
          my case it does.
          What can I do so that weblogic will allow me to have a directory and jsp with
          the same name?
          thanks,
          -Steve


          Well, adding a prefix like dir to get dir_foo only works if you
          don't have a class called dir_foo, right?
          I'm sure you can come up with other mechanims for munging names
          and I'm also sure that I can come up with examples where they
          don't work.
          Mike
          "steve" <[email protected]> wrote:
          >
          >I'd like to say no, but unfortunately that's not really an
          >option. It should be possible to drop in a jsp file
          >under my document root anywhere that I might have an html file.
          >
          >I agree java limits you from having a class and package of the
          >same name. But weblogic constructs the package names, so it can ensure
          >a conflict
          >does not happen.
          >
          >For instance, the "packagePrefix" JSPServlet initialization
          >argument that defaults to "jsp_servlet" avoids package
          >conflicts. Similarly, I'm suggesting a "directoryPrefix"
          >argument that would avoid the conflict that I'm running up
          >against.
          >
          >Given the same boring example:
          >foo.jsp
          >foo/bar.jsp
          >
          >and using a directoryPrefix of "_dir" it would be mapped to
          >
          >jsp_servlet/_foo.class
          >jsp_servlet/_dir_foo/bar.class
          >
          >Any thoughts?
          >
          >"Mike Reiche" <[email protected]> wrote:
          >>
          >>I believe that is a limitation of Java, not Weblogic.
          >>
          >>Just say no.
          >>
          >>Mike
          >>
          >>"Steve" <[email protected]> wrote:
          >>>
          >>>I have the following directory structure, well not really, but anyway...
          >>>foo.jsp
          >>>foo/bar.jsp
          >>>
          >>>The compilation of foo.jsp will fail stating that "jsp_servlet/_foo
          >>clashes
          >>>with
          >>>package of same name".
          >>>
          >>>The problem is that you can't have a jsp and directory of the same
          >name.
          >>>Actually,
          >>>to be specific, you can't only if that directory contains another jsp,
          >>>which in
          >>>my case it does.
          >>>
          >>>What can I do so that weblogic will allow me to have a directory and
          >>>jsp with
          >>>the same name?
          >>>
          >>>thanks,
          >>>-Steve
          >>
          >

I updated to Muse CC (2014.2) recently, but this morning it appeared in my Creative Cloud menu as needing to be updated again. Is that a minor upgrade with the exact same name?

I updated to Muse CC (2014.2) recently, but this morning it appeared in my Creative Cloud menu as needing to be updated again. Is that a minor upgrade with the exact same name?

The update is for few bug fixes and will show 2014.2 in CC as the update includes hotfix : Release notes | Adobe Muse CC
For exact version details you can check about muse from Muse menu options.
Thanks,
Sanjit

Auto Attendant - I have two entries with the exact same name when msDS-PhoenticDisplayName set

Exchange 2010 Sp3 w/latest rollup.
We want the UM attendant to speak first name lastname so I put in the msDS-PhoeneticDisplayName value by using the set-user command. After this was entered, the UM attendant will say "I have two entries with the exact same name" and speaks both
names identically. When I remove the value the problem goes away so I am confident this field is causing the problem. Anyone else have this problem and solved it?

Is it possible to find out what serial or UDID info is stored on iCloud being used by the FindMyIphone site? The FMI website doesn't show anything but the name and the device image (which is a generic iPhone image, and definitely not the 5S )
Unfortunately not.

Script to replace filename.tif with graphic of same name

Have never written nor used an InDesign script.
I'm using InDesign 3.0.1 and need a script which will replace filenames with inline graphics of the same name in a large catalog (each file has about 250 images).
Can anyone please help me?
Thanks

Dave
I placed and linked Jpegs in a document with like named tif's placed in a folder. I ran the script, pointed to the folder and it said that no graphics were replaced. The linked graphics were the original Jpegs.

My network drives crashed and I was able to restore one with the exact same name and login. The second one I also created using the same name and login but it does not find the files when I click.

I get Connection failed when I click on the photo in IPhoto. This window keeps popping up and I have to force quit IPhoto.

iPhoto tracks referenced files using Aliases and this works just fine when the Library and the photos are on the same volume. However, Aliases won't survive being moved from one volume to another. This is why experienced users on here recommend against using Referenced Libraries in general, and in particular when the library and files are on different volumes.
Try repair the aliases with an app like FileBuddy If that fails then I'm afraid you'll need to do it manually for every photo in the Library, unfortunately.
Regards
TD

How can I have two fields with the same name if it makes sense?

Hello, folks :)
I have a pretty hard time figuring out how I can have two text fields with the same binding name.
The whole problem is that when I need two fields with the same binding name they are still differnent coz they have the same name but differnt indices.
I should make a form filled at runtime by merging a pdf form file and an fdf file data file. And I have no choice to do it differently. And my form file needs some data like customerName, companyName twice in one form. But there's only one possible buinding name indexed zero.
How can I create a field with absolutely the same name or is it just impossible due to possible name conflicts? And is there a workaround to this problem? I just need one piece of data repeated in different places.
Thanks for your replies :)
P.S. if u think that the problem is not clear enough let me know. I'll supply you with more details. But the general process can not be changed.
One pdf should be mergred with an fdf with as the result of their merge a new filled and flattened form. I have no control over fdfs their are generated by Oracle and I can not fill the form using XML files coz this process should be integrated in a working application.

I just thought about a really ugly workaround with a server-side script adding values to fdf files but it's a bit of work and tests and personally i think it's a bad idea :-(

Class Loader Hierarchy in Weblogic 7.0

I have read the BEA documentation on the class loader hierarchy in Weblogic Server,
and I have some questions regarding some behavior I am seeing.
I am running Weblogic Server 7.0.
I have an ear file that contains 3 web apps (wars) and several utility jars. The
web apps' manifests contain the Class-Path entry for the utility jars. My understanding
of this is that each web app SHOULD have its own class loader. Also, the utility
jars will be scoped in a separate class loader and WILL NOT have visibility to
the web app classes. The web app classes should have visibility to the utility
jars.
Is this correct????
I added a static segment of code in each web app and printed the class loader
for each servlet when it was loaded. I also printed the class loader from a class
that is DEFINITELY contained in one of the utility jars. Here is the result:
Utility Class ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Utility Class
Parent ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 1 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet 1 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 2 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet 2 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
I'm a little confused.... I expected to see 3 different class loaders (i.e. one
for each class above). I believe the above printout says that all 3 classes are
being loaded by the SAME class loader instance (Launcher$AppClassLoader@b9d04).
Am I interpreting this correctly? If so, what's going on?

I rechecked the classpath for the user that starts Weblogic, and in the classpath
I found the project "src" directory (must have missed it earlier). When we did
our build, the classes are placed in the src structure then copied to the build
area. That's the reason I was not seeing the appropriate class loader hierarchy.
Thanks for all of the comments.
"Sanjeev Chopra" <[email protected]> wrote:
>
"Mark Cotherman" <[email protected]> wrote in message
news:[email protected]...
Thanks for your comments again Mark. I'm just trying to get a goodhandle
on how
this is working.
I'll assume that somehow my web app classes are being loaded into theroot
classloader.
The next question is... why??Just to be sure - is there any way these classes are sneaking into the
system classpath ?
My ear file contains the following:
a.war
b.war
c.war
lib/util1.jar
lib/util2.jar
lib/util3.jar
lib/util4.jar
The manifest in all three wars reference all util jars. This ear deployssuccessfully
on Weblogic with no errors.
How could these separate servlets (one in each war) not have seperateclass loaders
seperate from the root where the utils should reside. I don't thinkthat
I have
any control over where Weblogic loads the war classes, or do I?
See comments below....
Mark Spotswood <[email protected]> wrote:
Mark Cotherman wrote:
Thanks for the follow-up.
I want to make sure I follow what you are saying. All classes in
the
manifest
Class-Path of WARs are exported to the parent classloader.That's right.
To me this is the correct behavior since the manifest Class-Path
is
meant to provide
a way to share common utility classes among several web apps. AllEJB jars and
manifest Class-Path entries should be loaded by the same class loader.Its a way to share class definitions, but not necessarilly class
instances. I don't think that a web application should be extending
the classpath of its parent's classloader. This leads to namespace
problems as well as reloadability issues.
Ok, you lost me here. Shouldn't delegation handle the namespacecollisions??
If the web app class loader has a class definition (webapp:com.xyz.ClassA) with
exactly the same name in the same package as the root class loader(rootloader:
com.xyz.ClassA), I thought the web app would use (delegate loading)the
class
definition from the root class loader when PreferWebInf is set to false.
Isn't this why the PreferWebInf attribute, when set to true, can causeClassCastExceptions??
The web app when creating an instance of (webapp: com.xyz.ClassA)from
the web
app class loader can potentially pass a reference to this instanceto a
class
instance loaded from the root loader. The root class loader has adifferent class
definition for ClassA.
REALLY what makes since is that all common jar files be defined
in
the manifest
Class-Path OF THE ear FILE (if the WAR(s) are in an ear). These
jar
files should
then be loaded by the same class loader as the EJB jars. There shouldbe no need
for the WARs to have any reference to the utility jars since the
EJB
class loader
is the parent of the WAR class loaders.The ear file doesn't have a manifest classpath, but what you are getting
at makes sense. If you add a manifest to any EJBs in your app, theall
webapps (as well as all other EJBs) will be able to see it, sincewith
our structure, EJBs are loaded into the application's root classloader.
My problem is that the ACTUAL SERVLET classes are NOT being loadedby a separate
class loader from the EJB and common jar class loader. This is
completely
against
what is being said in the Weblogic documentation. The Manifest
Class-Path
should
have nothing to do with where the classes that reside in
WEB-INF/classes
of my
servlet are loaded.Classloaders will ask their parent for the class first before loading
it
themselves. So if the parent classloader somehow has visibility to
classes that your webpapp references, then it will get loaded by the
parent classloader.
I am in the middle of migrating an app from an older version of
Weblogic,
and
it would be helpful to have the ACTUAL class loading hierarchy welldocumented.
The basic hierarchy is all EJBs are in a root shared classloader and
each web application is loaded by a classloader that is a child of
that root.
Again, am I missing something here???My suspicion is that somehow these servlets are in the classpath ofthe
root classloader, so when the webapp classloaders delegate to thatone,
it will come up with the class.
mark
Mark Spotswood <[email protected]> wrote:
I believe what you are seeing is a bug in the servlet container.
The classloader organization is what you expect, but each webapp
is exporting the classpath information from its manifest to the
classloader above its classloader (which is common to all
three webapps) rather than to its own classloader. So because
of the delegation that happens with classloading, the common
parent classloader is the one that loads the class.
I believe that this behavior exists as an attempt to avoid
ClassCastExceptions, but I don't think that it is the right
solution to this problem. In our 8.1 release, this behavior
has been changed. That is, web applications no longer export
manifest classpath information to the parent of their classloader.
This change has not been ported back to the 7.x line, but a bug
report has been created (CR099889). You should be able to follow
up with support with this CR number.
mark
Mark Cotherman wrote:
I have read the BEA documentation on the class loader hierarchy
in
Weblogic Server,
and I have some questions regarding some behavior I am seeing.
I am running Weblogic Server 7.0.
I have an ear file that contains 3 web apps (wars) and several
utility
jars. The
web apps' manifests contain the Class-Path entry for the utility
jars.
My understanding
of this is that each web app SHOULD have its own class loader.
Also,
the utility
jars will be scoped in a separate class loader and WILL NOT have
visibility
to
the web app classes. The web app classes should have visibility
to
the utility
jars.
Is this correct????
I added a static segment of code in each web app and printed the
class
loader
for each servlet when it was loaded. I also printed the class loaderfrom a class
that is DEFINITELY contained in one of the utility jars. Here is
the
result:
Utility Class ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04
Utility
Class
Parent ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 1 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet1 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
Servlet 2 ClassLoader: sun.misc.Launcher$AppClassLoader@b9d04 Servlet2 Parent
ClassLoader: sun.misc.Launcher$ExtClassLoader@71732b
I'm a little confused.... I expected to see 3 different class loaders(i.e. one
for each class above). I believe the above printout says that all
3
classes are
being loaded by the SAME class loader instance
(Launcher$AppClassLoader@b9d04).
Am I interpreting this correctly? If so, what's going on?

Saved File w/same name: Rescue old one?

Hello;
I'm an experienced user, can't believe I did this.
Saved a DVDSP file in same folder with FCP file. Used same file name. Wrote DVDSP file, lost FCP file. I know data is still there, but now name in directory points to DVDSP file. Any suggestions on recovering?
Thanks,
Josh

Hi John,
when you save a file with the exact same name it will overwrite the old file. Data are lost and cannot be recovered.

Creating same-name directories, different cases

I'm trying to set up two directories with basically the same name but different cases:
domain.com/DirectoryName
domain.com/directoryname
Just because I know someone will type it in the second way assuming it will work, since the typical user does not know urls can be case-sensitive. The first directory will just redirect to the second.
My problem is that Dreamweaver won't allow me to create the two directories because it considers them to be the same (and is giving me the "folder already exists" error), regardless of the cases. Does anyone know how to work around this?

I don't follow. Physical directories never can have the same name inside the same parent directory on Windows or Mac, so it's nothing related to DW. They can on Unix systems, but that's a whole different matter and in your case an exclusive one of the server configuration. This needs to be done with aliases, symbolic links, resource mapping or URI forwarding on the server, not on how you design your webpage locally. A browser URL is just a virtual directory/ path and not immediately related to the actual physical structure and because of that, it's the server's responsibility to either convert the characters or not.
Mylenium

How to check if two or more controls/indicators have the same name/label in LabView?

LabView does not show any rror if I name two controls with exactly the same name. It can be confusing. I am using LabView 6.1.

Some people like the fact that you can name things the same. Some even want to be able to have two VIs with the same name in memory at the same time. (Scoping rules to follow in future LabVIEWs.) You can write a small program that lists out the names of all the controls and indicators in a VI using the VI server property nodes. Oh, OK I'll give you an example. (See attached)
Daniel L. Press
PrimeTest Corp.
www.primetest.com
Attachments:
PT_List_Control_Names_and_Detect_Match.vi ‏50 KB

Error deploying Struts 1.1 on weblogic 6.1 sp2

Hello,
I am trying to deploy the struts-documentation.war that comes with struts 1.1
on weblogic 6.1 sp2.
I already have xerces.jar , xalan.jar and crimson.jar in WEB-INF/lib. I have also
tired giving the files in the weblogic classpath.
It does not deploy the application and it gives the following error:
####<Jul 13, 2004 2:26:44 PM IST> <Debug> <HTTP> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <101158> <Exception thrown while loading struts-documentation:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1>
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1525)
at
weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
at
weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
at
weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:177)
at
weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3405)
at
weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
at
weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
at
weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
at
weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at
weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy29.addWebDeployment(Unknown Source)
at
weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
at
weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:984)
at
weblogic.management.internal.DynamicMBeanImpl.addDeployment(DynamicMBeanImpl.java:971)
at
weblogic.management.internal.DynamicMBeanImpl.add(DynamicMBeanImpl.java:956)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:648)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy64.addTarget(Unknown Source)
at
weblogic.management.mbeans.custom.ApplicationManager.autoDeploy(ApplicationManager.java:867)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:966)
at
weblogic.management.mbeans.custom.ApplicationManager.addApplication(ApplicationManager.java:886)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:802)
at
weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:733)
at
weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at
weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at
weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at
weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy5.update(Unknown Source)
at
weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
at
weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at
weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at
weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at
weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at
weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Jul 13, 2004 2:26:44 PM IST> <Error> <J2EE> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <160001> <Error deploying application struts-documentation:
Could not load struts-documentation>
####<Jul 13, 2004 2:26:44 PM IST> <Error> <Management> <phinwo-w00206>
<myserver> <ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'>
<system> <> <141042> <Error deploying application
.\config\mydomain\applications\struts-documentation.war:
java.lang.reflect.UndeclaredThrowableException>
Any help in this regard will be highly appreciated.

I'm also running Weblogic 6.1 SP2 and getting a very similar error during startup when trying to deploy JSTL (Apache's version 1.0.6 from here http://jakarta.apache.org/taglibs/) in an exploded application that starts up fine if I remove the JSTL jars from WEB-INF/lib.
The exact stack trace in my case is this:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1525)
at weblogic.utils.jars.ManifestEntry.stream(ManifestEntry.java:166)
at weblogic.utils.jars.Manifest.stream(Manifest.java:78)
at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:398)
at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:234)
at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3407)
at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3376)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:815)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
at weblogic.j2ee.Application.addComponent(Application.java:163)
at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy31.addWebDeployment(Unknown Source)
at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy30.updateDeployments(Unknown Source)
at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy41.start(Unknown Source)
at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
at weblogic.management.Admin.finish(Admin.java:590)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
at weblogic.Server.main(Server.java:35)

Problem in importing two different classes with same name...

I have to import two different classes in my program with the same name....
import org.apache.lucene.document.Document;
import org.w3c.dom.Document;
//    I AM USING THE DOCUMENT FROM W3C PACKAGE HERE....
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
                 DocumentBuilder builder = factory.newDocumentBuilder();
                 InputSource is = new InputSource( new StringReader( tempString ) );
                 d = builder.parse( is );
                 NodeList images = d.getElementsByTagName("img");
                 int length = images.getLength();
                 for(int i = 0;i<length;i++)
                     Node image = images.item(i);
                     String tempAltText = image.getAttributes().getNamedItem("alt").getNodeValue();
                     altText = altText.concat(" ").concat(tempAltText);
                 }and the error i am getting is
[javac] C:\Documents and Settings\sumit-i\WolframWorkspaces\Base\WolframNutch\src\java\com\wolfram\nutch\indexer\InfoCenterFilter.java:20: org.apache.lucene.document.Document is already defined in a single-type import
    [javac] import org.w3c.dom.Document;
    [javac] ^
    [javac] C:\Documents and Settings\sumit-i\WolframWorkspaces\Base\WolframNutch\src\java\com\wolfram\nutch\indexer\InfoCenterFilter.java:132: incompatible types
    [javac] found   : org.w3c.dom.Document
    [javac] required: org.apache.lucene.document.Document
    [javac] d = builder.parse( is );
    [javac] ^
    [javac] C:\Documents and Settings\sumit-i\WolframWorkspaces\Base\WolframNutch\src\java\com\wolfram\nutch\indexer\InfoCenterFilter.java:133: cannot find symbol
    [javac] symbol : method getElementsByTagName(java.lang.String)
    [javac] location: class org.apache.lucene.document.Document
    [javac] NodeList images = d.getElementsByTagName("img");
    [javac] ^
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 3 errorsany idea ..how to resolve it
Edited by: ping.sumit on Jul 16, 2008 3:39 PM
Edited by: ping.sumit on Jul 16, 2008 3:40 PM

now i changed the code to
import org.apache.lucene.document.Document;
import org.w3c.dom.Document;
org.w3c.dom.Document d = null;
try{
     System.out.println("in author");
               URL url = new java.net.URL(urlString);
               java.net.URLConnection conn = url.openConnection();
               BufferedReader in = new BufferedReader(new InputStreamReader(conn.getInputStream()));
               while ((in.readLine()) != null)
                    //tempString = tempString.concat(in.readLine());
                    String temp = in.readLine();
                    tempString = tempString + " " + temp;
               System.out.println("the string in author" + tempString);
                in.close();
                DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
                 DocumentBuilder builder = factory.newDocumentBuilder();
                 InputSource is = new InputSource( new StringReader( tempString ) );
                 d = builder.parse( is );
                 NodeList images = d.getElementsByTagName("img");and their is only one error i am getting ...and that is
[javac] C:\Documents and Settings\sumit-i\WolframWorkspaces\Base\WolframNutch\src\java\com\wolfram\nutch\indexer\InfoCenterFilter.java:20: org.apache.lucene.document.Document is already defined in a single-type import
    [javac] import org.w3c.dom.Document;
    [javac] ^
    [javac] Note: Some input files use unchecked or unsafe operations.
    [javac] Note: Recompile with -Xlint:unchecked for details.
    [javac] 1 error

Does alias exist to differentiate between 2 classes with same name?

I have 2 classes (a domainmodel-class and a webpage-class) with the same name. Of course I get a naming-conflict when I want to reference the domainmodel-class from the webpage-class (because they have the same name).
I was wondering if there's a language construct in java to import my domainmodel-class under a different name / alias in the webpage-class.
Of course I could simply rename my webpage-class, but that has some impact which I'd rather avoid.
Thanks,
Geert-Jan

gbrits wrote:
I have 2 classes (a domainmodel-class and a webpage-class) with the same name. Of course I get a naming-conflict when I want to reference the domainmodel-class from the webpage-class (because they have the same name).
I was wondering if there's a language construct in java to import my domainmodel-class under a different name / alias in the webpage-class.
Of course I could simply rename my webpage-class, but that has some impact which I'd rather avoid.
Thanks,
Geert-JanNo, you can't do that. But one class can be imported, and the other one be used with fully qualified name all of the time.

Distringuishing between 2 classes with same name

Hi,
I have just recently begun programming in Java on a software project with more than one programmer. On of my coworkers had us use the directory structure such that our packages are name with our domain backwards (ie, an example package is gov.lanl.gui). He was under the impression that by structuring things in this manner one would not have to worry about duplicate class names. So to test it he made a class called Point (knowing such a class existed in the Java API). When he tried to compile the code the compiler was confused as to which Point.java he wanted to use.
Is there a way to reconcile this without having to make sure a class doesn't already exist with the same name?
thanks,
Keri

I am confused by the statement:
When he tried to compile the code the compiler
was confused as to which Point.java he wanted to use.Why would there be more than one Point.java on his workstation? Did he extract the src.jar to his local file system? Please post the actual compiler error.
He is correct that the package structure allows for two different classes to have the same name. If you import java.util.* and java.sql.* into a class and then try to reference the Date class you will get a complier error. This is because there is a java.util.Date class and also a java.sql.Date class. This is one of the reasons that you shouldn't usually import an entire package. Another is that it can make complilation really slow. If you have to import both classes you can do so using the entire package structure in front of the class name e.g.
java.util.Date utilDate;
java.sql.Date sqlDate;

Clashes with class of same name: weblogic 6.0 sp2

Similar Messages

Maybe you are looking for