EA3: Versioning : Subversion - Commit

Hi all!
I checked out from an existing repository using the HTTP protocol.
After making changes to a file I wanted to commit the changes.
I tried to choose "Commit..." from
- The Versioning menu
- Right mouse click on the Worksheet of the File
- Right mouse click on the file tab on the left
Every one of them brought me the following error message after applying the Log message:
org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: svn: Commit failed (details follow):
svn: MKACTIVITY request failed on '/svn/project/!svn/act/598f8937-1901-0010-9f69-83fd84ec8eea'
svn: can not read HTTP status line
Am I doing something wrong?
Regards,
Hansi

Same here I can't commit changes.
I can update the files, browse history and view changes between each history revision and working copy, but if I try to commit I get the following error:
org.tigris.subversion.javahl.ClientException: svn: authentication cancelled.
And the following stack:
org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
     at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.commit(AbstractJhlClientAdapter.java:274)
     at oracle.jdevimpl.vcs.svn.op.SVNOperationCommit.invokeCommit(SVNOperationCommit.java:206)
     at oracle.jdevimpl.vcs.svn.op.SVNOperationCommit.invokeCommandImpl(SVNOperationCommit.java:72)
     at oracle.jdevimpl.vcs.svn.op.AbstractSVNOperation.mav$invokeCommandImpl(AbstractSVNOperation.java:46)
     at oracle.jdevimpl.vcs.svn.op.AbstractSVNOperation$1.doCommitOperation(AbstractSVNOperation.java:105)
     at oracle.jdeveloper.vcs.spi.VCSDialogCommitter$1.run(VCSDialogCommitter.java:82)
Caused by: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
     at org.tigris.subversion.javahl.JavaHLObjectFactory.throwException(JavaHLObjectFactory.java:435)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.throwException(SVNClientImpl.java:1311)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.commit(SVNClientImpl.java:498)
     at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.commit(AbstractJhlClientAdapter.java:268)
     ... 5 more
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled
     at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:30)
     at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:164)
     at org.tmatesoft.svn.core.internal.io.fs.FSRepository.getUserName(FSRepository.java:1084)
     at org.tmatesoft.svn.core.internal.io.fs.FSRepository.getCommitEditor(FSRepository.java:881)
     at org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:644)
     at org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:579)
     at org.tmatesoft.svn.core.wc.SVNCommitClient.doCommit(SVNCommitClient.java:549)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.commit(SVNClientImpl.java:496)
     ... 6 more

Similar Messages

Do we have a new version of comm.jar?

The version I am using in Windows is 1.0, jared in 1998. I am wondering if there is any new comm.jar release for Windows. I can find comm 3.0 for Linux in Sun site but nothing about Windows. Does anyone have info on it? What is Sun's plan on this package for Windows? Thanks!

Sun's plan is: "scrap it and never touch it again" as MS changed the API. Look for an alternate implementation like RXTX.

Getting Error on viewing subversion version history on file

I'm using SQL Dev Version 2.1.1.64.39 with version control to an existing subversion-server in the LAN.
Doing an SVN Update or Commit in SQL Developer works fine!
Working in file system with Windows Explorer and TortoiseSVN works fine, too.
But when I want to view the history of an file in SQL Developer I got the error:
Unable to retrieve version history for D:\Test\bla.sql
with the exception Stack:
org.tigris.subversion.svnclientadapter.SVNClientException: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
     at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getLogMessages(AbstractJhlClientAdapter.java:2205)
     at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getLogMessages(AbstractJhlClientAdapter.java:2225)
     at org.tigris.subversion.svnclientadapter.AbstractClientAdapter.getLogMessages(AbstractClientAdapter.java:194)
     at org.tigris.subversion.svnclientadapter.AbstractClientAdapter.getLogMessages(AbstractClientAdapter.java:139)
     at oracle.jdevimpl.vcs.svn.history.SVNHistoryEntryProducer.produceEntries(SVNHistoryEntryProducer.java:79)
     at oracle.jdevimpl.vcs.svn.history.SVNHistoryEntryProducer.produceEntries(SVNHistoryEntryProducer.java:52)
     at oracle.jdevimpl.vcs.generic.GenericHistoryProvider.getEntries(GenericHistoryProvider.java:142)
     at oracle.jdeveloper.history.HistoryManager.buildModel(HistoryManager.java:348)
     at oracle.jdevimpl.history.HistoryViewer$7.doInBackground(HistoryViewer.java:499)
     at oracle.jdevimpl.history.HistoryViewer$7.doInBackground(HistoryViewer.java:495)
     at javax.swing.SwingWorker$1.call(SwingWorker.java:278)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at javax.swing.SwingWorker.run(SwingWorker.java:317)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:619)
