Changes in EJB when deployed in JBoss

Hi,
We Created the Enterprise Application (EJB Project and WebProject) in the JDeveloper11g preview 1. It is Sucessfully working when it deployed in OC4J application server. I want to deploy the same application in the JBoss. what are the changes i should to deploy the the same application in JBoss. Can any one help me.
Thanking you,
NIRANJAN REDDY.

hi NIRANJAN REDDY (Prapan Sol)
see also the JDeveloper 11g Release Notes about deployment
http://www.oracle.com/technology/products/jdev/htdocs/11/knownissues.html#gi2
"+ADF 11g applications require a Java EE 5 container. To date, only Oracle WebLogic Server 10g (10.3) is certified, and *we plan to support JBoss* and Tomcat as well. Note, OC4J 10.1.3 and/or OAS 10.1.3 is not fully Java EE 5 compliant, and ADF 11g applications will not work in that environment.+"
success
Jan Vervecken

Similar Messages

Very Strange Problem... Missing hidden field when deployed on JBOSS

This problem is driving me nuts. Here it is... When I deploy my app to TomCat it works fine. When I deploy to JBoss everything works except the links . When I select a link rendered via JBoss the directory containing the JSP is displayed. I can also see that my filters are not being called in this case. I compared the HTML produced by TomCat to the HTML produced by JBoss and there was one minor difference. This hidden field was not rendered in JBoss:
<input type="hidden" name="contentView:contentForm:_idcl" />When I manually include this in the JSP and run JBoss.. It works.
I have spent a full day trying to figure out when the hidden field is not being rendered when deployed to JBoss... I would very much appreciate any suggestions.. Thanks in advance. Paul
Here is a bigger snippit:
<tags:layout
 heading = "/banner.jsp"
 menu = "/mainmenu.jsp">
 <f:subview id="contentView">
 <f:loadBundle basename="com.dygtig.bundles.labels" var="labels" />
 <h:messages layout="table" tooltip="Please review errors and resubmit."
 fatalClass = "msgFatalText"
 errorClass = "msgErrorText"
 warnClass = "msgWarnText"
 infoClass = "msgInfoText"/>
 <h:form id="contentForm" style="display:inline">
 <f:verbatim><CENTER></f:verbatim>
 <h:outputText value="Aircraft Types" styleClass="pageTitle"/>
 <f:verbatim> </f:verbatim>
 <h:dataTable value = "#{aCTypeListView.acTypes}"
 var = "ac"
 first = "0"
 rows = "15"
 columnClasses= ""
 styleClass = "normaltable"
 width = "500px" title="Aircraft List"
 rowClasses = "normaltabletext1,normaltabletext2"
 id = "AircraftTable">
 <h:column>
 <f:facet name="header">
 <h:outputText value="Action"/>
 </f:facet>
 <h:commandLink action="#{aCTypeListView.updateActype}">
 <f:param name="acId" value="#{ac.id}"></f:param>
 <h:outputText value="Upd" styleClass="commandLink"/>
 </h:commandLink>
 <h:outputText value=" "></h:outputText>
 <h:commandLink action="#{aCTypeListView.deleteActype}" >
 <f:param name="acId" value="#{ac.id}"></f:param>
 <h:outputText value="Del" styleClass="commandLink"/>
 </h:commandLink>
 </h:column>
 <h:column>
 <f:facet name="header">
 <h:outputText value="Type-Suffix"/>
 </f:facet>
 <h:outputText value="#{ac.typeSuffixText}"/>
 </h:column>
 <h:column>
 <f:facet name="header">
 <h:outputText value="Model"/>
 </f:facet>
 <h:outputText value="#{ac.model}"/>
 </h:column>
 </h:dataTable>
 <dygtig:tablescroller tables="AircraftTable" />
 
 <h:commandLink action="#{aCTypeListView.createActype}">
 <h:outputText value="Create New Aircraft Type" styleClass="link"/>
 </h:commandLink>
 
 </CENTER>
 
 <! manually add hidden field here> </h:form>
 </f:subview>
