All,
OSB does not refer to the files in the MDS repository like SOA Suite applications does. Instead, the files are imported into the Service Bus application.
We are having multiple OSB projects, when we make any changes to the common XSD file, the XSD file needs to be manually copied over to all the OSB projects.
Is there any solution available to keep the common xsd's in location and point all OSB projects to use the XSD from the common location?
Thank you
Related
I have a WPF application.. I need to create 3 setups, each setup is for an environment(development, staging and production), I've put each environment configuration into App.config file of my main UI project. I need Installshield to pull the appropriate configuration file while creating the setup file.
A question: Is there a way to do it differently?
thanks,
There are several approaches you could take. Here's one:
In recent versions of InstallShield (Professional and higher editions), you can override Path Variables on a per-Release basis. If you craft your source filesystem and source path correctly, this should let you select from multiple source app.config files just by building a different release.
How can i include txt files and access to them within play framework? I need to load some text from .txt files depending on user request. I'm used to access files from inside jars and thinking in deploying the web as a runnable jar.
You can do exactly the same thing in Play. It doesn't matter whether your application is packaged as a jar file or not.
The resource file just needs to be on the CLASSPATH.
My Java JSP application requires to store permanent files on the Tomcat web server. At the moment I save the files in the "/temp" folder of the System. But this folder gets cleared from time to time. Further, the current solution is hard-coded which makes it less flexible (e.g. when moving to another server).
I would like to now if there is a best practice for defining and accessing a permanent directory in this configuration. In detail, where is the best place to define the app file directory, and how would I access this from within my java application? The goal of this setup would be to cause the least effort when (a) updating the application (i.e. placing a new war file), and (b) moving from one server to another and OS (e.g. Unix, Windows, MacOS).
The research I have done on this topic so far revealed that the following would be solutions (possibly amongst others):
1.) Use of a custom subdirectory in the Tomcat installation directory.
What happens to the files if I deploy a new version on the tomcat via
war file?
Where do I define this directory to be accessed from
within my Java application?
2.) In a separate directory in the file system.
Which are good locations or ways to get the locations without knowing
the system?
Where do I define this directory to be accessed from
within my Java application?
Thank you for your advice!
Essentially, you are creating 'a database' in the form of some files. In the world of Java EE and servlet containers, the only really general approach to this is to configure such a resource via JNDI. Tomcat and other containers have no concept of 'a place for persistent storage for webapps'. If a webapp needs persistent storage, it needs to be configured via JNDI, or -D, or something you tell it by posting something to it. There's no convention or standard practice you can borrow.
You can pick file system pathname by convention and document that convention (e.g. /var/something on Linux, something similar on Windows). But you won't necessarily be aligned with what anyone else is doing.
I am porting a Java EE application from Oracle 10g Application Server to Oracle 11g Weblogic Server.
I have a common.jar which contains Connection related classes and present inside war/web-inf/lib. The application is deployed as an EAR and the ejbs also refer to classes inside the common.jar to get DB Connection. The EJB is not able to get reference to these classes at runtime. I copied the common.jar inside APP-INF/lib directory, In that case what happens is the JSP’s are unable to get reference to the Connection related classes. I have jsp’s which has sql code embedded in it. This application was developed way back and do not have the business knowledge change these code now.
How can I solve this issue? How the ejb can get reference to the classes located inside war/web-inf/lib.
You cannot have the EJB look into the WAR WEB-INF/lib for classes. That goes against the Classloader Hierarchy for Weblogic.
Putting the common jar in the APP-INF/lib is the correct way to go
WebLogic Server provides a location within an EAR file where you can
store shared utility classes. Place utility JAR files in the
APP-INF/lib directory and individual classes in the APP-INF/classes
directory. (Do not place JAR files in the /classes directory or
classes in the /lib directory.) These classes are loaded into the root
classloader for the application.
Can you also post the errors JSPs get when they are unable to load these? Are these ClassNotFoundException or NoClassDefFoundError or something else ?
Also see the Best practices for using Shared Java EE Libraries
Is it a good idea? I've never seen it done before.
The application in question is an enterprise project deployed as an EAR file on an app server. Properties include path to log file, name of JMS topic, etc. The intention being properties can be queried at runtime from the database, rather than having to redeploy the entire application, which might cause downtime and require developer/administrator attention.
How else would I modify runtime properties of the enterprise application?
Thanks.
You can do that or you can use properties file (config file) to store such info as I have seen this done on multiple projects. The preference of choosing between database and properties file is dependent on many factors but assuming the data are too little to be on database table, it's really fine for both solutions.