Ear deploy problems if dir contains '.' in the name

Is there a fix that will allow Weblogic 8.1 SP for RedHat to deploy an ear that contains directory structure containing '.' in the name?
We currently have to extract the ear and modify the application.xml to deploy the app in question due to this limitation.

"Don Maxwell" <[email protected]> wrote in message news:27286804.1095364176807.JavaMail.root@jserv5...
Is there a fix that will allow Weblogic 8.1 SP for RedHat to deploy an ear that contains directory structure containing '.' in thename?
>
We currently have to extract the ear and modify the application.xml to deploy the app in question due to this limitation.What is the problem? Can you show a stacktrace?
óÌÁ×Á

Similar Messages

War an ear deployment problem

hi,
I got a war and ear that share common classes. I would like to deploy both of them on the same application server.
I started with weblogic and it worked fine.
Now I am running it on Websphere - the problem is the ear application failed to start - it cant find one of it's property files even though it is in the class path.
I see that the jar containing all the properties is in the class path - the application can access all other properties files except this one.
The problematic properties file is my.commons.logging.properties which is a refactoring to the common.logging jar.
I also see that if the war is not deployed - the ear is deployed without a problem.
the war contains commons.logging.properties and because Websphere also had it's own common.logging i had to use "parent last" for the war deployment.
If i change the load order of the applications(the ear is loaded first) - the properties file is found.
I will be happy to hear any idea you got about this.
I don�t understand how two different applications affect each other that way.
Thanks!!!

Sounds like a bug. You can report it to [email protected]
-- Rob

WSDL Web Services Client and EAR deploy problem

Hi!
I have allready posted this on "Web AS General", with no result.
So I hope this forum is a better choise.
Environment:
SAP EP / SAP NW04 / SPS14
NW DevStudio
I just deployed an ear file (first time ...) with SDM.
The ear file represents an auto generated web services client on basis of a WSDL file.
(done from web services perspective in NWDS choosing "New Deployable Proxy Project")
When running a test I get the following error:
"Could not find portal application Unknown provider of external application: J2EE::sap.com/NWTPINWSClient"
.. where NWTPINWSClient is the name of the EAR - file
The test code contains this:
The portalapp.xml has the following tag:
<application-config>
<property name="SharingReference" value="J2EE::sap.com/NWTPINWSClient">
</property>
</application-config>
I'm new to this, so please feel free to consider newbie misstakes.
BRGRDS
Peter M

Can you/anybody post solution. I have the same problem.
Thanks
Srinivas

EAR Deployment Problem with weblogic 10.2. Need help.

Hi,
I have a EAR file exported from MyEclipse IDE. When i am deploying the EAR file in weblogic 10.2, i am not seeing classess and properties were not exploded under WEB-INF/classes in the web project. I can see the classes folder but it's empty.
When i opened i can see EJB project JAR file and web project .war file in the EAR file. I checked the .war file content and i can see all the classes and properties available in the .war file.
Please help me to find, why the classes and properties are not being exploded when i am deploying as package.
Note: When i am deploying from myeclipse as exploded deployment i was able to run the application but i am failing when i deploy as a package (.ear file).
Thank you,
Vijay M

I found the answer to this. The documentation is not clear enough, LD_LIBRARY_PATH MUST be set and MUST have a pointer to the directory where the SSL .so modules are. I wrote up a blog article explaining the configuration and detailed this issue.
http://blogs.oracle.com/irm/2010/06/quick_guide_to_oracle_irm_11g_1.html

[SOLVED]cURL got problem uploading file with "[]" in the name

$ curl -# -iv -u username:passwd -T '[gg].png' 'ftp://ftp.liondrive.com:2221'
curl: (3) [globbing] error: bad range specification after pos 2
When I rename [gg].png to gg.png, it's all just fine.
Anybody encountered same thing?
What's the problem?
Last edited by lolilolicon (2009-06-24 07:18:05)