</tags:layout>

Hi Paul,
I have the same problem under deployment to WAS, all <h:commandLink>s are out of order. The hidden form field '...:_idcl' is missing in the generated JSP, but will be generated under Tomcat.
Have you found a solution?
Cheers, Ralf.

Jdeveloper - how to change security mode when deploying to integratedserver

HI
I'm using jdeveloper 11.1.1.2.0.
I want to deploy webadf application to integrated weblogis server.
However, i cannot find a way to change security model from CustomRolesAndPolicies to CustomRoles.
The only way is, to deploy application manually via console. But if you deploy manually, you have to do it all the time; its not possible to update it from IDE.
Thanks in advance.
Mitja

You need to ask Apple to reset your security questions. To do this, click here and pick a method; if that page doesn't list one for your country or you're unable to call, fill out and submit this form.
(117238)

Changing PollingFrequency when deploying?

Hi,
We have a few FTP-adapter based polling flows and I wonder if anyone know of any way to either programaticaly change the value of PollingFrequency or alter it when deploying.
We have to have the value set to 15 minutes in the production environment but that is not very nice in on development server as it takes a while to test things if I have to wait 15 minutes for a file to be picked up by BPEL.
So does anyone know a way to either change this value depending on which server it resides on or possibly force the FTP adapter to pickup files regardless of the value?
The ideal option would be to somehow set it via a property in the bpel.xml file as we already use that file to change various aspects when deploying the process to various environments.
// MickeM

Thanks for your reply.
We currently use ant to deploy but have opted to use different bpel.xml files for the various environments as "most" things can be set there and we found it to be slightly more predictable than search-replace in "various files".
The problem we found with search-replacing in the wsdl file is that we both have no "default name" for the in-ftp wsdl-filename (some flows even have more then one) so it would require a "separate build step" for each flow to work that way and also since "search replace" would spread the changes over multiple files it would be hard for the customer to maintain the platform in the long run.
As it is now we have a "single point" where we have all our "specific configurations" so from a maintinence perspective it is easy to see "why" a value is used and whence it came.
So a way to alter/control it from bpel.xml (or similar) would be preferable.
But perhaps that is not possible?
// MickeM

Invalid change to class error when deploying EJB

We have EJBs that were built by Webgain Visual Cafe and successfully deploy
to WLS 5.1. We then use the WLE EJB Deployer Tool to build WLE container
classes and deploy the same EJBs in WLE 5.1.
One EJB does not deploy in WLE. The ULOG error message is:
133929.EA-LAWSTUC!JavaServer.517: main: IJENGINE_CAT:150: ERROR: Invalid
change to class service.Request
133929.EA-LAWSTUC!JavaServer.517: main: EJB_CAT:29: ERROR: While deploying
jar ServiceEJB : com.beasys.weblogic.classloader.RedeploymentException:
ERROR: Invalid change to class service.Request
133929.EA-LAWSTUC!JavaServer.517: Finalizer: IJENGINE_CAT:152: INFO: Closing
jar C:\aj\ServiceEJB_WLE.jar
Does anyone know what can cause an "invalid change to class" error when
deploying to WLE 5.1? Especially since the EJB deploys successfully in
WLS.
Carl Lawstuen

Reason: database keeps a reference of the class in JAVA$CLASS$MD5$TABLE table. This table keeps a refrence to all java classes loaded in database, and is present in each schema you deploy classes. That's the reason why if you change the application module name, you can load this classes. It instead keeps a reference if you use DROP JAVA CLASS command to drop a java class from de database. Use DROP JAVA command to clear the reference of the dropped classes when dropping it.
You can see this table as a class dictionary of the database, and you don't have to handle this records manually.

Changes in EJB3.0 application when deployd in JBoss

