Kodo-service.xml vs kodo.properties

I'm deploying under JBoss using JCA.
I changed all my code to be 1.0 compliant. However my
persistenceFactory.setNonTransactionalRead is now throwing a
JDOUserException
->configuration is frozen.
I see that it is a property now in kodo.properties. Do I somehow use
kodo.properties in conjunction with kodo-service.xml ?

Similar Messages

Kodo-service.xml template

Hi, I am running JBoss 4.0.3RC1 and Kodo 3.3.1 and the kodo-services.xml
file that comes with the kodo installation doesn't seem to work. I have
changed the properties as indicated in the documentation. Can someone
give me a kodo-services.xml file that works with the latest JBoss please?.
Here's the stack trace:
16:16:08,687 ERROR [MainDeployer] Could not create deployment:
file:/C:/Program
Files/jboss-4.0.3RC1/server/default/deploy/kodo-service.xml
org.jboss.deployment.DeploymentException: No ClassLoaders found for:
org.jboss.r
esource.connectionmanager.LocalTxConnectionManager; - nested throwable:
(java.la
ng.ClassNotFoundException: No ClassLoaders found for:
org.jboss.resource.connect
ionmanager.LocalTxConnectionManager)
at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
:141)
at
org.jboss.system.ServiceController.install(ServiceController.java:202
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:220)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:919)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:773)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy6.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:325)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:501)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:204)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:277)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:267)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:217)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:950)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:436)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:973)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:774)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:721)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
at org.jboss.Main.boot(Main.java:195)
at org.jboss.Main$1.run(Main.java:463)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jbos
s.resource.connectionmanager.LocalTxConnectionManager
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:292)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
assLoader.java:475)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
oader.java:377)
at java.lang.ClassLoader.loadClass(Unknown Source)
at
org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
1189)
at
org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
271)
at
org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:
329)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:124)
at
org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
tor.java:151)
at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
:116)
... 81 more

Never mind I fiigured it ou.
"Eduardo" <[email protected]> wrote in message
news:[email protected]...
>
Hi, I am running JBoss 4.0.3RC1 and Kodo 3.3.1 and the kodo-services.xml
file that comes with the kodo installation doesn't seem to work. I have
changed the properties as indicated in the documentation. Can someone
give me a kodo-services.xml file that works with the latest JBoss please?.
Here's the stack trace:
16:16:08,687 ERROR [MainDeployer] Could not create deployment:
file:/C:/Program
Files/jboss-4.0.3RC1/server/default/deploy/kodo-service.xml
org.jboss.deployment.DeploymentException: No ClassLoaders found for:
org.jboss.r
esource.connectionmanager.LocalTxConnectionManager; - nested throwable:
(java.la
ng.ClassNotFoundException: No ClassLoaders found for:
org.jboss.resource.connect
ionmanager.LocalTxConnectionManager)
at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
:141)
at
org.jboss.system.ServiceController.install(ServiceController.java:202
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.install(Unknown Source)
at org.jboss.deployment.SARDeployer.create(SARDeployer.java:220)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:919)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:773)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy6.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:325)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:501)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:204)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:277)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:267)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:217)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:950)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:436)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:973)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:774)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:721)
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.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
er.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
or.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
BeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:434)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:315)
at org.jboss.Main.boot(Main.java:195)
at org.jboss.Main$1.run(Main.java:463)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for:
org.jbos
s.resource.connectionmanager.LocalTxConnectionManager
at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:292)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryCl
assLoader.java:475)
at
org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassL
oader.java:377)
at java.lang.ClassLoader.loadClass(Unknown Source)
at
org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
1189)
at
org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:
271)
at
org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:
329)
at org.jboss.system.ServiceCreator.install(ServiceCreator.java:124)
at
org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
tor.java:151)
at
org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
:116)
... 81 more

Jboss kodo-service.xml deploy problem