OK, I got it
The problem is caused by curl attempting to do globbing on urls that contain []{}. The best fix would probably be for hpodder to invoke curl with --globoff.
....Ha, should have googled the error message before posting. Sorry.
Edit
another woraround is use escape...
curl -# -iv -u username:passwd -T '\[gg\].png' 'ftp://ftp.liondrive.com:2221'
Last edited by lolilolicon (2009-06-24 07:26:43)

EAR Deployment Problem UNIX vs Windows

Hi Experts,
My WAS is 6.40. We are running on AIX Unix System. On my portal I need to deploy an EAR File. I can very well deploy that EAR file through the SDM but when I try to call the JSP, it throws an error "No calss def found". This error corresponds to a Class file which is inside a JAR. It is not able to locate that class file. We are using some external JARS. I have packages these JARS in my EAR.
One point to notice is that If I deploy this EAR on a WINDOWS server. It runs absolutely fine and it also is able to find the class in the JARS. The problem is with the AIX UNIX server only.
Is there some config that I need to do on the UNIX system ? I think the EAR structure is giving the problem. But then It should not run on Windows also.
Any suggestions ?
Regards
/sab

HI Kedar,
Thanks for your reply. Do u mean to say that the JARS for AIX have to be different ?
One observation. The EAR works fine on SAP WAS (Windows) and TOMCAT (Windows) but refuses to run on AIX.
Following is the error :
Application error occurred during request processing.
Details: java.lang.NoClassDefFoundError: tellustech/licensing/ClientChecker
Exception id: [001125A6424A0054000000060007608C00043ECE62BAC38A]
What is it about the .SO files ? What is their role in this chain ? Can u pleaese help me undesrand that more ?
<i>"3. As you have mentioned the problem causes if files mismatch between 32 bit & 64 bit."</i> what I had mentioned was a question asking that If my AIX box is 64 bit and I develop my application on a 32 bit laptop. Whould this kind of difference cause this problem ?
So u mean to say that I should provide the following Info to my JAR provider for giving me JARS specific to AIX?
1.Machine Type
2.Operating System
3.Processor
4.System Type
5.Operating System Version
6.Release Level
7.CPU Version
8.Java Version
9.Java Path
10.Compiler Used
11.Compiler Path
Dont worry about the points U'll get the max. Help me resolve this ?
Are u in India, can we talk on the phone for this. I really need to fix this ASAP.
Regards
/sab

Terracotta: application deploy problem (WLP 9.2)

hi,
when i try to deploy a Portal application on a bea weblogic server (9.2.1), that is enabled for terracotta (added the java startup arguments to the bea server and the client is visible in the Terracotta Administrator Console), the deployment fails and a lot of compile errors are shown concerning bea classes (from netuix.jar and content.jar, see bottom for snippet). for some reason bea wants to compile these classes on deployment.
has anybody seen this same problem and does anybody have a solution or workaround for this problem? must the classes be compiled on the fly during development?
regards,
erik
log snippet:
####<Oct 4, 2007 6:48:49 PM CEST> <Error> <Deployer> <opteron-w2k3> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1191516529616> <BEA-149205> <Failed to initialize the application 'ps' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(netuix.jar)
Unable to deploy EJB: netuix.jar from netuix.jar:
There are 1 nested errors:
java.io.IOException: Compiler failed executable.exec:
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\wsrp\services\persistence\internal\ProducerPersistenceManager_7vyoe8_Impl.java:11: com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.wsrp.services.persistence.internal.ProducerPersistenceManager_7vyoe8_Intf
public final class ProducerPersistenceManager_7vyoe8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\BookDefinitionManager_1xzrxc_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.BookDefinitionManager_1xzrxc_Intf
public final class BookDefinitionManager_1xzrxc_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortletCategoryManager_uhkdka_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortletCategoryManager_uhkdka_Intf
public final class PortletCategoryManager_uhkdka_Impl
[MORE CLASSES HERE]
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PortalDefinitionManager_d875a8_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PortalDefinitionManager_d875a8_Intf
public final class PortalDefinitionManager_d875a8_Impl
^
D:\beas\bea921\user_projects\domains\eo_domain\servers\AdminServer\cache\EJBCompilerCache\-1qrbdkqefeo8m\com\bea\netuix\application\manager\persistence\jdbc\PageDefinitionManager_c4el9c_Impl.java:11: com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Impl is not abstract and does not override abstract method __tc_setmanagedfield(java.lang.String,java.lang.Object) in com.bea.netuix.application.manager.persistence.jdbc.PageDefinitionManager_c4el9c_Intf
public final class PageDefinitionManager_c4el9c_Impl
^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
25 errors
     at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:435)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:295)
     at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:303)
     at weblogic.ejb.container.ejbc.EJBCompiler.doCompile(EJBCompiler.java:309)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:497)
     at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:464)
     at weblogic.ejb.container.deployer.EJBDeployer.runEJBC(EJBDeployer.java:430)
     at weblogic.ejb.container.deployer.EJBDeployer.compileJar(EJBDeployer.java:752)
     at weblogic.ejb.container.deployer.EJBDeployer.compileIfNecessary(EJBDeployer.java:655)
     at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1199)
     at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:354)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:360)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46)
     at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
     at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:137)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