Caused by: org.tigris.subversion.javahl.ClientException: svn: authentication cancelled
     at org.tigris.subversion.javahl.JavaHLObjectFactory.throwException(JavaHLObjectFactory.java:777)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.throwException(SVNClientImpl.java:1850)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.logMessages(SVNClientImpl.java:470)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.logMessages(SVNClientImpl.java:430)
     at org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getLogMessages(AbstractJhlClientAdapter.java:2195)
     ... 16 more
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled
     at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:60)
     at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
     at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.findStartingProperties(DAVUtil.java:126)
     at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineProperties(DAVUtil.java:216)
     at org.tmatesoft.svn.core.internal.io.dav.DAVUtil.getBaselineInfo(DAVUtil.java:174)
     at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:182)
     at org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482)
     at org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:851)
     at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534)
     at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:716)
     at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:532)
     at org.tmatesoft.svn.core.javahl.SVNClientImpl.logMessages(SVNClientImpl.java:462)
     ... 18 more

version 2.1.0.63 (main build 63.73) also has the same problem
Wayne
-- it appears to be some type of authentication error. When we turn off authentication we can view the history with no problems. Possibly same problem as
Re: EA3: Versioning : Subversion - Commit ?
Edited by: wcoleku on Mar 26, 2010 5:00 PM
Our version of subversion is 1.4.2
USE AT OWN RISK
tried the following fix and it appears that it worked (haven't fully tested yet)
downloaded and installed jdeveloper Studio 11.1.1.2.0
make a copy of files before trying
copied C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.jdeveloper.subversion\*.jar files to C:\sqldeveloper64-2.1.1.64.39\sqldeveloper\jdev\extensions\oracle.jdeveloper.subversion
copied C:\oracle\Middleware\jdeveloper\jdev\extensions\oracle.jdeveloper.subversion.jar to C:\sqldeveloper64-2.1.1.64.39\sqldeveloper\jdev\extensions\
Edited by: wcoleku on Mar 26, 2010 5:35 PM

What version of SVNKit can we expect with 11g?

Hi,
JDev 11g TP4 uses SVNKit 1.1.4 which does not seem to work with the current version of Subversion Server (1.5.2).
Error: svn: Malformed Network Data
The current version of SVNKit is 1.2.0 so the latest JDev plugin is quite behind by a number of versions.
The only workaround at the moment is to downgrade Subversion server.
It would be disappointing for the new release of JDev to be shipped with a plug-in that will work with current release of Subversion, will this be the case?
thanks,
Brenden

Brenden,
I just did a test using JDeveloper 11g drop 6 (which is a build that Ace Directors got for testing, later than TP4, much earlier than 11g r1) - I was able to create a new application, import it into an SVN 1.5.2 repository (via HTTP), make some changes, and commit back to the repository.
When I use Tools->Preferences->Versioning->Subversion, I see it is using SVNKit 1.1.7 (r4142).
I do have the SVN Server installed on my laptop, so I went into the svnkit.jar (<jdev_home>/jdev/extensions/oracle.jdeveloper.subversion) and checked the JAR file - it is, in fact, 1.1.7.
Frank - could I ask you to clarify please (it's actually the reason I originally posted something and then deleted it). I know that JDev 11g is built on a SVN 1.4 client (not a 1.5) - I thought you may be confusing SVNKit version with SVN client version. Drop6 has svnkit 1.1.7, which does appear to work with Subversion 1.5.2 (according to [url http://www.nabble.com/svn:-Malformed-network-data-td16423851.html]this and [url https://svn.svnkit.com/repos/svnkit/tags/1.1.8/changelog.txt]this, it appears 1.1.7 is the first version to work properly with 1.5.x
I guess we'll find out in the next week or so (or so) what version SVNKit comes with 11g r1 - but it would be awesome if it were 1.1.7 at minimum (like drop 6)
John

Dreamweaver + Subversion + Workflow = Impossible?

For several years, my team and I have been using Dreamweaver with Microsoft VSS 6.0. We had a decent workflow in place and felt comfortable that various versions of our code were being stored in the VSS repository. When we upgraded to Dreamweaver CS5 we were very excited that Subversion was now the sole supported version control system for Dreamweaver. However, we knew there'd be a learning curve working with it and moving off of VSS.
The Problem
I need help getting an optimal solution in place using Dreamweaver and Subversion that allows my three developers to work on code without the risk of overwriting each others work.
Attempts and Current Understanding
I know that Dreamweaver's check-in/check-out feature with notes has worked reliably in the past and think of that as a viable option here. However, this feature gets disabled when version contorl with Subversion is enables. I make up that this is because of the shared functionality of buttons within Dreamweaver. For example, the check-in button is the same as the Version Control >> Commit command that is availabl when right clicking on a file. When "checking a file out" of Subversion within the Dreamweaver IDE the vanilla Dreamweaver functionality that notifies other developers that someone else is working on a file goes away. If I want to use vanilla Dreamweaver check-in/check-out with notification I cannot enable version control in that Dreamweaver site.
Right now here's where we're at...
One development Dreamweaver site called WD_Site and a production site called WP_Site. Here's how we have the configuration of each setup.
WD_Site (Development)
Local Files: Somewhere on each of our C-drives
Remote Server: Our development web server accessed via UNC path (\\servername\sharename)
Testing Server: Our testing web server accessed via UNC path
Version Control: None
Cache: Off
Design Notes: Maintain, enabled upload of design notes to share
Check-In/Check-Out: Enabled
On Save we're automatically uploading to remote
We're not checking-out files automatically on open
Testing Server Model: Coldfusion
WP_Site (Production)
Local Files: Test Server
Remove Server: None
Testing Server: Production Web Server accessed via UNC path
Version Control: Subversion, HTTP
The theory is that we can use Dreamweaver's check-in/check-out for the actual work being done in the WD_Site. This seems to work well as long as we're checking files in and out form the Remote View. Local view works very poorly. There is a huge delay and much inconsistency in how the status of a file (red check, green check, lock, etc.) icons appear. In fact, it's flat-out lousy. In the remote server view it work much better. We'd then check-in code that's ready for test, it'd autosave to our development server and then the developer would move it up to our test server manually.
From there the test passes because we're super good at what we do. Then we're ready to go to PRD. We want to check the code into the repository and then move the file up to production in our WP_Site. Check-in to subversion comes up with errors almost all of the time. Is this because of the way the original repository was imported from TortoiseSVN v1.6.14? What's going on?
Please try this out and give me any tips for making this desired process work. I'm counting on you developer community. You're my last and only hope.

Any opinions on this?
Cheers and thanks
Patrick

JDeveloper 11.1.2.1.0 Can't edit subversion client config

I'd like to change the subversion client config to enable auto-props but can't find an option to do this in JDeveloper. Tools->Preferences...->Versioning->Subversion->General only appears to have an option for modifying the server parameters. Anybody know how I can change the subversion client config through JDev?

Makes sense. Editing the svn 'servers' file through JDev displays it's path at the top of editor:
C:\Documents and Settings\BLACKADR\Application Data\JDeveloper\system11.1.2.1.38.60.81\o.jdeveloper.subversion
and I can see that there is also a default 'config' file in this same folder so I guess this must be the one JDev will pick up. Will think about raising an enhancement request for an Edit "Client config" option in the JDev Preferences dialog. Thanks for your help.

Unable to use Subversion 1.7 from JDeveloper 11.1.2?

When I try to check out a workspace from my Subversion repository, I get the message
svn: The path '...' appears to be part of Subversion 1.7 ... Please upgrade your Subversion (SVNKit) client to use this working copy.
I'm running JDev 11.1.2.1.0. Under Tools, Preferences, Versioning, Subversion, I can see that "Native Client (jni, version 1.6.15) is selected.
There is no update available under Help, Check for Updates.
Can it really be true that the latest JDev doesn't support the latest SVN here more than 6 months after its release? If you are seeing this issue, how are you circumventing it?
Best regards
Sten Vesterli

As per these forum posts SVN 1.7 doesnot work with Jdev 11.1.1.5 , I wasn't able to make to work with Jdev 11.1.1.6 either
Jdeveloper 11.1.1.5.0 and Subversion 1.7.0
Jdeveloper Crashed - Previously reported error [IllegalStateException...
Not too sure about Jdev 11.1.2 though one of the forum posts say it should work post 11gr2 update 1

How do I add files to a local Subversion repository using JDeveloper?

Hi Guys and Gals,
Using Studio Edition Version 11.1.1.3.0. Extension "Version Support for Subversion 11.1.1.3.37.56.60".
I'm getting into creating my first "real" JDeveloper program and want to implement Subversion control. I've never done anything with version control software before so please go easy on me.
Problem:
<ol>After my initial project import, I cannot add any new files to subversion since the "Add" icon remains grayed out.</ol>
Process:
<ol>I'm working off the Oracle JDeveloper 11g Handbook step by step (pages 57-59). I'm not sure what I'm doing wrong.
<li>Create a local repository by going to Versioning | Subversion | Create Local Repository. No problems</li>
<li>Select Versioning | Version Application. No problems again.</li>
<li>All my files now have a '1' by them, but no state icons. I do have a new window called "Versioning Navigator" that popped up showing my files and subversion connection.</li>
<li>I add a new file. It doesn't matter what type. From looking at the book and online sources, I should be able to right click the file or select Versioning | Subversion | Add to add the file, but the icons are grayed out on the main menu and on my right-click menu all I get is Versioning | Import Files or Versioning | Pending Changes. There are no pending changes in my Pending Changes window.</li></ol>
What gives?

Lovett,
Not sure what you mean by "Integrated?" I'm guessing that what you are probably doing is creating a local repository - that will be OK for just learning and playing about on a single machine, but not for working in a team. I'd seriously recommend installing a SVN server (really, it's quite easy if you use VisualSVN - it's just run the installer and go), as it will be what you must use if you are working in a team environment. For learning - just run the SVN server on the JDeveloper machine - it's what I did when I wrote the articles.
But yes, I understand the desire to keep it simple. You should be able to do most of the stuff in the ADF Essentials series (except for log in as different users) with a local repository.
Best,
John

EA3: Unable to See the contents in Materialized Views

I have been using sql developer 1.2.1.
I exported my connections as an xml and imported it in EA3 Version 1.5.0.53.
In Version 1.2.1, I am able to see the tables under Materialized Views, but in EA3, If I click on the folder which says "Materialized Views" nothing happens.
DB
Database version to which I am connecting -> Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
SQL Developer
Oracle SQL Developer 1.5.0.53
Version 1.5.0.53
Build MAIN-53.04
Thanks
Maha

variable SCHEMA VARCHAR2
exec :SCHEMA :='JDESTAGE'
select name,object_id, '' short_name,
o.OWNER OBJECT_OWNER
from sys.all_snapshots s,sys.all_objects o
where s.owner = o.owner
and s.name = o.object_name
and s.owner = :SCHEMA
and o.object_type = 'MATERIALIZED VIEW' ;
Result
anonymous block completed
NAME OBJECT_ID SHORT_NAME OBJECT_OWNER
0 rows selected
-Maha

EHS - CG36 - Import report - Set MSDS version from key file data

Hi.
This is in reference to thread EHS - CG36 - Import report - how to define MSDS version in key file?
I'm faced with the same client requirement, came across this discussion, and wondering if there was a solution to this.
I'm on ECC6.0. My client requests to retain the Version of the MSDS at the time of export (CG54 Dok-X, VER key file data) when it gets imported to another system (CG36). Example (similar to Roy's): If the reports in export system are 1.0 and 2.0, then they must be created in the import system the same, not 1.0 and 1.1.
Apparently, as Christoph has stated, the standard CG36 Import process doesn't make use of the VER key file data besides storing it into the Report's Additional Info (DMS Class charact.).
I tried to get around this via the user exit. In the IMPORT fm, I set the version/subversion of the report to be created but the C1F3 fm that does the actual report creation just ignores it. If you've done a similar approach, what have I missed? I'm also afraid if I have to clone the C1F3 fm...
I appreciate your thoughts and inputs.
Thanks in advance.
Excerpt from my fm ZC13G_DOKX_SDB_IMPORT:
FORM l_create_ibd_report...
IF e_flg_error = false.
*   fill the report_head
    e_report_head-subid     = i_subid.
    e_report_head-sbgvid    = i_sbgvid.
    e_report_head-langu     = i_langu.
    e_report_head-ehsdoccat = i_ehsdoccat.
    e_report_head-valdat    = sy-datum.
    e_report_head-rem       = i_remark.
*beg-LECK901211-ins
    e_report_head-version    = i_ver.
    e_report_head-subversion = i_sver.
*end-LECK901211-ins
* Begin Correction 15.06.2004 745589 ***********************************
    IF ( l_api_subjoin_tab[] IS INITIAL ).
*     create the report
      CALL FUNCTION 'C1F3_REPORT_CREATE'
        EXPORTING
          i_addinf            = i_addinf
          i_flg_header        = true
          i_flg_subjoin       = false
        IMPORTING
          e_flg_lockfail      = l_flg_lockfail
          e_flg_error         = l_flg_error
          e_flg_warning       = l_flg_warning
        CHANGING
          x_api_header        = e_report_head
        EXCEPTIONS
          no_object_specified = 1
          parameter_error     = 2
          OTHERS              = 3.
    ELSE.
Edited by: Maria Luisa Noscal on Apr 8, 2011 8:23 AM

Solution is to incorporate the logic used by tc CG36VEN, that is, the process of performing a direct table ESTDH update after the new report is saved into the database.
Edited by: Maria Luisa Noscal on Apr 19, 2011 7:34 PM

Javax comm 2.0 API

Hello everyone.
Do anyone of you know why the new version of comm api (version 3.0) does not support Windows? It is only available for Solaris SPARC, Solaris x86, and Linux x86.
Therefore, I can only use comm 2.0. But my problem is that although I have managed to connect a GPS device with my desktop, I can not do that with my laptop or a different desktop pc that I have tried.
The problem is that the application that I have developed can not find the COM port that I describe.
Any thoughts?
Thanks a lot
Pavlos

http://www.rxtx.org/
RXTX is an open source javax.comm 2.x compatible package with multi platform support. I use it on all of WinXP/CE, Linux, FreeBSD, OSX and it works like a charm for parallel, serial and serial to USB devices (for GPRS modems and GPS devices specifically). RXTX is nicely abstracted also so you don't specifically need to use anything but the javax.comm interface unless you want to use one of the API extensions (for example clearCommInput() which is a very obvious omission in the javax.comm api - skip() just does not cut it).
The code itself is not well documented - for the most part you can use the javax.comm documentation or just read the source - but it works, and works very well. Even if the heuristics in the RXTXCommDriver don't automatically find the device (you can check the sources as to why) you can add devices at runtime with CommPortIdentifier.addPortName() if needed.

Updating Comms 6 GA to U2, do I need to run comm_dssetup.pl again?

I'm planning on upgrading our Comms 6 server from GA to U2.
Do I need to run comm_dssetup.pl if I already ran it under Comms 6.0 GA?
I read [the wiki|http://comm_dssetup.pl] and get the impression that this is required if you are going from a non 6.0 version of comms. Further clarification here or in the wiki would be great.

karl.rossing wrote:
Can i run commpkg upgrade and upgrade comm_dssetup.pl and Delegated admin before taking an outage to upgrade for the rest (mail, calendar, convergence and IM) of the components.The first step will be to run ./commpkg upgrade to upgrade dssetup (and only dssetup) and then run the comm_dssetup.pl command. This will result in the Directory Server being restarted after the schema changes have been applied (short outage period assuming everything goes smoothly).
Once you have upgraded dssetup you can then run ./commpkg upgrade again to upgrade just Delegated Administrator. This will automatically deploy the updated version into the web-container. You will need to restart the web-container after the upgrade process has concluded.
Are there any side effects from taking delegated admin offfline while the rest of comms is running.Where have you deployed Delegated Administrator? Is it in the same web-container as Convergence and UWC/CE?
Regards,
Shane.

Options under versioning tab

Hi,
What is the difference between the options available under "Versioning" tab
"Commit" and "Commit Design", "Update", "Update Design "
Thanks and Regards
Sugirtha

Hi Sugirtha,
"Commit" and "Update" should work on a selection in Pending Changes, while "Commit All" and "Update All" should respectively commit and update all changes regardless of selection.
I see that there is a bug and the "Commit" and "Commit All" have one and the same behavior, and "Update" and "Update All" have the same too.
I will log a bug for that.
Thanks and best regards,
Ivaylo

Use versions in command line

Hi Community,
is it possible to use the "versions" functions from CLI? When yes, how?
I work more often with Vim and some scripts to create ASCII files... I think it should be possible to use a command for versioning (staging/commit) like in git, but couldn't find right now
Thanks in advance
kind regards
Dirk

Hi,
Agree with garyc007. Exchange 2010 tools show the currently installed Service Pack version, and not what RU is currently installed.
Exchange 2010 SP3's build number is 14.3.123.4. One CAS server ends up with version 14.03.0174.001, it means this server has installed Update Rollup 4 for Exchange Server 2010 SP3 successfully. I recommend you check if the other server has installed Update
Rollup 4 for Exchange Server 2010 SP3 successfully.
Here is a blog for your reference.
Exchange Server and Update Rollups Build Numbers
https://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers.aspx
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Using transaction activation policy together with TOPLINK Java object/relational mapping "commit and resume" transaction?

Has any one has experience using WLE transaction context together with TOPLINK Java
version of "commit and resume" context?

Has any one has experience using WLE transaction context together with TOPLINK Java
version of "commit and resume" context?

EA3: Versioning : Subversion - Commit

Similar Messages

Maybe you are looking for