Hi,
I'm trying to deploy kodo-service.xml in jboss-3.0.0RC1 and get this error:
2002-06-11 13:48:06,030 ERROR [org.jboss.deployment.MainDeployer] could
not start deployment
:file:/D:/jbossrc1/server/default/deploy/kodo-service.xml
java.lang.AbstractMethodError
at
com.solarmetric.kodo.impl.jdbc.JDBCPersistenceManagerFactory.<init>(JDBCPersistenceManagerFactory.java:153)
at
com.solarmetric.kodo.impl.jdbc.ee.EEPersistenceManagerFactory.<init>(EEPersistenceManagerFactory.java:53)
at
com.solarmetric.kodo.impl.jdbc.ee.JDOConnectionFactory.<init>(JDOConnectionFactory.java:41)
I get the same error using the default kodo-service.xml file included with
the downloaded package.
Any ideas?
Thanks!
Jesper

Note that neither Kodo JDO 2.3.0 beta nor Kodo JDO 2.2.5 does not exhibit
the 1.4 problem.
-Patrick
On 6/11/02 8:07 AM, "Jesper Ladegaard" <[email protected]> wrote:
Okay,
I can see from some other post it\'s a Java 1.4 problem.
/Jesper
Patrick Linskey [email protected]
SolarMetric Inc. http://www.solarmetric.com

Kodo-ds.xml: how to use for two database in same app server?

hi,
i meet a problem: i have two applications in the same app server(one app
use one database.). BUT, only one kodo-ds.xml can configure the
PersistenceManagerFactory with jndi name. When i figure the two jidi name
for two "<tx-connection-factoy>" in the root element
"<connection-factories>" in the kodo.ds.xml. That's unavailable!
eg:
<connection-factories>
<tx-connection-factoy>

</tx-connection-factoy>
<tx-connection-factoy>

</tx-connection-factoy>
</connection-factories>
THAT'S MY CONFIGURATION. UNAVALIABLE NOW.... Who can help me solve this
problem?
thx!

You should deploy multiple kodo-ds.xml files (i.e. kodo-ds-oracle.xml).
Kidwish wrote:
hi,
i meet a problem: i have two applications in the same app server(one app
use one database.). BUT, only one kodo-ds.xml can configure the
PersistenceManagerFactory with jndi name. When i figure the two jidi name
for two "<tx-connection-factoy>" in the root element
"<connection-factories>" in the kodo.ds.xml. That's unavailable!
eg:
<connection-factories>
<tx-connection-factoy>

</tx-connection-factoy>
<tx-connection-factoy>

</tx-connection-factoy>
</connection-factories>
THAT'S MY CONFIGURATION. UNAVALIABLE NOW.... Who can help me solve this
problem?
thx!
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Creation of InitialContext fails when i hot-deploy scheduler-service.xml

Creation of InitialContext fails when i hot-deploy scheduler-service.xml
I configured scheduler-service as follows in Jboss 3.2:
scheduler-service.xml
<mbean code="org.jboss.varia.scheduler.Scheduler"
     name=":service=Scheduler">