the deployment problem is solved by putting the bea packages in the exclude section of the Terracotta configuration file.

BEA WLS 6.1 SP2: Deploy problems (JDBCConnectionPool/JDBCTxDataSource)

Hello anybody,
learnt XA being necessary if more than one sql command in transaction, so I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now I receive the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction branch
start() failed on resource 'OracleDB' Unexpected error during start for XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Hi Klaus,
if you want to implement a global transaction over two different JDBC Resource Managers
(update on both + 2PC) they have to be both XA compliant.
Or you could have only one of them XA compliant(i.e: one 8.1.6 or higher Oracle instance):
for the other one (i.e.: one 7.3.2 Oracle instance) you could use a non XA-driver
and configuring a TXDataSource with "enable two-phase commit" = true (but only one
non-XA JDBC driver at a time can participate in a distributed transaction).
Well, XA transactions are not a pre-requisite for EJB: you could use simple "local"
transactions or distributed transactions without XA drivers as well (using a single
resource manager).
But if you want to update multiple resource managers in the same transaction using
EJBs, this is a "global" transaction, and WL server fully supports it.
But the partecipants must be XA compliant to be able to "talk" to WL coordinator.
Sergi
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
>
Hi Sergi, hello world,
thanks a lot for this message. So the conclusion is that I hava no chance
at all
to use this oracle version (7.3.2) with BEA WLS (or more common EJB), cause
a prerequisite
for EJB are XA-transactions.
Is this conclusion correct.
Many thanks again
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
distributed transaction (XA) features require version
Oracle8i release 8.1.6 or later of the Oracle server.
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hi Sergi,
1.) sorry, that was a typing error with the oracle version, I meant 7.3.2.
2.) I didn´t use a special driver but that that was delivered with thewls
server
in the package "weblogic.jar".
Could I enable you helping me with this information?
Best wishes
Klaus
"Sergi Vaz" <[email protected]> wrote:
Hi Klaus,
which
1) Oracle server version (I don't think it's a 8.3.2.)
2) Oracle JDBC driver version
are you you using ?
Sergi
"Klaus Dirlewanger" <[email protected]> wrote:
Hello anybody,
learnt XA being necessary if more than one sql command in transaction,so
I changed
my entries to the following:
<JDBCConnectionPool
DriverName="oracle.jdbc.xa.client.OracleXADataSource"
Name="OracleDB"
Password="{3DES}iKOCmvzSc6g="
Properties="user=osv"
Targets="osvServer"
TestConnectionsOnReserve="false"
URL="jdbc:oracle:thin:@pegnitz:1526:ora1"/>
<JDBCTxDataSource
JNDIName="JNDINameOracleOSV-DB"
Name="OracleDataSource"
PoolName="OracleDB"
Targets="osvServer"/>
We set up on a database ORACLE 8.3.2.
Now, with the non-XA-driver there was no deployment problem, but now
I
receive
the
following error message on the server output:
Unable to deploy EJB: CourseDateEJB from osv.jar:
The Container-Managed Persistence Entity EJB failed while creating itsSQL
Type Map.
The error was:
XA error: XAER_RMERR : A resource manager error has occured in the transaction
branch
start() failed on resource 'OracleDB' Unexpected error during start
for
XAResource
'OracleDB': null
     at weblogic.ejb20.deployer.Deployer.deploy(Deployer.java:1019)
     at weblogic.j2ee.EJBComponent.deploy(EJBComponent.java:30)
     at weblogic.j2ee.Application.deploy(Application.java:247)
     at weblogic.j2ee.J2EEService.deployApplication(J2EEService.java:185)
     at weblogic.management.mbeans.custom.Application.setLocalDeployed(Application.java:362)
     at weblogic.management.mbeans.custom.Application.setDeployed(Application.java:296)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeSetter(DynamicMBeanImpl.java:1388)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:881)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:392)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:298)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.RemoteMBeanServerImpl_WLSkel.invoke(Unknown
Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Many thanks if s.b. could help me.
Klaus

Deployment problem in jdeveloper9i

hi ,
i have a project containing jsps in jdeveloper9i..i want to deploy it to an oracle9i AS .. i have followed the steps of creating new deployment profile and choosing (war file)
and then i have created the connection to the application server and named it oracle 9ias ..
then i have Right-clicked the deployment profile webapp.deploy and choose Deploy to oracle 9ias which is the name of the connection..
but the deployment did not succeed
at the point of Invoking Oracle9iAS admin tool
it takes a very long time then gives me a message that deployment is incomplete..
can anyone help?

Hi Mona,
I can't help you (sorry), but have you tried asking your question on the "JDeveloper" forum:
JDeveloper and ADF
or the "General" forum:
Oracle Application Server - General
Hopefully someone there will be able to help you.
Good Luck,
Avi.

Renaming function contained @ in the DLL

Hello every one.I have a bunch of code . THis code connect t othe exteral library:
public interface TransToQuik extends Library{
public int _TRANS2QUIK_CONNECT@16(String lpcstrConnectionParamsString, LongByReference pnExtendedErrorCode, String lpstrErrorMessage, int dwErrorMessageSize);
LongByReference pnExtendedErrorCode= new LongByReference();
    String Error;
    int len;
    int FunctionResult=0;
    String lpstrErrorMessage="";
    int dwErrorMessageSize=0;
    TransToQuik lib = (TransToQuik) Native.loadLibrary ("D://java project//Robot//TRANS2QUIK.dll",TransToQuik.class);
   FunctionResult=lib._TRANS2QUIK_CONNECT@16("D://QUIK5.15//",pnExtendedErrorCode,lpstrErrorMessage,dwErrorMessageSize);
    System.out.println(lib);But it is do not work cause the JAVA do not understand function contained @ in the name. In iinteret i find no examples. Please help me.

For the future it would be useful to mention which libraries you use. In your case it seems to be JNA.
Since that function hasn't got a name that's a valid Java name, I doubt that you can easily call it like that.
But from the documentation it seems that there is at least one other way to call native functions with JNA:
[Create a Function object|https://jna.dev.java.net/javadoc/com/sun/jna/Function.html#Function(com.sun.jna.NativeLibrary,%20java.lang.String,%20int)] and call that objects invoke() method.
Edit: By the way, the name of the language and platform is "Java". It's not "JAVA", because it's not an acronym.

War problems- Deployment descriptor is malformed, check agains the DTD (0/1)

I'm sorry for cross-posting this but I don't know which is the correct
newsgroup to post this.
I have posted this before but I haven't had a successful response that
has solved my problem so I'm reposting it again.
I'm trying to create an ear file for our ejbs and servlets. I create
my war file and ejb jar files and then create the ear file. When I
start weblogic the ejbs load fine but I get an error when loading my
war file. The error is Deployment descriptor is malformed, check
against the DTD. The weblogic.xml and web.xml files are the same
files that I place in the
/config/investia/applications/DefaultWebApp_javelin/WEB-INF.
Our current way of deploying our application is to create one jar file
that contains all our classes and add this to the system classpath and
and add the web.xml and weblogic.xml file in the WEB-INF directory.
We also specify the jar files in the config.xml file to point to this
jar.
One of the things that I also tried to do is just to grab the web.xml
and the weblogic.xml file from the petStore.war file that was in the
petStore.ear file located in the /config/petstore/applications
directory. I did not modify this file and just used this file as is
when I created my war file with my own classes. I just wanted to know
if I was going to get any DTD errors. Sure enough, I got DTD errors
when parsing this file. I was hoping this would load and I would get
some classpath not found error or something else because I didn't copy
any of the classes.
I have attachec my web.xml and weblogic.xml files that work fine when
not building the war file. I just can't seem to figure this out and
would appreciate all the help I can get. The web.xml file only has
one servlet active and everything below that is commented out.
Thanks,
Ruben

Hi,
The issue is not in the weblogic.xml file, the issue is on your classpath, JAVA_HOME variable, or on the starting script for your managed server that sets one variable wrong and the managed node is not able to find the proper JDK. My guess would be that it is the last one.
You may ignore the weblogic.xml warning (at least in WL 8.x) and correct that whenever you have some cycles left.
Regards,
LG

Deployment problems EAR & WAR

I have serious problems deploying an EAR, containing 25 ejb-jars and 3 wars.
The history of the project is that it was first developed on WLS 4.5 & 5.1. We
have later moved to Orion were the actual development takes place. Now we can
run the application on Orion and WLS 5.1. We now want to deploy the application
on WLS 6.1 sp 2. We have setup the whole application to be deployed as one EAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think it was).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to the console,
however when I tried to access servlets or JSPs, they simply weren't there (Error
404--Not Found). When I deployed the EAR from the console I got a number of zipexceptions.
After asking around, I was recommended to remove the compression in the jar,war
& earfiles. When I did that I got a number of errors in static initializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed those and
the application was deployed without errors (when I start WLS and the EAR is deployed
by being in the config.xml file). Still when I deploy it from the console it still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there. The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'm also
confident that modules are correct, it does work in Orion, which has similar classloading.
From other developers, I have heard that I need to use WLS 6.1 sp 2, no compression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB) files.
What really annoys me that I do not seem to get any errors, logs or anything.
The console indicates that everything is deployed even if apparently is not.
And I can deploy PerStore and everything works. If I deploy the wars, and ejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I think that
I have to skip my first intent and deploy an exploded EAR instead of having (almost)
the same deployement as in Orion, which kind of pisses me of. I am also disappointed
that BEA has apperantly skipped java-modules all together. It is after all in
the specification.
I have talked to a number of people and they say that the whole EAR deployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson

EAR deployment works fine from my own experience. Use JAR and turn off
compression for the WARs and JARs and the EAR itself, although I've never
seen a ZIP exception and I use JAR and ZIP and Winzip and whatever else I
can grab to muck with the files. 6.5MB is not tiny, but it isn't very large
either -- WL can handle much bigger EARs. Normally we don't suggest having
so many JARs and WARs in the EAR, but that is more preference ... are you
using manifest class path? ... are you referring to any of the files in the
WARs from any of the classes in the JARs?
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Erik Romson" <[email protected]> wrote in message
news:[email protected]...
>
I have serious problems deploying an EAR, containing 25 ejb-jars and 3wars.
The history of the project is that it was first developed on WLS 4.5 &5.1. We
have later moved to Orion were the actual development takes place. Now wecan
run the application on Orion and WLS 5.1. We now want to deploy theapplication
on WLS 6.1 sp 2. We have setup the whole application to be deployed as oneEAR,
this works fine with Orion. The whole building is made in Ant.
I'm new on WLS 6.1 but have worked a lot on WLS 5.1 and 4.5 (I think itwas).
I might have missed something but the documentation on EAR is very short.
When I first deploy the EAR, it seemed to work fine according to theconsole,
however when I tried to access servlets or JSPs, they simply weren't there(Error
404--Not Found). When I deployed the EAR from the console I got a numberof zipexceptions.
After asking around, I was recommended to remove the compression in thejar,war
& earfiles. When I did that I got a number of errors in staticinitializers in
EJBs, which indicated that the EJBs actually were deployed. I fixed thoseand
the application was deployed without errors (when I start WLS and the EARis deployed
by being in the config.xml file). Still when I deploy it from the consoleit still
throws ZipExceptions.
Anyway now I can access one of the war files but the other is not there.The deployed
war file is a lot smaller than the one not being deployed.
I think that all settings in application.xml, web.xml etc is correct. I'malso
confident that modules are correct, it does work in Orion, which hassimilar classloading.
>
From other developers, I have heard that I need to use WLS 6.1 sp 2, nocompression
and that I have to break up large EARs in smaller (my EAR is 6,5 MB)files.
>
What really annoys me that I do not seem to get any errors, logs oranything.
The console indicates that everything is deployed even if apparently isnot.
>
And I can deploy PerStore and everything works. If I deploy the wars, andejbs
from the console (one at a time), it works.
I would appreciate any help on this subject any workarounds etc. I thinkthat
I have to skip my first intent and deploy an exploded EAR instead ofhaving (almost)
the same deployement as in Orion, which kind of pisses me of. I am alsodisappointed
that BEA has apperantly skipped java-modules all together. It is after allin
the specification.
I have talked to a number of people and they say that the whole EARdeployment
in WLS is very shaky. Is this true?
Thanks in advance,
Erik Romson