Hi,
We Created the Enterprise Application (EJB Project and WebProject) in the JDeveloper11g preview 1. It is Sucessfully working when it deployed in OC4J application server. I want to deploy the same application in the JBoss. what are the changes i should to deploy the the same application in JBoss. Can any one help me.
Thanking you,
NIRANJAN REDDY.

This is the Forms forum, your question seems to be related to JDeveloper try posting the question in the [JDeveloper Forum|http://forums.oracle.com/forums/forum.jspa?forumID=83] .
Tony

Classpath problem when deploying a persistence unit (in JBoss)

Hello,
I have a JAR file containing an EJB with a persistence.xml file.
I also have another JAR project containing a persistent annotated POJO class that the persistence unit is supposed to map.
I defined the class in the persistence unit using a class XML element, but because it's in another JAR, the persistence unit implementation cannot find it. I tried to use a jar-file element instead and specify the name of the JAR containing the POJO, and from the log it seems the class is found and identified as persistent, but then the actual mapping operation fails because of the same reason! I also tried to edit the classpath property in the EJB JAR's manifest fileto include the POJO JAR, but that did not help too...
Does anyone know what I'm missing here and how to make the persistence unit succeed in mapping the POJO class?
Thanks.

Ok, some more details regarding the problem:
Here is the persistence unit definition:
<persistence-unit name="NorthwindPU" transaction-type="JTA">
 <provider>org.hibernate.ejb.HibernatePersistence</provider>
 <jta-data-source>jdbc/NorthwindDB</jta-data-source>
 
 <jar-file>TestProjectPersistence.jar</jar-file>
 <properties>
 <property name="hibernate.transaction.factory_class"
 value="org.hibernate.transaction.CMTTransactionFactory"/>
 <property name="hibernate.transaction.manager_lookup_class"
 value="org.hibernate.transaction.JBossTransactionManagerLookup"/>
 <property name="hibernate.dialect" value="org.hibernate.dialect.PostgreSQLDialect"/>
 <property name="hibernate.current_session_context_class" value="jta"/>
 </properties>
</persistence-unit>Here is the stack trace I get when starting the server and deploying the application:
javax.persistence.PersistenceException: [PersistenceUnit: NorthwindPU] class or package not found
 at org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1093)
 at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:871)
 at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:758)
 at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:425)
 at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:131)
 at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:301)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
 at java.lang.reflect.Method.invoke(Unknown Source)
 at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
 at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
 at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
 at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
 at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
 at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
 at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
 at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
 at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
 at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
 at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
 at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
 at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
 at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
 at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
 at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
 at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
 at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
 at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
 at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
 at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
 at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
 at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
 at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
 at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
 at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
 at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
 at org.jboss.Main.boot(Main.java:209)
 at org.jboss.Main$1.run(Main.java:547)
 at java.lang.Thread.run(Unknown Source)

EJB 3.0 deployment on JBoss - No ClassLoaders found