<attribute name="StartAtStartup">true</attribute>
<attribute name="SchedulableClass">com.beta.my.utils.FMScheduler</attribute>
<attribute name="SchedulableArguments">Schedulabe Test,12345</attribute>
<attribute name="SchedulableArgumentTypes">java.lang.String,int</attribute>
<attribute name="InitialStartDate">0</attribute>
<attribute name="SchedulePeriod">10000</attribute>
<attribute name="InitialRepetitions">-1</attribute>
</mbean>
Schedulable Class
package com.beta.my.utils;
import java.util.Date;
import org.jboss.varia.scheduler.Schedulable;
public static class FMScheduler
implements Schedulable
private String mName;
private int mValue;
public FMScheduler(String pName,int pValue)
mName = pName;
mValue = pValue;
public void perform(Date pTimeOfCall,long pRemainingRepetitions)
try {
          Context context = new InitialContext();//properties taken from jndi.properties file
          } catch (Exception e){
               e.printStackTrace();
I started my jboss..,FMScheduler created successfully, perform method in FMScheduler called succesfully after SchedulePeriod(1000)
The problem occurs(NullPointerException) while i changed SchedulePeriod time and hot-deployed(just saved scheduler-service.xml).
The following Exception occures due to InitialContext creation fails*(Context context = new InitialContext();)* in FMScheduler.
17:46:27,361 ERROR [STDERR] java.lang.NullPointerException
17:46:27,361 ERROR [STDERR] at org.jboss.mx.loading.UnifiedClassLoader.findR
esources(UnifiedClassLoader.java:374)
17:46:27,361 ERROR [STDERR] at java.lang.ClassLoader.getResources(ClassLoade
r.java:825)
17:46:27,361 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12$5.run
(VersionHelper12.java:145)
17:46:27,361 ERROR [STDERR] at java.security.AccessController.doPrivileged(N
ative Method)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.VersionHelper12.getRe
sources(VersionHelper12.java:142)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getAp
plicationResources(ResourceManager.java:468)
17:46:27,377 ERROR [STDERR] at com.sun.naming.internal.ResourceManager.getIn
itialEnvironment(ResourceManager.java:159)
17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.init(InitialConte
xt.java:215)
17:46:27,377 ERROR [STDERR] at javax.naming.InitialContext.<init>(InitialCon
text.java:195)
17:46:27,377 ERROR [STDERR] at com.beta.my.utils.FMScheduler.perform
(FMScheduler.java:42)
17:46:27,392 ERROR [STDERR] at org.jboss.varia.scheduler.Scheduler$Listener.
handleNotification(Scheduler.java:1263)
17:46:27,392 ERROR [STDERR] at org.jboss.mx.server.NotificationListenerProxy
.handleNotification(NotificationListenerProxy.java:69)
17:46:27,392 ERROR [STDERR] at javax.management.NotificationBroadcasterSuppo
rt.sendNotification(NotificationBroadcasterSupport.java:95)
17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.sendNotification
s(Timer.java:441)
17:46:27,392 ERROR [STDERR] at javax.management.timer.Timer.access$000(Timer
.java:31)
17:46:27,408 ERROR [STDERR] at javax.management.timer.Timer$RegisteredNotifi
cation.doRun(Timer.java:612)
17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.SchedulableRunnable.run(Sch
edulableRunnable.java:164)
17:46:27,408 ERROR [STDERR] at org.jboss.mx.util.ThreadPool$Worker.run(Threa
dPool.java:225)
please help me if u have any idea,thanks

Hi Hamsa,
Did you also create and configure an "Execution Destination"?
You can test the Metadata destination configuration on Web Service Navigator.
On the web service navigator (http://hostname:portnumber/wsnavigator) search in the metatda destination you have created for the service you imported in web dynpro as a model. If you can find it there test it on the ws navigator.
Best regards,
Yasar

How to generate param-prefix in web-services.xml

Hello I am using source2wsdd to generate my WSDL and my web-services.xml. For sake
of interoperability I would like to have the type param-prefix in the web-services.xml
file. From my Bean class what kind of javadoc comments would help me generate
the type param-prefix ?
I also would like the location="header" in the param list.
Thanks,
Aswin.
<param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:SOAPCredentials"
location="header"
class-name="com.xyz.webservices.SOAPCredentials"
name="SOAPCredentials"
style="in">
</param>
<return-param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:GetFileProfileInformationResponse"
class-name="com.xyz.webservices.GetFileProfileInformationResponse"
name="parameters">
</return-param>
</params>

Please try this:
* @wlws:part p_SOAPAuthToken location="header"
* type="typeNS:p_SOAPAuthToken"
* class-name="com.xyz.webservices.SOAPAuthToken"
* style="inout"
* xmlns:typeNS=http://namespace/of/the/type
* @wlws:part p_SOAPCredentials location="header"
* type="typeNS:p_SOAPCredentials"
* class-name="com.xyz.webservices.SOAPCredentials"
* style="in"
* xmlns:typeNS=http://namespace/of/the/type
* @ejbgen:remote-method
public void login(SOAPAuthToken p_SOAPAuthToken,
SOAPCredentials p_SOAPCredentials)
I did not try this one out. So i can only hope that it works.
Regards,
-manoj
http://manojc.com
"Aswin Dinakar" <[email protected]> wrote in message
news:40aeeb5d$1@mktnews1...
>
I tried this
* @wlws:part p_SOAPAuthToken location="header"
* @wlws:part p_SOAPAuthToken type="param-prefix:p_SOAPAuthToken"
* @wlws:part p_SOAPAuthTokenclass-name="com.xyz.webservices.SOAPAuthToken"
* @wlws:part p_SOAPAuthToken style="inout"
* @wlws:part p_SOAPCredentials location="header"
* @wlws:part p_SOAPCredentials type="param-prefix:p_SOAPCredentials"
* @wlws:part p_SOAPCredentialsclass-name="com.xyz.webservices.SOAPCredentials"
* @wlws:part p_SOAPCredentials style="in"
* @ejbgen:remote-method
public void login(SOAPAuthToken p_SOAPAuthToken,
SOAPCredentials p_SOAPCredentials)
and I got the following error -
[source2wsdd] source2wsdd: In doclet classweblogic.webservice.tools.ddgen.Servi
ceGen, method start has thrown an exceptionjava.lang.reflect.InvocationTargetE
xception
[source2wsdd] weblogic.xml.stream.XMLStreamException: Attribute QNamevalue "par
am-prefix:p_SOAPAuthToken" does not map to a prefix that is in scope
[source2wsdd] atweblogic.webservice.dd.NSAttribute.getValueAsXMLName(NSAttrib
ute.java:45)
[source2wsdd] atweblogic.webservice.dd.DDLoader.processParamElement(DDLoader.
java:1252)
"manoj cheenath" <[email protected]> wrote:
Check out this example:
http://manojc.com/?sample3
You can find more details regarding the tags here:
http://manojc.com/tutorial/sample3/source2wsdd.html
Regards,
-manoj
http://manojc.com
"Aswin D" <[email protected]> wrote in message
news:[email protected]...
Hello I am using source2wsdd to generate my WSDL and my
web-services.xml.
For sake
of interoperability I would like to have the type param-prefix inthe
web-services.xml
file. From my Bean class what kind of javadoc comments would help megenerate
the type param-prefix ?
I also would like the location="header" in the param list.
Thanks,
Aswin.
<param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:SOAPCredentials"
location="header"
class-name="com.xyz.webservices.SOAPCredentials"
name="SOAPCredentials"
style="in">
</param>
<return-param xmlns:param-prefix="http://tempuri.org/"
type="param-prefix:GetFileProfileInformationResponse"
class-name="com.xyz.webservices.GetFileProfileInformationResponse"
name="parameters">
</return-param>
</params>

How to set buildID.xml and custom.properties in SDK

Hello,
I just completed a new build deployment of SAP ME5.2, because after I deployed the new version, I don't think I have set a
correct version number.Can you someone give me a sample how to set the buildID.xml and custom.properties? I am a new on the SAP ME5.2
The Base version is ME_Base_5.2.5.16.5_netweaver-71_Update.zip and
MEClient_Base_5.2.5.16.5_netweaver-71_Update.zip. the HB customzation
version is ME_xxxxxx_2.0.0.0.x_netweaver-71.
Within the sap note 1484551, you mentioned we need change the
SDKInstallDir/build/buildID.xml file, here is the context of the file:
buildID.xml -
<?xml version="1.0" encoding="UTF-8"?>
<buildID xmlns:xs="http://www.w3.org/2001/XMLSchema">
<customer>XXXXXX</customer>
<revision>1.0.0.0</revision>
<build>1</build>
</buildID>
buildID.xml -
1. how can we change the revision and build?
There is another file BuildToolDir/build/script/custom.properties, here
is the file context:
custom.properties----
This file contains build properties used to configure the build
system.
The name of the software vendor implementing the customizations.
vendor.name=xxxxxxxxx
Vendor build identifier. This value is used to uniquely identify
customizations built by a particular vendor for a particular customer
and base
application version.
This is also used in path locations and in naming certain build
artifacts, like the custom EJB module and the utility classes archive.
vendor.id=xxxxxxxxx
The installation of the J2EE engine installed in the development
environment.
ex. C:/usr/sap/CE1\J00
j2ee.instance.dir=J2EEInstanceDir
The web context path used to access the main web application. This
is used by the build to set the
context-root value in application.xml after an update has been
imported.
web.context.path=
The web context path used to access the production XML interface web
application. This is used by the build to set the
context-root value in application.xml after an update has been
imported.
xml.context.path=
The web context path to access resources from the web extension
application, like images and work instruction HTML files.
web-ext.context.path=web-ext
The target database vendor. Valid values are 'oracle' or 'sqlserver'.db.vendor=ORACLE
The JDBC driver configured for the application server.
db.drivername=VMJDBC
JDBC connection propertes for the WIP (Work In Process) database.
This is the primary application database.
db.wip.driverclassname=
db.wip.driver.url=
db.wip.host=
db.wip.port=
db.wip.sid=
db.wip.user=
db.wip.password=
JDBC connection propertes for the ODS (Open Data Store) database.
This is the offline reporting and archiving database.
db.ods.driverclassname=
db.ods.driver.url=
db.ods.host=
db.ods.port=
db.ods.sid=
db.ods.user=
db.ods.password=
Flag indicating whether to add DPMO NC codes to NC idat files when a
new update is imported. This value is initially
set by the installer according the the user selection.
dpmo.nc.codes=
The default locale used by the production system. The default locale
is the locale used to display locale
specific text and messages when the requested locale is not
available. This property does not need to
be set if the default locale is english.
default.locale=en
Used when running the build from Eclipse to locate the java compiler
used by the WebLogic EJB compiler.
jdk.home=C:/Program Files/Java/jdk1.5.0_20
Compiler debug mode. If set to 'true', debug symbols will be
compiled into the byte code.
compile.debug=true
Keystore alias
security.alias=xxxxx
Keystore password
security.storepass=ChangeIt
Key password
security.keypass=ChangeIt
Keystore type (jks=default,jceks,pkcs12)
security.storetype=jks
Optional source control build identifier that is to be displayed with
standard version information.
scs.build.ID=
Optional extended version information to be displayed with standard
version information.
ext.info=
custom.properties----
2. How can we change this here?
Regards,
Leon Lu
Edited by: Leon Lu on Aug 4, 2011 11:14 AM
Edited by: Leon Lu on Aug 4, 2011 11:21 AM

Hi,
I created one request with logo in the header an page in the footer etc. and called StyleSheet. After you can import this formats by each request.
You can do this in compound layout.
Regards,
Stefan

Fault elt in web-services.xml NOT WORKING

We are trying to capture an invalid message coming into our service before our
service actually processes it. Per WLS7 documentation, it provides the ability
to add a <fault> elt under the <params> elt in web-services.xml to perform that.
Here's how the operations portion of our web-services.xml looks like:
<operations>
<operation method="echo(java.lang.String)" component="jcComp0" name="echo"
handler-chain="diagnosticChain">
<params>
<param location="body" class-name="java.lang.String" style="in" name="echoString"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</param>
<return-param location="body" class-name="java.lang.String" name="Result"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</return-param>
<fault name="InvalidMessageException" class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
</params>
</operation>
</operations>
However, when we tried doing that, we got a BIG set of exception while trying
to build our client. It looks as follows:
client:
[clientgen] Generating client jar for diagnostic.ear ...
[clientgen] Could not read Web Service deployment descriptor
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:112)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] Could not read Web Service deployment descriptor
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:332)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] weblogic.webservice.dd.DDProcessingException: Could not find required
attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] at weblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java:287)
[clientgen] at weblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
[clientgen] at weblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
[clientgen] at weblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
[clientgen] at weblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
[clientgen] at weblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
[clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
[clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --------------- nested within: ------------------
[clientgen] weblogic.webservice.util.WebServiceJarException: Could not load deployment
descriptor - with nested exception:
[clientgen] [weblogic.webservice.dd.DDProcessingException: Could not find required
attribute "type" for element <fault> (Line 28, Column 8)]
[clientgen] at weblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EARClientGen.java:330)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.java:110)
[clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
BUILD FAILED
Anybody has any ideas?
Thanks much,
sami

Manoj,
Thanks a lot, THAT DID IT... two very helpful hints from you in a row.
By the way, one thing worth mentioning is that the Weblogic documentation that
we explored did not have enough information about that issue.
Thanks again.
sami
"manoj cheenath" <[email protected]> wrote:
Buried deep in the stack trace, is this little
detail:
Could not find required
attribute "type" for element <fault> (Line 28, Column 8)
So the correct DD should look something like:
<fault type="typeNS:string"
xmlns:typeNS="http://www.w3.org/2001/XMLSchema"
class-name="tutorial.sample9.HelloWorldException"
name="HelloWorldException">
</fault>
Also, check out this example:
http://manojc.com/?sample9
There is a know problem: WLS can not handle
exceptions that contain complex data types.
This will be fixed in SP1.
Regards,
-manoj
http://manojc.com
"sami titi" <[email protected]> wrote in message
news:[email protected]...
We are trying to capture an invalid message coming into our servicebefore
our
service actually processes it. Per WLS7 documentation, it providesthe
ability
to add a <fault> elt under the <params> elt in web-services.xml toperform
that.
Here's how the operations portion of our web-services.xml looks like:
<operations>
<operation method="echo(java.lang.String)" component="jcComp0"name="echo"
handler-chain="diagnosticChain">
<params>
<param location="body" class-name="java.lang.String" style="in"name="echoString"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</param>
<return-param location="body" class-name="java.lang.String"name="Result"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" type="xsd:string">
</return-param>
<fault name="InvalidMessageException"class-name="com.gmacfs.routeone.diagnostic.InvalidMessageException"/>
</params>
</operation>
</operations>
However, when we tried doing that, we got a BIG set of exception whiletrying
to build our client. It looks as follows:
client:
[clientgen] Generating client jar for diagnostic.ear ...
[clientgen] Could not read Web Service deployment descriptor
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:112)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] Could not read Web Service deployment descriptor
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:332)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --- Nested Exception ---
[clientgen] weblogic.webservice.dd.DDProcessingException: Could notfind
required
attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] atweblogic.webservice.dd.ParsingHelper.getRequiredAttribute(ParsingHelper.java
:287)
[clientgen] atweblogic.webservice.dd.DDLoader.processFaultElement(DDLoader.java:1195)
[clientgen] atweblogic.webservice.dd.DDLoader.processFaultElements(DDLoader.java:1166)
[clientgen] atweblogic.webservice.dd.DDLoader.processParamsElement(DDLoader.java:1004)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationElement(DDLoader.java:977)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationElements(DDLoader.java:853)
[clientgen] atweblogic.webservice.dd.DDLoader.processOperationsElement(DDLoader.java:841)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElement(DDLoader.java:378)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServiceElements(DDLoader.java:283)
[clientgen] atweblogic.webservice.dd.DDLoader.processWebServicesElement(DDLoader.java:271)
[clientgen] at weblogic.webservice.dd.DDLoader.load(DDLoader.java:249)
[clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:79
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:330)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
[clientgen] --------------- nested within: ------------------
[clientgen] weblogic.webservice.util.WebServiceJarException: Couldnot
load deployment
descriptor - with nested exception:
[clientgen] [weblogic.webservice.dd.DDProcessingException: Could not
find>required>> attribute "type" for element <fault> (Line 28, Column 8)
[clientgen] atweblogic.webservice.util.WebServiceWarFile.getWSDD(WebServiceWarFile.java:81
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.getWebServiceDD(EAR
ClientGen.java:330)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.EARClientGen.run(EARClientGen.ja
va:110)
[clientgen] atweblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenT
ask.java:270)
[clientgen] at org.apache.tools.ant.Task.perform(Task.java:217)
[clientgen] at org.apache.tools.ant.Target.execute(Target.java:164)
[clientgen] atorg.apache.tools.ant.Target.performTasks(Target.java:182)
[clientgen] atorg.apache.tools.ant.Project.executeTarget(Project.java:601)
[clientgen] atorg.apache.tools.ant.Project.executeTargets(Project.java:560)
[clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:454)
[clientgen] at org.apache.tools.ant.Main.start(Main.java:153)
[clientgen] at org.apache.tools.ant.Main.main(Main.java:176)
BUILD FAILED
Anybody has any ideas?
Thanks much,
sami

Error while inluding xsd:whiteSpace in web-services.xml

Hi,
i am trying to allow the xml attribute values to preserve the whiteSpace characters(tabs, line feeds, carriage returns etc...)
In web-services.xml i am adding
<xsd:complexContent>
<xsd:restriction base="xsd:string">
<xsd:attribute name="address">
<xsd:whiteSpace value="preserve"/>
</xsd:attribute>
</xsd:restriction>
</xsd:complexContent>
But i am getting a run time exception as
[weblogic.xml.schema.model.parser.XSDParseException: invalid element "xsd:whiteSpace" AT line 0, column 0: <['http://www.w3.org/2001/XMLSchema']:xsd:whiteSpace value="preserve">]
am i doing in a correct way?
Please suggest me.
Thanks
subba.

weblogic server doesn't support some of the xsd features.
WebLogic Server does not support the following XML Schema features:
?     Complex data type inheritance by restriction
?     Union simple data types
?     References to named model groups
?     Nested content models in a single complex type
?     Redefinition of declarations
?     Identity constraints (key, keyref, unique)
?     Nested XSD model groups with other content models at the same level.
There cannot be a modelgroup (say sequence) that contains another nested modelgroup (say choice), and a content element (say element). So, if a nested modelgroup is required, make sure that it contains only another model group and no other content element.
?     Wildcards
but i didn't understand why its giving error for whiteSpace.
Can someone reply to this please,, its urgent for me.
thanks
subba.

Generate web-service.xml

I need to configure the deployment descriptor web-services.xml, but I don't know where or how to generate it. I use version 8.1 of weblogic. Someone can help me? thanks!

I have an XML input in my transaction. I was able to generate the WSDL without problems. But need to know how to test it by sendig in some XML data. Probably, we could both be helping each other in the process.
Regards,
Chanti.

What web service & xml will be used for deleting the packged epub/pdf file from Admin Console

What web service & xml will be used for deleting the packged epub/pdf file from Admin Console?
I am able to delete the files from Admin console directy but not able to get which web service is calling on deleting the file from admin console:
Mangal

Hi Jim,
I tired following web service and xml to delete the packaged ebook but it is giving me error instead of response:
Web Service & XML
http://myserver_url/admin/ManageResourceKey
<request action="delete" auth="builtin" xmlns="http://ns.adobe.com/adept">
<nonce>" . $nonce . "</nonce>
<expiration>'. $expiration .'</expiration>
<resourceKey>
<resource>resource_id</resource>
<resourceItem>1</resourceItem>
</resourceKey>
</request>
Error Message
<error xmlns="http://ns.adobe.com/adept"
data="E_ADEPT_DATABASE http://myserver_url/admin/ManageResourceKey
Cannot%20delete%20or%20update%20a%20parent%20row:%20a%20foreign%20key%20constraint%20fails %20(`adept`.`distributionrights`,%20CONSTRAINT%20`distributionrights_ibfk_2`%20FOREIGN%20K EY%20(`resourceid`)%20REFERENCES%20`resourcekey`%20(`resourceid`))"/>
Magal Varshney

Web-services.xml for EJB component and SOAP Message Handler Chain

I have used the following example for my own web service with EJB component and SOAP
Message Handler Chain:
http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
I have a deployment error:
javax.naming.NameNotFoundException: Unable to resolve 'app/ejb/DocumentService.j
ar#DocumentService/home' Resolved: 'app/ejb' Unresolved:'DocumentService.jar#Doc
umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
In attachement is the ear file.
Is there a problem in web-services.xml?
Thanks
[ws_dox_sdi.ear]

It works. Thanks,
Ioana
"Neal Yin" <[email protected]> wrote:
The error means your EJB is not deployed.
Adding a EJB module to your application.xml file of the ear should fixe
it.
<application>
<display-name />
<module>
<web>
<web-uri>dox_sdi.war</web-uri>
</web>
</module>
<module>
<ejb>DocumentService.jar</ejb>
</module>
</application>
"Ioana Meissner" <[email protected]> wrote in message
news:3cf640cc$[email protected]..
I have used the following example for my own web service with EJBcomponent and SOAP
Message Handler Chain:
http://e-docs.bea.com/wls/docs70/webServices/dd.html#1058208
I have a deployment error:
javax.naming.NameNotFoundException: Unable to resolve'app/ejb/DocumentService.j
ar#DocumentService/home' Resolved: 'app/ejb'Unresolved:'DocumentService.jar#Doc
umentService' ; remaining name 'DocumentService.jar#DocumentService/home'
In attachement is the ear file.
Is there a problem in web-services.xml?
Thanks

Web-services.xml, dtd or xml schema?

Hi there!
I'm just curious to know whether there exists any dtd or schema
for wls 7.x web-services.xml file?
The diagram in
http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
shows one order for the contents of the web-service element,
whereas the examples reflect another (being types,
type-mapping, components, operations).
Why are the example web-services.xml not tagged with the
information of the location of the schema?
Of course building web-services.xml manually is not the first
thing to try, but since the contents are documented and since
it gives the best control over the process, it makes sense.

Hello,
There's not one. The primary vision for the web-services.xml file
was/is to be a linkage between wsdl/soap and the j2ee environment. It
was not intended to be a starting point for building an application, but
a semi-private intermediary.
HTHs,
Bruce
Toni Nykanen wrote:
>
Hi there!
I'm just curious to know whether there exists any dtd or schema
for wls 7.x web-services.xml file?
The diagram in
http://e-docs.bea.com/wls/docs70/webserv/wsp.html#1001373
shows one order for the contents of the web-service element,
whereas the examples reflect another (being types,
type-mapping, components, operations).
Why are the example web-services.xml not tagged with the
information of the location of the schema?
Of course building web-services.xml manually is not the first
thing to try, but since the contents are documented and since
it gives the best control over the process, it makes sense.

Problem in Service XML upload

We are using MDM 2.0.1 on Windows 2008 R2
In the application..
Menu --> Admin Menu --> A --> Application Viewer
In Application Viewer, when we are trying to upload a Service XML file, an error occured showing :
Service XML does not exist+
But in the directory, C:/ouaf/dev9/splapp/xmlmetainfo
all XML files are existing.
We couldn't figure it out what could be the possible cause for this error..
Please Guide us..

Hi SD,
As you have given the key fig length 16, it will show the same in ODS and Cube.
But in front end you can change that.Go to the key fig property -->decimal should be 2 and scaling factor 1.
If you have problem bcos of ERR that is bcos you have not maintained Currency,Create a Cal Key fig--> use NODIM(Original key fig).Hide the orig kf
Cheers,
Shana
Assigning pts is the way of saying thanks in SDN

Exception thrown while reading an XML file using Properties

Exception thrown while reading an XML file using Properties.
Exception in thread "main" java.util.InvalidPropertiesFormatException: org.xml.sax.SAXParseException:
The processing instruction target matching "[xX][mM][lL]" is not allowed.
at java.util.XMLUtils.load(Unknown Source)
<?xml version="1.0"?>
<Config>
     <Database>
          <Product>FX.O</Product>
          <URL>jdbc:oracle:thin:@0.0.0.0:ABC</URL>
     </Database>
</Config>Am I missing anything?

Thanks a lot for all yr help.I have got the basics of
the DTD
However,when I say thus
<!DOCTYPE Config SYSTEM "c:/PartyConfig">
?xml version="1.0"?>
<Config>
     <Database>
          <Product>FX</Product>
          <URL>jdbc:oracle:thin:@0.0.0.0:ABC</URL>
     </Database>
</Config>I get the error
Invalid system identifier: file:///c:/ParyConfig.dtd
Please advise?for goodness sake, how many times do I have to tell you that you can't just expect the Properties class to accept arbitrary XML in any format? it reads XML in the format I linked to, and nothing else. Properties is not a general purpose XML binding. you can't do what you're trying to do with it. read this and in particular pay attention to the following
The XML document must have the following DOCTYPE declaration:
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
Furthermore, the document must satisfy the properties DTD described above.
you are not reading my answers properly, are you? kindly do so

Kodo-service.xml vs kodo.properties

Similar Messages

Maybe you are looking for