MDB Deployed Twice/Once not even under the JAR that contains it

We have an application that has multiple jars bundled into one ear. Our application
tag looks like follows from the config.xml for the project:
<Application Name="Central"
Path="C:\PPOS\2004.1.0\Application\Central Server\weblogic\applications\pposcentralserver.ear"
StagedTargets="central" StagingMode="stage" TwoPhase="true">
<EJBComponent Name="commonserver" Targets="central" URI="commonserver.jar"/>
<EJBComponent Name="hostcommonserver" Targets="central" URI="hostcommonserver.jar"/>
</Application>
hostcommonserver.jar contains a MDB. It gets deployed properly and if I monitor
the queue it looks at on another server I can see it has "connected". The problem
however is on this server if I monitor commonserver.jar, the same MDB shows up
there even though it is NOT contained in the deployment descriptors for that jar.
If I look on the server that contains the queue I can see that there are twice
as many consumers as there should be.
The weird part. If I change the name in the <EJBComponent> tag above from "commonserver"
to anything else, this does not happen.
I have not tested putting a message on the queue to see which MDB consumes it
(getting to that point of testing will take me some time so I wanted to get the
ball rolling on this) however I feel there is some bug here and since using the
WLS console to look at the properties of this MDB is an often used part of support
troubleshooting for this product, I can't have the wrong version of the MDB in
place consuming messages while the correct one sits idly by making it appear it
is not getting messages.
Thanks.