I have problem deploying a simple EJB 3.0 jar file , it contains an Interface , its Bean and the jboss.xml
jboss.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss>
<enterprise-beans>
<session>
<ejb-name>ServerDBConnectionBean</ejb-name>
<management>org.jboss.ejb3.test.service.ServiceSixManagement</management>
<ejb-class>connection.server.ServerDBConnectionBean</ejb-class>
<remote>connection.server.ServerDBConnection</remote>
<jndi-name>ServerDBConnectionBean</jndi-name>
</session>
</enterprise-beans>
</jboss>
The problem is that when i deploy this jar file in JBoss , it says .........
12:10:17,988 WARN [ServiceController] Problem creating service jboss.j2ee:service=EJB3,module=server.jar
java.lang.ClassNotFoundException: No ClassLoaders found for: connection.server.ServerDBConnectionBean
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.ejb3.Ejb3AnnotationHandler.populateBaseInfo(Ejb3AnnotationHandler.java:265)
at org.jboss.ejb3.Ejb3DescriptorHandler.populateBaseInfo(Ejb3DescriptorHandler.java:202)
at org.jboss.ejb3.Ejb3AnnotationHandler.getContainers(Ejb3AnnotationHandler.java:123)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:409)
at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:397)
at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:378)
at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:350)
at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:305)
at org.jboss.ejb3.Ejb3Module.createService(Ejb3Module.java:77)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:330)
at org.jboss.system.ServiceController.create(ServiceController.java:273)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy28.create(Unknown Source)
at org.jboss.ejb3.EJB3Deployer.create(EJB3Deployer.java:429)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss.DeployerInterceptor.create(DeployerInterceptor.java:74)
at org.jboss.ws.integration.jboss.DeployerInterceptorEJB.create(DeployerInterceptorEJB.java:44)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy29.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
I suppose the problem is with the package , cause when i deploy with single package hirarechy i.e; server.ServerDBConnectionBean , it works .
Kindly any suggestions

hi
I think you ur jboss.xml is wrong.
Try using like this for EJB3
 <enterprise-beans>
 <session>
 <ejb-name>XXX</ejb-name>
 <jndi-name>XXXX</jndi-name>
 <local-jndi-name>XXXXX</local-jndi-name>
 </session>
 </enterprise-beans>I think <ejb-class> is not supported in jboss.xml..
Regards
Srinivas

How to access EJB deployed in JBOSS 4 from Creator

Hello.
I am trying to access EJBs deployed on JBOSS in order to develop a web app client, when I import the EJB set from Creator (sessions and entities packages in a jar file) I got the following error message....."No EJB set found in file....." .
I presume there is an kind of xml file description specific for Sun App Server missing. I would like to know if there is other way to expose EJB in creator?....maybe write a config file by hand.
I already read the tutorials related to EJB but those only use pre build EJB jars for Sun App Sserver.
Also I read all the posted about JBoos and EJB in this forum but those are pretty general.
By the way I have Delegate classes to access the EJB. How do I register my delegates in Creator in order to expose their methods?
I�ll really appreciate some light in this matter.
Thanks in advance!!!

Hi,
The below forum thread may help you :
http://swforum.sun.com/jive/thread.jspa?forumID=123&threadID=51321
Thanks,
Runa.

NPE occurs when deploying suitecase dependent on WSIF / EJB

