I had this issue; "Classpath entry eclipse.fproj.jdt.libprov.osgi/jpt.jpa is marked for publish/export but is not exported on the project classpath. Classpath visibility within Eclipse and at runtime will differ."
Found the answer here in information is knowledge style. Did the same thing. Ticked it for export in the Properties / Java Build Path / Order and Export and no worries
This is the error message I was getting with Glassfish3 (dropped jboss for now);
org.glassfish.deployment.common.DeploymentException%%%EOL%%%Module type not recognized%%%EOL%%%
Turns out it was an application.xml issue. Glassfish didn't like me putting the client jar in the application.xml as a java module. When I commented it out the EAR loaded without issues. I guess Glassfish wants the client jar tucked under EarContent/APP-INF/lib the problem there is that Eclipse seems to prefer it being as an app client and top level in the ear when debugging.
Apparently the only fix for this is to put the entire server/lib/ directory of jars into the classpath.
[JAM] Error: unexpected exception thrown:
com.bea.util.jam.internal.javadoc.JavadocParsingException: Parsing failure in ...SomethingService.java at line 25.
Most likely, an annotation is declared whose type has not been imported.
This means that you have to have an install of weblogic on your continuous integration server; secondly, it means that ant has to import all the jars in which a wildcard. The second things isn't a big deal. The first is.
Since we are transitioning to maven it also means we will have to start adding jars to nexus one by one. We have the weblogic full client jar, but whatever annotation is missing is not in the jars in that 36 megabyte group of weblogic jars.
Uploading them all one by one and adding them as a dependency looks to be a laborious task.
We were getting this exception in our ant scripts while compiling our webmethods with weblogic's JwscTask. The issue was that a webmethod that was having its java signature generated had a reference to a class that used an enum in a switch statement. This is the stacktrace;
[jwsc] An exception has occurred in the compiler (1.6.0_05). Please file a bug at the Java Developer Connection
(http://java.sun.com/webapps/bugreport) after checking the Bug Parade for duplicates.
Include your program and the following diagnostic in your report. Thank you.
[jwsc] java.lang.IllegalAccessError: tried to access class com.sun.tools.javac.comp.Lower&EnumMapping
from class com.sun.tools.javac.comp.Lower
[jwsc] at com.sun.tools.javac.comp.Lower.mapForEnum(Lower.java:321)
[jwsc] at com.sun.tools.javac.comp.Lower.visitEnumSwitch(Lower.java:3017)
[jwsc] at com.sun.tools.javac.comp.Lower.visitSwitch(Lower.java:3008)
[jwsc] at com.sun.tools.javac.tree.JCTree&JCSwitch.accept(JCTree.java:896)
[jwsc] at com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:44)
[jwsc] at com.sun.tools.javac.comp.Lower.translate(Lower.java:1901)
[jwsc] at com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:56)
[jwsc] at com.sun.tools.javac.tree.TreeTranslator.visitBlock(TreeTranslator.java:146)
[jwsc] at com.sun.tools.javac.comp.Lower.visitBlock(Lower.java:2967)
[jwsc] at com.sun.tools.javac.tree.JCTree&JCBlock.accept(JCTree.java:739)
[jwsc] at com.sun.tools.javac.tree.TreeTranslator.translate(TreeTranslator.java:44)
[jwsc] at com.sun.tools.javac.comp.Lower.translate(Lower.java:1901)
[jwsc] at com.sun.tools.javac.tree.TreeTranslator.visitMethodDef(TreeTranslator.java:130)
[jwsc] at com.sun.tools.javac.comp.Lower.visitMethodDefInternal(Lower.java:2290)
[jwsc] at com.sun.tools.javac.comp.Lower.visitMethodDef(Lower.java:2209)
[jwsc] at com.sun.tools.javac.tree.JCTree&JCMethodDecl.accept(JCTree.java:639)
Annoyingly that error was blocking an automated deployment. The solution was removing the enum based switch statement.
Got a confusing error from maven this morning;
Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one.
This means you are in a directory that does not have a pom in it. Doh.
When running the jwsc task from the weblogic-maven-plugin on windows I was getting this error;
[ERROR] Failed to execute goal Lifelock:weblogic-maven-plugin:2.9.1.1-SNAPSHOT:jwsc (generate.weblogic.webservices) on project ... Exception encountered during jwsc: Failed to copy C:\Users\bamboo\AppData\Local\Temp\BP-MB\_ytegi8\web.xml to C:\Atlassian\bamboo-home\xml-data\build-dir\BP\ES\target\C:\Atlassian\bamboo-home\xml-data\build-dir\BP\ES\target\classes\WEB-INF\WEB-INF\web.xml due to C:\Atlassian\bamboo-home\xml-data\build-dir\BP\ES\target\C:\Atlassian\bamboo-home\xml-data\build-dir\BP\ES\target\classes\WEB-INF\WEB-INF\web.xml (The filename, directory name, or volume label syntax is incorrect) -> [Help 1]
From that error it appeared that the fullpath was being appended twice. For what it is worth, it works on mac/OSX without an issue. The pom for OSX had the outputName configuration elements as ${project.build.outputDirectory}/WEB-INF. I removed that for windows and the maven lifecycle ran to completion. I guess it is a bug in the oracle or be a ant task that the weblogic-maven-plugin wraps. I couldn't find the bug in the plugin itself.
Quite annoying as I had it running on my mac pro before I checked it in. But our bamboo server is on Windows 7. So it failed as soon as the script was put into continuous integration.
Got this error in Weblogic 10.3:
There was a failure when processing annotations for application /apps/*/domains/ domainWS/servers/MS2/tmp /_WL_user/*war. Please make sure that the annotations are valid. The error is 0
The reason is that there was an @EJB in one of the Service files that had the injected local interface commented out. I was mucking with maven jars and builds and obviously didn't comment out an injected bean correctly.
When deploying an ear built by maven with client, ejb, and two war files bundled in the error, "java.lang.NoSuchMethodError: log" kept popping up when it was deployed. Sfl4j 1.6's log() method is incompatible with the 1.5 and 1.4 versions. So obviously there was an old version of sfl4j floating around in the dependencies of dependencies. The problem was a dependency was adding slf4j 1.4 into the APP-INF/lib which was causing the runtime conflict. Using the m2eclipse dependency view I was able to exclude these sfl4j artifacts from the build.
java.lang.NoSuchMethodError: log
at org.apache.commons.logging.impl.SLF4JLocationAwareLog.info(SLF4JLocationAwareLog.java:120)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:187)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1786)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3000)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:471)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:118)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:205)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:164)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Most Popular on South Sea Republic
The articles that have been viewed the most:
Most Popular Restaurants in Phoenix
Phoenix Eats Out is the restaurant review site for
Phoenix,
Scottsdale and
Old Town Scottsdale which lists the modernist and contemporary restaurants, taverns and bars in the greater Phoenix area.
This is the list of the most popular restaurants pages from phoenixeatsout.com that have been viewed the most;
My personal favourite restaurants in Phoenix are
AZ88,
Postinos,
Bomberos with
Grazie,
Humble Pie,
Orange Table,
The Vig,
Fez and others coming close behind. View the complete list with the photo-journalistic style images on
phoenixeatsout.com
Most Popular Hikes in Arizona
Arizona is an outdoor state and has lots of hiking in the city and around the state. Phoenix is unusual for most cities in having several large mountains in the center of the city with great hiking. Anyone who comes to Phoenix has to do the
Echo Canyon trail on Camelback and the
Summit Hike on Squaw Peak or Piesta Peak. The views of the city, suburbs and surrounding mountains are wonderful from Camelback and Piesta Peak.
For more experienced hikers there is the McDowell Mountains in North Scottsdale that has several difficult and strenuous hikes in
Tom's Thumb and
Bell Pass. Alternatively, you can hike the highest mountain in Arizona. At 12,600 feet
Humphrey's Peak is a long and difficult hike.
Alternate Australian Constitutions
Between 2004 and 2009 this site,
southsearepublic.org, was a constitutional blog based on scoop which focused on Australian and global constitutional issues.
One of the strongest aspects of it was the development of constitutions by those involved in the blog. These constitutions are the outcome:
The constitutions were built using principles from Montesquieu's separation of powers, the enlightnment's universal political rights and the ancient Athenian technology of sortition and choice by lot.
Archives For South Sea Republic
South Sea Republic started in 2004 as an Australian constitutional blog in 2004 based on scoop software. It was an immigrative outgrowth of Kuro5hin. The archives for each year since then;
The articles are ordered by views.
Who Is Cam Riley
I am an Australian living in the United States as a permanent resident.
I am a software developer by trade and mostly work in Java and jump between middleware and front end.
I originally worked in the New York area of the United States in telecommunications before moving to Washington DC and
working in a mix of telecommunications, energy and ITS. I started my own software company before heading out to
Arizona and working with Shutterfly. Since then I have joined a startup in the Phoenix area and am thoroughly enjoying myself.
I do a lot of photography which I post on this website, but also on flickr. I have a photo-journalistic website which lists
the modernist and contemporary restaurants in phoenix. I have a site on the
Australian Flying Corps [AFC] which has been around since the 1990s and which I unfortunately
lost the .org URL to during a life event; however, it is under the
www.australianflyingcorps.com URL now.
The AFC website has gone through several iterations since the 90s and the two most recent are
Australian Flying Corps Archives(2004-2002) and
Australian Flying Corps Archives(2002-1999) which are good places to start.
Websites Worth Reading
Websites of friends, colleagues and of interest;