Try posting to the jms newsgroup.
cheers
mbg
"Jeff Walsh" <jeff.walsh@no_spam_jda.com> wrote in message
news:3fb298e4$[email protected]..
>
Bump...
"Jeff Walsh" <[email protected]> wrote:
We have an application that has multiple jars bundled into one ear.
Our application
tag looks like follows from the config.xml for the project:
<Application Name="Central"
Path="C:\PPOS\2004.1.0\Application\Central
Server\weblogic\applications\pposcentralserver.ear"
StagedTargets="central" StagingMode="stage" TwoPhase="true">
<EJBComponent Name="commonserver" Targets="central"URI="commonserver.jar"/>
<EJBComponent Name="hostcommonserver" Targets="central"URI="hostcommonserver.jar"/>
</Application>
hostcommonserver.jar contains a MDB. It gets deployed properly and if
I monitor
the queue it looks at on another server I can see it has "connected".
The problem
however is on this server if I monitor commonserver.jar, the same MDB
shows up
there even though it is NOT contained in the deployment descriptors for
that jar.
If I look on the server that contains the queue I can see that there
are twice
as many consumers as there should be.
The weird part. If I change the name in the <EJBComponent> tag above
from "commonserver"
to anything else, this does not happen.
I have not tested putting a message on the queue to see which MDBconsumes
it
(getting to that point of testing will take me some time so I wanted
to get the
ball rolling on this) however I feel there is some bug here and since
using the
WLS console to look at the properties of this MDB is an often used part
of support
troubleshooting for this product, I can't have the wrong version of the
MDB in
place consuming messages while the correct one sits idly by making it
appear it
is not getting messages.
Thanks.