I am getting a NullPointerException when deploying a BPEL process that depends on an EJB accessed via a WSIF definition. Both the ejb and the suitcase are deployed onto the same oc4j instance, and i have tested the ejb from a standalone client to ensure that it is operational, but i get the exception noted below. I can only assume that there may be something wrong with the WSIF definition, but I have checked it numerous times to make sure that it accurately reflects the ejb definition. Can you give me some hints as to some things to check that could possibly cause this error? From the stack trace, it seems that it is ejb related, but i guess i could be wrong:
<2006-04-11 11:20:28,088> <ERROR> <default.collaxa.cube.engine.deployment> <Cube
ProcessFactory::generateProcessClass>
Process "XYZ" (revision "1.01.000.0000") compilation failed.
<2006-04-11 11:20:28,182> <ERROR> <default.collaxa.cube.engine.deployment> <Cube
ProcessLoader::create>
<2006-04-11 11:20:28,182> <ERROR> <default.collaxa.cube.engine.deployment> Proce
ss "XYZ" (revision "1.01.000.0000") load FAILED!!
com.evermind.server.rmi.OrionRemoteException: java.lang.NullPointerException
at com.evermind.server.ejb.EJBUtils.getUserException(EJBUtils.java:296)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2174)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Nested exception is:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:398)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.addStatus(CubePr
ocessHolder.java:275)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcess
Holder.java:1240)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(Cube
ProcessHolder.java:882)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadArchive(Cube
ProcessHolder.java:824)
at com.collaxa.cube.engine.CubeEngine.loadProcessArchive(CubeEngine.java
:939)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.loadProcessArchive(BP
ELDomainManagerBean.java:390)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2157)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
<2006-04-11 11:20:28,182> <ERROR> <default.collaxa.cube.engine.deployment> <Cube
ProcessMonitorWork::run> Error while loading process archive C:\OraBpelPM\integr
ation\orabpel\domains\default\deploy\bpel_XYZ_1.01.000.0000.jar
com.evermind.server.rmi.OrionRemoteException: java.lang.NullPointerException
at com.evermind.server.ejb.EJBUtils.getUserException(EJBUtils.java:296)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2174)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)
Nested exception is:
java.lang.NullPointerException
at java.util.Hashtable.put(Hashtable.java:398)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.addStatus(CubePr
ocessHolder.java:275)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.bind(CubeProcess
Holder.java:1240)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadAndBind(Cube
ProcessHolder.java:882)
at com.collaxa.cube.engine.deployment.CubeProcessHolder.loadArchive(Cube
ProcessHolder.java:824)
at com.collaxa.cube.engine.CubeEngine.loadProcessArchive(CubeEngine.java
:939)
at com.collaxa.cube.ejb.impl.BPELDomainManagerBean.loadProcessArchive(BP
ELDomainManagerBean.java:390)
at IBPELDomainManagerBean_StatelessSessionBeanWrapper34.loadProcessArchi
ve(IBPELDomainManagerBean_StatelessSessionBeanWrapper34.java:2157)
at com.collaxa.cube.engine.deployment.CubeProcessMonitorWork.run(CubePro
cessMonitorWork.java:130)
at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
at java.lang.Thread.run(Thread.java:534)

Note, that this has nothing to do with WSIF.. and is a cmpilation error ...
my best guess is the revision number..
Process "XYZ" (revision "1.01.000.0000") load FAILED!! can you change that to reflect a norma double or in (1, 1.1, 2.0...)
thx clemens

WebLogic 12.1.2 fails when deploying ear with injecting extension and bean with injection of this extension in ejb

WebLogic 12.1.2 fails when deploying an enterprise application(ear) that contains a ejb in which injected 1) an extension 2)bean with injection of this extension.
The following exception is thrown:
Caused By: org.jboss.weld.exceptions.DeploymentException: WELD-001409 Ambiguous dependencies for type [CdiExtension] with qualifiers [@Default] at injection point [[field] @Inject private test.extension.Bean1.extension].
Possible dependencies [
[Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@1115deb],
Extension [class test.extension.CdiExtension] with qualifiers [@Default]; zip:/domain1/servers/AdminServer/tmp/_WL_user/test/7x6roh/lib/test-extension-0.0.1-SNAPSHOT.jar!/META-INF/services/javax.enterprise.inject.spi.Extension@1[test.extension.CdiExtension@ed791f]]]
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:314)
    at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:280)
    at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:143)
    at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
    at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:382)
    at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:367)
    at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379)
    at com.oracle.injection.provider.weld.WeldInjectionContainer.start(WeldInjectionContainer.java:106)
    at com.oracle.injection.integration.CDIAppDeploymentExtension.initCdi(CDIAppDeploymentExtension.java:70)
    at com.oracle.injection.integration.CDIAppDeploymentExtension.activate(CDIAppDeploymentExtension.java:47)
    at weblogic.application.internal.flow.AppDeploymentExtensionFlow.activate(AppDeploymentExtensionFlow.java:37)
    at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
    at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
    at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)
    at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
    at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
Problem can be easily reproduced by a minimal case:
test.ear:
\lib\test-extension-0.0.1-SNAPSHOT.jar
test-ejb-0.0.1-SNAPSHOT.jar
where
test-extension-0.0.1-SNAPSHOT.jar contains:
CdiExtension.java:
package test.extension;
import javax.enterprise.inject.spi.Extension;
public class CdiExtension implements Extension {
    private String someString = "Some String";
    public String getSomeString() {
        return someString;
Bean1.java:
package test.extension;
import javax.enterprise.context.ApplicationScoped;
import javax.inject.Inject;
@ApplicationScoped
public class Bean1 {
    @Inject
    private CdiExtension extension;
    public String get() {
        return extension.getSomeString();
test-ejb-0.0.1-SNAPSHOT.jar contains:
EjbBean.java:
package test;
import test.extension.Bean1;
import test.extension.CdiExtension;
import javax.ejb.Stateless;
import javax.inject.Inject;
@Stateless
public class EjbBean {
    @Inject
    private CdiExtension extension;
    @Inject
    private Bean1 bean1;
    public String getSomeString() {
        return extension.getSomeString() + "\n" + bean1.get();
p.s. i seen same problem in community.oracle.com/thread/2577403 , but it happen in "war", not "ear", and seems successfully patched with patch №17424706

Hi,
It looks like there is patch exists for this issue.
Patch 17198187
Please try to download from the MOS or try to open a ticket with support.
Regards,
Kal

Ejb-ref errore when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

The issue is that WLS 6.1 didn't really support ejb-links properly. An
ejb-link should allow you to link a webapp or an ejb to another EJB
without requiring additional information or a global JNDI name on the
target EJB.
WLS 8.1 is following your ejb-link and telling you there's not enough
information.
You have 2 options:
1) Remove the <ejb-link>...</ejb-link> from your web.xml. You'll be
using just an ejb-reference at that point, but you've already included
the necessary information in the weblogic.xml that we can locate the EJB
via its global jndi-name
or
2) Change the ejb-link to be
<ejb-link>CustomMessaginBrick.jar#CustomMessagingBrick</ejb-link>
If you wanted to, you could then remove the reference info from the
weblogic.xml
-- Rob
luca wrote:
when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
Thanks in advance!
Greets,
Luca
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

Unable to deploy EJB 3.0 on JBoss 4.0.4GA - no home interface

I am stuck in that my EJB3.0 project (one entity bean, one session bean and one client test bean) builds OK but somehow Eclipse Europa is unable to deploy it to JBoss (4.0.4 GA and 5 Beta) -- something to do with JNDI error as it involves javax.naming exceptions.
My Eclipse directory structure is :-
Titan (project name)
|
ejb - com.titan (package name)
| |
| domain -> Cabin.java (my entity bean)
| |
| travelagent -> TravelAgentBean.java
| -> TravelAgentRemote.java
|
META_INF -> ejb-jar.xml
-> MANIFEST.MF
-> persistence.xml
My ejb-jar.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar id="ejb-jar_ID" version="2.1" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd">
<display-name>Titan</display-name>
<enterprise-beans>

<session >
<display-name>TravelAgentBean</display-name>
<ejb-name>com/titan/travelagent/ejb/TravelAgentBean</ejb-name>
<remote>com.titan.travelagent.ejb.TravelAgentRemote</remote>
<ejb-class>com.titan.travelagent.ejb.TravelAgentBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
</ejb-jar>
And my persistence.xml is :
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd">
<persistence-unit name="Titan">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<class>com.titan.domain.Cabin</class>
<properties>
<property name="hibernate.connection.driver_class" value="oracle.jdbc.OracleDriver" />
<property name="hibernate.connection.url"
value="jdbc:oracle:thin:@localhost:1521:XE" />
<property name="hibernate.connection.username" value="SYSTEM" />
<property name="hibernate.connection.password" value="Swordfish1" />
</properties>
</persistence-unit>
</persistence>
I right-click on the Titan project name and choose Build Project. I get the following error message :-
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.2
Warning: A Session bean must implement, directly or indirectly, the javax.ejb.SessionBean interface.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.3
Warning: A Session bean must define at least one ejbCreate method.
13:01:06,046 WARN [verifier] EJB spec violation:
Bean : com/titan/travelagent/TravelAgentBean
Section: 7.11.1
Warning: The session bean must implement either a remote home and remote, or a local home and a local interface or a service endpoint interface.
13:01:06,062 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.0.4.GA/server/default/deploy/Titan.jar
I don't understand, because as of EJB 3.0, you don't really need a home or local-home interface anymore...

Using @SecurityDomain("exemplo1") in my EJB and NOT providing jboss.xml, it works.
@SecurityDomain("exemplo1")
@RolesAllowed("yyy")
@Stateless(name="UserManagement")
public class UserManagementBean implements UserManagement {
public void add(User user) {
}Damn! This is some serious shit... I don�t want to configure this in every single EJB.
EJB 3.0 is nice, but some small trivial details like this and others, that was forgotten by Sun, piss me off!

Ejb-ref error when deploying a previously working ear on weblogic 8.1

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

when deploying an ear module on weblogic 8.1 i get the following error:
The ejb-link 'CustomessagingBrick.jar/CustomMessaginBrick' declared in ejb-ref
or ejb-local-ref 'ejb/Service2' in the application module 'cmbrick.war' could
not be resolved. The target EJB for the ejb ref could not be found.
The ear is composed of two sub-modules:
CustomMessaginBrick.jar
cmbrick.war.
The same ear was deployed on weblogic 6.1.
Every reference in the ear seems in the right place so i am really clueless.
Hereafter i include the relevant portions of the deployment descriptors.
the web.xml for cmbrick.war contains the following data:
<ejb-local-ref>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocalHome</local-home>
<local>com.hutchison3g.core.brick.custom.messaging.CustomMessagingBrickLocal</local>
<ejb-link>CustomMessagingBrick</ejb-link>
</ejb-local-ref>
its weblogic.xml file is the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"
"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd">
<weblogic-web-app>
<reference-descriptor>
<ejb-reference-description>
<ejb-ref-name>ejb/Service2</ejb-ref-name>
<jndi-name>Service2</jndi-name>
</ejb-reference-description>
</reference-descriptor>
</weblogic-web-app>
while the weblogic-ejb-jar for CustomMessaging bricks contains the following:
<weblogic-enterprise-bean>
<ejb-name>CustomMessagingBrick</ejb-name>
<stateless-session-descriptor>
<pool>
</pool>
<stateless-clustering>
</stateless-clustering>
</stateless-session-descriptor>
<transaction-descriptor>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>Service2</jndi-name>
</weblogic-enterprise-bean>....

Change PowerPivot data source when deploying from Dev - Staging - Production

We have PowerPivot workbooks we store in SharePoint 2013 Libraries.
We have a powershell script which automates the deployment of sites and pages. Is there a way using PowerShell (or any scripting language really) to look into the workbook and change the PowerPivot data source when deployment from one environment to
another? (Dev -> Stage -> Prod) We need to update the workbooks to point to our SSAS cubes Dev -> Stage -> Prod respectively.
Thank you for any expert advice you may offer,
Sincerely,
-Craig

Basically, it's an excel file (XLSX) file and you can use excel OM for this.
A simple program (in C# or any language of your choice) can be written to do the following and achieve what you need.
using XLS = Microsoft.Office.Interop.Excel;
string info = null;
XLS.Application application = null;
try
application = new XLS.Application();
var book = application.Workbooks.Open(filepath);
foreach (XLS.WorkbookConnection wc in book.Connections)
  switch (wc.Type)
   case XLS.XlConnectionType.xlConnectionTypeOLEDB:
    info = wc.Name + " " + wc.OLEDBConnection.Connection.ToString() + "\r\n";
    break;
book.Close();
finally
if (application != null)
  application.Quit();
Hopefully, this was helpful.

Changes in EJB when deployed in JBoss

Similar Messages

Maybe you are looking for