Is it possible to deploy an EAR to a Netweaver AS without restarting the AS

The application has been designed to use multiple Java Resource bundles that contain various messages and properties that are updated quite often. The Resource Bundles have been separated into separate SCAs so that they can be deployed separate from other parts of the application. Is it possible to deploy the EARs contained within these SCAs without restarting the Java AS?
We are working with NWDI 7.1 deploying to Java 1.5 running on zLinux

Hi,
That should be no problem at all. Any machine with or without NI software can use an FTP client to transfer files to and from an RT target such as CompactRIO.
You should be able to build the executable on the development machine, transfer it via USB drive to another machine and then use FTP software to transfer the file from there. You'll just need the IP address of the target and login information.
For more information on FTP transfer with or without MAX to RT targets, see the following KB article:
http://digital.ni.com/public.nsf/allkb/4DCF9D581C491E9F8625711B005FA539?OpenDocument
I hope this helps, please don't hesitate to reply with more questions on the subject.
Regards,
Tom
Applications Engineering, NI UK

Two AM's with the same name but different forms causes Deployment problems

Two Masters forms, DOC & PM are cloned except for the "where clause" in the View's query and the titles in their JSP's.
DOC workspace has a BC project and a BC4JSP Project. The BC project comprises of the EO and VO named ComVsStaticValue. In the Edit prop-> query for the VO I have specified the "where clause" as VSSV_VS_CODE='DOCTOR'.
In Java Webserver :-
The JSP's are located in C:\source\Doctor\ .. and the *.xml and *.class files generated by the BC proj is in C:\source\Doctor\pol_ValueSet\..
If I execute Doctor in JWS the records are getting filtered properly.
PM workspace has a BC project and a BC4JSP Project. Again The BC project comprises of the EO and VO named ComVsStaticValue. In the Edit prop-> query for the VO I have specified the "where clause" as VSSV_VS_CODE='PAY_MODE'.
In Java Webserver :-
The JSP's are located in C:\source\PMode\ .. and the *.xml and *.class files generated by the BC proj is in C:\source\PMode\pol_ValueSet\..
If I execute PM in JWS, the PM's JSP comes (the title is correct) but the records pertaining to DOC appears. I checked the View's xml file in C:\source\PMode\pol_ValueSet\ the "where clause" is correct. The xml & classes have the same name but their contents are different.
I want to know whether this problem is because both have the same name for the AM and the BC4JSP's property file.
Please clarify.

Deploying two app modules with the same name will definitely cause problems.
The JSPs use the information in the properties file to connect to the application module and get the data they need from the appropriate View Objects in those app modules. If you have two app modules with the same name, when a JSP tries to connect, it has no way of knowing which one of the app modules to connect to if they both have the same name.
You could:
1. Just use one application module that contains all the View Objects you need to access.
or
2. Rename one of the application modules or the package it is located in so the names are distinct. If you choose this method, you will also need to update the JSPs (specifically the 'registerApplicationFrompPopertyFile' method call), and your JSP project's appmodule property file.

Ear deploy problems if dir contains '.' in the name

Similar Messages

Maybe you are looking for